CVSS 4.0
6.0 mediumCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVE-2026-128986 eclipse foundation eclipse basyx go components: Interpretation Conflict
Medium (6.0) in eclipse foundation eclipse basyx go components.
On this page
In Eclipse BaSyx Go Components versions up to and including 1.1.3, ABAC-enabled deployments match `ROUTE` access rules against the fully decoded request path, while the router routes on the raw, still encoded path. An encoded slash (`%2F`) inside a path value is a segment separator for the access check but part of the value for the router, so a request can match a narrow `ROUTE` rule while the handler returns a different, larger resource.
An authenticated caller whose rules grant READ only on parts of a resource can therefore read the whole resource. In the DPP API, a rule such as `/v1/dpps/*/elements/*`, meant to grant only passport elements, also grants the complete passport whose identifier contains `/elements/`. In the Submodel Repository, AAS Repository and AAS Environment, a rule such as `/submodels/*/submodel-elements/*/attachment`, meant to grant only file attachments, also grants the complete element whose stored idShort contains `%2F`.
The issue is fixed in Eclipse BaSyx Go Components v1.1.4.
Severity
- CWEs
- CWE-177 Improper Handling of URL Encoding (Hex Encoding)
CWE-436 Interpretation Conflict
CWE-863 Incorrect Authorization - OWASP Top 10
- A01:2025 Broken Access Control, A06:2025 Insecure Design
- Published
- Assigned by
- eclipse (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-128986 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128986?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128986?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128986 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-128986)
HTML:
<a href="https://cve.bz/cve/CVE-2026-128986"><img src="https://cve.bz/cve/badge/CVE-2026-128986.svg" alt="CVE-2026-128986"></a>
Affected
- eclipse foundation:eclipse basyx go components
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Eclipse Foundation Eclipse BaSyx Go Components | before 1.1.4 |
Attack patterns (CAPEC)
- CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
- CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
- CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High
- CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
- CAPEC-72 URL Encoding Likelihood: High · Severity: High
- CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
- CAPEC-468 Generic Cross-Browser Cross-Domain Theft Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.