CVE-2026-128790
Description
In Eclipse BaSyx Go Components versions up to and including 1.1.2, ABAC-enabled deployments of the Submodel Repository and the AAS Environment do not apply an access rule's `FILTERLIST` fragment filters to single Submodel reads. `GET /submodels` removes the fields that a rule's `FILTERLIST` hides, but `GET /submodels/{submodelIdentifier}` and `GET /submodels/{submodelIdentifier}/$metadata` return them unfiltered. An authenticated caller with READ access to a Submodel can therefore read fields that the access rules hide from them, for example `supplementalSemanticIds` keys that name the other parties allowed to read the Submodel. If versioning is enabled (`history.mode` set to `api` or `audit`), `GET /submodels/{submodelIdentifier}/$history` and `GET /shells/{aasIdentifier}/$history` in the Submodel Repository, AAS Repository and AAS Environment return the complete stored version without applying the rule's formula or fragment filters. A caller whose rules grant READ on these routes can read fields that the access rules hide, and Submodels and Asset Administration Shells that the direct read does not return to them at all. The issue is fixed in Eclipse BaSyx Go Components v1.1.3.
Weakness
- CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
- CWE-863: Incorrect Authorization
CISA SSVC decision points
| Exploitation | none |
|---|---|
| Automatable | no |
| Technical impact | partial |
| Scored | 2026-11-16 |
Timeline
- 2026-11-13Published by the CNA14:12 UTC
- 2026-11-13Published in NVD14:17 UTC · 5 minutes after the CNA
- 2026-11-16CISA SSVC decision recorded3 days after publication
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| eclipse_foundation eclipse_basyx_go_components | from 0 before 1.1.3fixed in 1.1.3 | 1.1.3 |
References
- https://github.com/eclipse-basyx/basyx-go-components/pull/855
- https://github.com/eclipse-basyx/basyx-go-components/pull/883
- https://github.com/eclipse-basyx/basyx-go-components/releases/tag/v1.1.3
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/577
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1371#note_8664220
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-128790'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-128790'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-128790'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-128790'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).