Read the docs

Access rule bypass in Eclipse BaSyx Go Components via encoded slashes

Priority LOW 27CWE-177Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.

Summary

Eclipse BaSyx Go Components from 0 before 1.1.4 matches ABAC ROUTE access rules against the decoded request path, while the router uses the raw encoded path. An encoded slash is a separator for the access check but part of the value for the router (CWE-177), so a narrow rule can match a request that returns a larger resource. An authenticated caller with READ rules on parts of a resource can read the whole resource.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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.

Why it matters now

EPSS 0.00286 21st percentileScored 2026-11-16
Fix Fixed Eclipse BaSyx Go Components (Eclipse Foundation): 1.1.4

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse BaSyx Go Componentsbefore 1.1.41.1.4Patch availableCNA
  • Eclipse BaSyx Go Components VendorEclipse Foundation Affected before 1.1.4 Fixed in 1.1.4 Patch available CNA

Remediation

Update Eclipse BaSyx Go Components to version 1.1.4, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA Eclipse BaSyx Go Components (Eclipse Foundation) Fixed in 1.1.4

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-128986
  2. 2026-11-13 Alias added: GHSA-gjpm-3829-v3j3

References

  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 482 →

Sources