CVE-2026-15704 Details
Description
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. The 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. An 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. The 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.
A vulnerability allowing authorization bypass has been identified in Eclipse BaSyx Go Components versions up to and including 1.0.0. This issue affects ABAC-enabled deployments due to inconsistent handling of trailing slashes between the ABAC middleware and the HTTP router. The shared router configuration used Chi's 'middleware.StripSlashes', causing requests with trailing slashes to be routed to the corresponding route without the slash. However, the ABAC middleware evaluated the original path with the trailing slash. If no matching route was found for the slash-suffixed path, the request was forwarded, the router stripped the slash, and the protected handler was executed without the necessary ABAC authorization or query filters. This flaw allows unauthorized access to protected API routes by appending a trailing slash, potentially enabling unauthorized read, create, update, delete, or upload operations, depending on the component and HTTP method involved.
Users are advised to upgrade to Eclipse BaSyx Go Components version 1.0.1 or later. For those unable to upgrade immediately, temporary mitigations include rejecting non-root API paths ending in a slash at a reverse proxy or gateway, rewriting such paths to remove the trailing slash before they reach the application, or restricting network access to ABAC-enabled BaSyx Go services until the fixed version is deployed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 24, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-180 | Incorrect Behavior Order: Validate Before Canonicalize | [email protected] |
| CWE-284 | Improper Access Control | [email protected] |
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
No affected product data is available for this CVE.
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 24, 2026 | CVE Translated | [email protected] |
| Jul 24, 2026 | CVE Modified | CISA-ADP |
| Jul 24, 2026 | New CVE Received | [email protected] |