# CVE-2026-103507: Arbitrary file-write via log configuration path in P4Search

> An authenticated attacker can write arbitrary files via the logging interface, potentially achieving code execution on the host.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-w4rv-834f-h4j4

## What is CVE-2026-103507?

CVE-2026-103507 is a high-severity path traversal vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Perforce P4 Search prior to 2026.4.2 does not restrict file paths written through its logging configuration interface. An attacker holding the service authentication token can write arbitrary files on the host, potentially leading to code execution as the P4 Search service account.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-103507?


## How do I fix CVE-2026-103507?

No fix has been published for CVE-2026-103507 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103507 being exploited?

There is no known exploitation of CVE-2026-103507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103507 and fix it if it is affected.

What it is: CVE-2026-103507 is a high-severity path traversal vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103507 in the wild and no public exploit code.

Affected product: Perforce P4 (Helix Core). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103507/ (Markdown: https://insights.sbomify.com/CVE-2026-103507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103507
- OSV: https://osv.dev/vulnerability/CVE-2026-103507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103507/
Summaries are generated and may contain mistakes; the official description above is the record.