Skip to main content
VulnerabilityPublished

CVE-2026-101322: Eclipse BaSyx AAS Web UI · CWE-201

Affects Eclipse BaSyx AAS Web UISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to v2-260924 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in v2-260924, 2-260924
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 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 15 Nov 2026.

What to do

Upgrade Eclipse BaSyx AAS Web UI to v2-260924; eclipse-basyx/basyx-aas-web-ui to 2-260924.

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse BaSyx AAS Web UIAffected
  • ≥ v2-241220, < v2-260924
Fixed in
  • v2-260924
GitHubeclipse-basyx/basyx-aas-web-uipkg:github/eclipse-basyx/basyx-aas-web-uiOther threatsAffected
  • <2-260924 >=2-241220
Fixed in
  • 2-260924

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Eclipse BaSyx AAS Web UI version v2-260924 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

In Eclipse BaSyx AAS Web UI versions v2-241220 through releases before v2-260924, the shared request handler attached the selected infrastructure's `Authorization` header to outgoing requests without checking the destination origin. In deployments using authentication, an attacker could induce a user to open a crafted Web UI link whose `aas` or `path` query parameter points to an attacker-controlled endpoint. The user's browser would then send the configured Basic Authentication credentials, Bearer token, or an available OAuth2 access token to that endpoint. The attacker could reuse the disclosed credential to access protected AAS services with the victim's privileges. The issue is fixed in v2-260924.

References

Community reviews

Loading reviews…