CVE-2026-128986
Medium 6.0No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 22% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Weakness: CWE-177, CWE-436, CWE-863
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/eclipse-basyx/basyx-go-components/pull/888 (opens in a new tab)
- https://github.com/eclipse-basyx/basyx-go-components/releases/tag/v1.1.4 (opens in a new tab)
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/582 (opens in a new tab)
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1389 (opens in a new tab)