CVE Intelligence
High File handling

CVE-2026-103508 — Path traversal via logging configuration in P4Search

P4 Search (formerly Helix Search) allows an authenticated user holding administrative privileges on the connected P4 Server to supply a crafted logging configuration that causes files to be written or deleted outside the intended logging directory. This could lead to code execution as the P4 Search service account. This issue affects P4 Search 2026.4.2 and earlier. Perforce resolved it in 2026.4.3.

Published Oct 15, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Perforce

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Perforce
P4 (Helix Core)
CVSS base
7.3
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Perforce P4 (Helix Core)).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Perforce P4 (Helix Core) ≤ 2026.4.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
High
User interaction
None
Scope
X
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
High
Availability (vulnerable system)
High
Confidentiality (subsequent)
Low
Integrity (subsequent)
High
Availability (subsequent)
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.3 CVSS 4.0 High — — security@puppet.com via NIST National Vulnerability Database
7.3 CVSS 4.0 High — — Perforce via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security@puppet.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-23 · Relative Path Traversal

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 16, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · perforce/p4 (helix core)
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 7.3
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Oct 15, 2026 · Perforce

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

Perforce
every CVE for this vendor
File handling
same class
CWE-23
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-103509 Credential Disclosure in P4 Search Configuration API 1d
  • CVE-2026-103512 Ticket host-binding bypass via spoofed client IP in P4Search 11d
  • CVE-2026-103511 Arbitrary file-write via extension installation in P4Search 11d
  • CVE-2026-103510 Authentication bypass via blank auth token in P4Search 11d
  • CVE-2026-103507 Arbitrary file-write via log configuration path in P4Search 11d
  • CVE-2026-100102 RCE via exposed JDWP debug agent in P4Search 11d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-103508 is "Path traversal via logging configuration in P4Search", rated High. It affects P4 (Helix Core) (Perforce); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.