CVE-2026-128790 · Runtime
NO FIX YET · SEE WHAT TO DO
In Eclipse BaSyx Go Components up to and including 1.1.2, ABAC-enabled deployments do not apply a rule's FILTERLIST fragment filters to single Submodel reads or to $history routes. An authenticated caller with READ access can therefore see fields and Submodels that the access rules are meant to hide from them.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Deployments that run Eclipse BaSyx Go Components 1.1.2 or earlier with ABAC access rules enabled on the Submodel Repository or AAS Environment. Callers with READ access can see hidden fields through single Submodel reads and $metadata; if history.mode is api or audit, $history routes expose complete stored versions as well. Deployments without ABAC rules, or already on 1.1.3, are not affected.
Not affected if abac-disabled, already-on-1.1.3
Who cares aas, abac, basyx, industrial-iot, submodel-repository
1.1.2; anything at or below it is in range.history.mode set to api or audit.1.1.3.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
The issue is fixed in Eclipse BaSyx Go Components v1.1.3.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.