CVE-2026-15704: Software Security Vulnerability Vulnerability
CRITICALCVE-2026-15704 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-180: Incorrect Behavior Order: Validate Before Canonicalize) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-15704 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-15704
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.
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-15704, 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-180: Incorrect Behavior Order: Validate Before Canonicalize, where the product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step. 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
References
Frequently Asked Questions
What is CVE-2026-15704?
Which Software versions are affected?
What version fixes CVE-2026-15704?
What is the CVSS score of CVE-2026-15704?
What CWE is associated with CVE-2026-15704?
How can I check Maven dependencies for CVE-2026-15704?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-86p5-cmgc-c94w",
"modified" : "2026-07-24T09:32:16Z",
"published" : "2026-07-24T09:32:16Z",
"aliases" : [ "CVE-2026-15704" ],
"details" : "In Eclipse BaSyx Go Components versions up to and including 1.0.0, ABAC-enabled deployments are vulnerable to an authorization bypass caused by inconsistent trailing-slash handling between the ABAC middleware and the HTTP router.\n\n\n\nThe shared router configuration used Chi's `middleware.StripSlashes`, so a request such as `GET /shells/` was dispatched to the registered `GET /shells` route. However, the ABAC middleware evaluated the original request path including the trailing slash. If ABAC route lookup did not find a matching slash-suffixed route, the request was passed onward and the router then stripped the slash and executed the protected handler without the intended ABAC authorization decision and without the expected ABAC query filters.\n\n\n\nAn unauthenticated or unauthorized network attacker could append a trailing slash to protected API routes to reach handlers that should have been denied by ABAC policy. Depending on the exposed component, HTTP method, and deployed policy, this could allow unauthorized read, create, update, delete, or upload operations.\n\n\n\nThe issue affects ABAC-enabled deployments of services that use the shared router and ABAC middleware, including AAS Repository, Submodel Repository, AAS Registry, Submodel Registry, Concept Description Repository, Discovery, AAS Environment upload, and related services. The issue is fixed in Eclipse BaSyx Go Components v1.0.1.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-15704"
}, {
"type" : "WEB",
"url" : "https://github.com/eclipse-basyx/basyx-go-components/pull/442"
}, {
"type" : "WEB",
"url" : "https://github.com/eclipse-basyx/basyx-go-components/releases/tag/v1.0.1"
}, {
"type" : "WEB",
"url" : "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/164"
}, {
"type" : "WEB",
"url" : "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/580"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-180" ],
"severity" : "CRITICAL",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-07-24T09:16:24Z"
}
}