CVE-2026-103509

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

GHSA-m94h-8qfm-w394 ↗EUVD-2026-102095 ↗

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.3
fixed in 2026.4.3
CWE-1220 Insufficient Granularity of Access Control
ETK-2026-1703Zero's internal tracking ID, independent of the CVE number., permanent identifier
5d 03h 30msince last run
56mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+10h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

P4Search versions 2026.4.2 and earlier can expose stored credentials through the configuration API. An actor with administrative access to the connected P4 Server may retrieve those credentials and use them to expand access.

mitigation

Upgrade P4Search to version 2026.4.3 or later. Restrict P4 Server administrative access and rotate credentials that may have been exposed.

fixed in 2026.4.3

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.23%12th percentile
agent run time
56m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 14:41Z
Δ 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-15 14:41Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1703",
  "cve_id": "CVE-2026-103509",
  "display_id": "CVE-2026-103509",
  "ghsa_id": "GHSA-m94h-8qfm-w394",
  "euvd_id": "EUVD-2026-102095",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cleartext credential exposure in P4Search configuration API",
  "summary": "P4Search versions 2026.4.2 and earlier can expose stored credentials through the configuration API. An actor with administrative access to the connected P4 Server may retrieve those credentials and use them to expand access.",
  "mitigation": "Upgrade P4Search to version 2026.4.3 or later. Restrict P4 Server administrative access and rotate credentials that may have been exposed.",
  "vendor": "Perforce",
  "product": "P4 (Helix Core)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.4.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.4.3"
      ],
      "package_name": "P4Search",
      "purl": null
    }
  ],
  "cwes": [
    1220
  ],
  "cvss_score": 8.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H",
  "epss_score": 0.0023,
  "epss_percentile": 0.1287,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 55.662101166666666,
  "t0_at": "2026-10-15T14:41:28.829000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T14:41:28.829000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T14:41:28.829000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103509"
    }
  }
}

published 2026-10-15 18:02Z
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.