How severe is CVE-2026-103510?

CVE-2026-103510 has a CVSS 4.0 base score of 9.5, rated critical severity.

Is CVE-2026-103510 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-103510?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-103510 published?

CVE-2026-103510 was published on 2026-10-05 and last updated on 2026-10-06.

CVE-2026-103510

CVE-2026-103510 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-636.

Key facts

Severity: Critical (CVSS 4.0 base score 9.5)
EPSS exploit prediction: 0% (26th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-636
Published: 2026-10-05
Last modified: 2026-10-06

Description

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 connected P4 Server.

Frequently asked questions

What is CVE-2026-103510?: 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 connected P4 Server.
How severe is CVE-2026-103510?: CVE-2026-103510 has a CVSS 4.0 base score of 9.5, rated critical severity.
Is CVE-2026-103510 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-103510?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-103510 published?: CVE-2026-103510 was published on 2026-10-05 and last updated on 2026-10-06.

References

https://portal.perforce.com/s/cve/a91Qi000003FDw5IAG/authentication-bypass-via-blank-auth-token-in-p4search

Other CWE-636 vulnerabilities

CVE-2026-22034 — Critical (CVSS 9.8): Snuffleupagus is a module that raises the cost of attacks against website by killing bug classes and providing a…
CVE-2024-3729 — Critical (CVSS 9.8): The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to improper missing encryption exception handling…
CVE-2026-53459 — Critical (CVSS 9.3): Bambuddy is a self-hosted print archive and management system for Bambu Lab 3D printers. Starting in version 0.1.6 and…
CVE-2026-95848 — Critical (CVSS 9.1): Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when a configured authenticator or authorizator class…
CVE-2026-40525 — Critical (CVSS 9.1): OpenViking prior to version 0.3.9 contains an authentication bypass vulnerability in the VikingBot OpenAPI HTTP route…
CVE-2026-77866 — Critical (CVSS 9.0): Server-Side Request Forgery (SSRF) vulnerability in Slab safeurl allows an attacker who controls a validated URL to…

Browse all CWE-636 vulnerabilities →