CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components
Summary
| CVE | CVE-2026-15704 |
|---|---|
| State | PUBLISHED |
| Assigner | eclipse |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-24 09:16:24 UTC |
| Updated | 2026-07-30 19:12:22 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 9.8 CRITICAL from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.003530000 probability, percentile 0.280290000 (date 2026-08-03)
Problem Types: CWE-180 | CWE-284 | CWE-863 | CWE-863 CWE-863 | CWE-284 CWE-284 | CWE-180 CWE-180
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | CVSS | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Eclipse Foundation | Eclipse BaSyx Go Components | affected 1.0.1 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| gitlab.eclipse.org/security/vulnerability-reports/-/work_items/580 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | gitlab.eclipse.org | |
| gitlab.eclipse.org/security/cve-assignment/-/work_items/164 | [email protected] | gitlab.eclipse.org | |
| github.com/eclipse-basyx/basyx-go-components/releases/tag/v1.0.1 | [email protected] | github.com | |
| github.com/eclipse-basyx/basyx-go-components/pull/442 | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Sebastian Eicke (en)
There are currently no legacy QID mappings associated with this CVE.