CVE-2026-103511
Arbitrary file-write via extension installation in P4Search
No known exploitation. EPSS puts it in the 26th percentile. Fixed in 2026.4.2.
No public exploit knownFix2026.4.2Upgrade to this build
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
Find your product and version, then upgrade to the build on the right.
- Perforce P4Affected: ≤ 2026.4.1Upgrade to: after 2026.4.1Fixed builds2026.4.2Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
Perforce P4 Search prior to 2026.4.2 does not validate file names supplied to its extension installation feature. An attacker with super-user or service-token privileges can write files with arbitrary content to the P4 Search installation directory.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 26th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 1 day, from the signal feeds we watch.
- Record updated
- Publishedweakness classified, record updated, record updated
Affected products
Technical detail
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for P4 (Helix Core), not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI