# CVE-2026-15704: CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components

> Attackers can bypass ABAC authorization by appending trailing slashes to protected API routes, allowing unauthorized access to data and operations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-86p5-cmgc-c94w

## What is CVE-2026-15704?

CVE-2026-15704 is a critical missing authorization vulnerability in Eclipse BaSyx Go Components, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control), CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-15704?


## How do I fix CVE-2026-15704?

No fix has been published for CVE-2026-15704 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15704 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15704 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15704 and fix it if it is affected.

What it is: CVE-2026-15704 is a critical missing authorization vulnerability in Eclipse BaSyx Go Components, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15704 exists.

Affected product: Eclipse BaSyx Go Components. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15704/ (Markdown: https://insights.sbomify.com/CVE-2026-15704/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15704
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15704
- OSV: https://osv.dev/vulnerability/CVE-2026-15704

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15704/
Summaries are generated and may contain mistakes; the official description above is the record.