CVE-2026-103510: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-rgmx-jfh8-6fx8
Share
CWE-636
Published
Advisory Summary

CVE-2026-103510 is a CRITICAL security vulnerability vulnerability (CWE-636: Not Failing Securely ('Failing Open')) affecting Software libraries in the Maven ecosystem. The weakness occurs when when the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-103510 at a Glance

CVE Identifier CVE-2026-103510
GHSA Identifier GHSA-rgmx-jfh8-6fx8
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-636: Not Failing Securely ('Failing Open')
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-103510

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-103510, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-636: Not Failing Securely ('Failing Open'), where when the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-103510 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-103510
portal.perforce.com/s/cve/a91qi000003fd... WEB
https://portal.perforce.com/s/cve/a91Qi000003FDw5IAG/authentication-bypass-via-blank-auth-token-in-p4search

Frequently Asked Questions

What is CVE-2026-103510?
CVE-2026-103510 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-636: Not Failing Securely ('Failing Open').
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-103510?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-103510?
CVE-2026-103510 is classified under CWE-636: Not Failing Securely ('Failing Open') (When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.).
How can I check Maven dependencies for CVE-2026-103510?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rgmx-jfh8-6fx8",
  "modified" : "2026-10-05T09:31:52Z",
  "published" : "2026-10-05T09:31:52Z",
  "aliases" : [ "CVE-2026-103510" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS: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"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-103510"
  }, {
    "type" : "WEB",
    "url" : "https://portal.perforce.com/s/cve/a91Qi000003FDw5IAG/authentication-bypass-via-blank-auth-token-in-p4search"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-636" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-05T09:17:06Z"
  }
}