Skip to main content
VulnerabilityPublished

CVE-2026-128790: Eclipse BaSyx Go Components · Incorrect Authorization

Affects Eclipse BaSyx Go ComponentsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.1.3 soon.

Data as of 13 Nov 2026, 15:16 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (eclipse)CVSS 4.07.1
Patch
Available – fixed in 1.1.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Eclipse BaSyx Go Components to 1.1.3.

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse BaSyx Go ComponentsAffected
  • <1.1.3
Fixed in
  • 1.1.3

AI-suggested

Upgrade to Eclipse BaSyx Go Components version 1.1.3 or later, where this authorization issue is fixed. No other mitigation is indicated by the vendor advisory.

Description

Eclipse BaSyx Go Components versions up to 1.1.2 contain an incorrect authorization vulnerability in ABAC-enabled deployments of the Submodel Repository and AAS Environment. Specifically, certain GET requests for single Submodels and their metadata do not apply access rule filters, allowing authenticated users with READ access to view fields that should be hidden. Additionally, when versioning is enabled, history endpoints return unfiltered data, exposing sensitive fields and entire Submodels or Asset Administration Shells that should be restricted. This issue is fixed in version 1.1.3.

References

Community reviews

Loading reviews…