CVE-2026-103507

waiting for further signalsZero needs more public information before it can validate it.

GHSA-w4rv-834f-h4j4 ↗EUVD-2026-92299 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Perforce P4 (Helix Core) <= 2026.4.1
CWE-73 External Control of File Name or Path
ETK-2026-642, permanent identifier
15d 16h 08msince last run
1h 11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h11m
0
+2h
+6h
+8h
+10h
+12h

description

P4 Search versions earlier than 2026.4.2 are affected by insufficient validation of log output paths. An attacker with a valid service authentication token may write files to arbitrary locations on the host and could potentially obtain code execution as the P4 Search service account.

mitigation

Upgrade P4 Search to version 2026.4.2 or later. Restrict access to service authentication tokens until the upgrade is complete.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.51%42nd percentile
agent run time
1h 11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 08:31Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-05 08:31Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103507

{
  "etk_id": "ETK-2026-642",
  "cve_id": "CVE-2026-103507",
  "display_id": "CVE-2026-103507",
  "ghsa_id": "GHSA-w4rv-834f-h4j4",
  "euvd_id": "EUVD-2026-92299",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated arbitrary file write in P4 Search",
  "summary": "P4 Search versions earlier than 2026.4.2 are affected by insufficient validation of log output paths. An attacker with a valid service authentication token may write files to arbitrary locations on the host and could potentially obtain code execution as the P4 Search service account.",
  "mitigation": "Upgrade P4 Search to version 2026.4.2 or later. Restrict access to service authentication tokens until the upgrade is complete.",
  "vendor": "Perforce",
  "product": "P4 (Helix Core)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2026.4.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "P4Search",
      "purl": null
    }
  ],
  "cwes": [
    73
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0051,
  "epss_percentile": 0.4257,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 70.5311629,
  "t0_at": "2026-10-05T08:31:12.818000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T08:31:12.818000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T08:31:12.818000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103507"
    }
  }
}

published 2026-10-05 11:31Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.