Read the docs

Eclipse BaSyx Go Components ABAC bypass exposes unauthorized Submodel Elements

Priority LOW 31CWE-200Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Information disclosure, 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-200 and CWE-863.

Summary

Eclipse BaSyx Go Components versions before 1.1.3 return Submodel Elements the caller is not authorized to read from GET /submodels/{submodelIdentifier}/submodel-elements in ABAC-enabled deployments of the Submodel Repository and the AAS Environment. If an access rule grants READ on one Submodel Element through a $sme REFERABLE object, the list route returns every element of that Submodel, including its value. The single-element route and full Submodel read deny the other elements, so an authenticated caller with that one grant can read them all. The weakness is CWE-863.

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.2, ABAC-enabled deployments of the Submodel Repository and the AAS Environment return Submodel Elements that the caller is not authorized to read from `GET /submodels/{submodelIdentifier}/submodel-elements`. If an access rule grants READ on a single Submodel Element through a `$sme` `REFERABLE` object, the list route returns every element of that Submodel, including its value, as soon as one element matches the caller's rules. The single-element route and the full Submodel read enforce the same rule and deny access to the other elements. An authenticated caller with a READ grant for one element of a Submodel can therefore read all other elements of that Submodel. The issue is fixed in Eclipse BaSyx Go Components v1.1.3.

Why it matters now

EPSS 0.00313 24th percentileScored 2026-11-16
Fix Fixed Eclipse BaSyx Go Components (Eclipse Foundation): 1.1.3

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.31.1.3Patch availableCNA
  • Eclipse BaSyx Go Components VendorEclipse Foundation Affected before 1.1.3 Fixed in 1.1.3 Patch available CNA

Remediation

Upgrade Eclipse BaSyx Go Components to version 1.1.3, which fixes the issue. The CVSS 4.0 base score is 7.1 (HIGH).

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.3

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Eclipse BaSyx Go Components 1.1.3

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-91536 Eclipse BaSyx Go Components expose fields hidden by access rulesPriority LOW 31

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127102
  2. 2026-11-13 Alias added: GHSA-x45g-v897-hmfm

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