# 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 Environme


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-grwr-c8jg-hx89

## What is CVE-2026-128790?

CVE-2026-128790 is a high-severity vulnerability in Eclipse BaSyx Go Components, published on 13 Nov 2026. 

### Official 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-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-128790?


## How do I fix CVE-2026-128790?

No fix has been published for CVE-2026-128790 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-128790 being exploited?

There is no known exploitation of CVE-2026-128790 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128790 and fix it if it is affected.

What it is: CVE-2026-128790 is a high-severity vulnerability in Eclipse BaSyx Go Components, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128790 in the wild and no public exploit code.

Affected product: Eclipse BaSyx Go Components. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128790/ (Markdown: https://insights.sbomify.com/CVE-2026-128790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128790
- OSV: https://osv.dev/vulnerability/CVE-2026-128790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128790/
Summaries are generated and may contain mistakes; the official description above is the record.
