Cyber Resilience

CVE-2026-103510

Published
05 October 2026
Modified
06 October 2026
CVSS Score v4 9.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/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
EPSS Score 0.0035 26th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-103510 is a critical-severity Failing Open (CWE-636) vulnerability in Perforce (inferred from references). Its CVSS base score is 9.5 (Critical).

Operationally, ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CP-12 (Safe Mode) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the…

more

connected P4 Server.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-41759Shared CWE-636
CVE-2026-41334Shared CWE-636
CVE-2026-68746Shared CWE-636
CVE-2026-69306Shared CWE-636
CVE-2026-53852Shared CWE-636
CVE-2024-2660Shared CWE-636
CVE-2026-27448Shared CWE-636
CVE-2025-41760Shared CWE-636
CVE-2026-41377Shared CWE-636
CVE-2026-18329Shared CWE-636

Affected Assets

Perforce
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CP-12 Safe Mode partial match

CP-12 forces entry into a safe mode on detected conditions, limiting exposure but not covering every failure path.

SA-8 requires application of engineering principles that include fail-secure design, reducing the likelihood the weakness is introduced.

SC-24 directly requires the system to fail to a known state that preserves security properties, structurally stopping fallback to a less-secure mode.

SI-17 mandates explicit fail-safe procedures that activate on indicated failures, preventing the insecure fallback behavior.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-636, a class-level weakness, and none of its children carries one either.

References