What’s Vulnerable › Vulnerabilities
CVE-2026-101322
- Severity: high (CVSS 8.3 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-01 · updated 2026-10-01
- Weakness: CWE-201
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.
Affected products
- Eclipse Foundation Eclipse BaSyx AAS Web UI: from v2-241220 before v2-260924 — fixed in v2-260924
How to fix
Upgrade to a fixed version: Eclipse Foundation Eclipse BaSyx AAS Web UI v2-260924. Check the vendor advisory for mitigations.
References
- https://github.com/eclipse-basyx/basyx-aas-web-ui/pull/1557
- https://github.com/eclipse-basyx/basyx-aas-web-ui/releases/tag/v2-260924
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/328
Get alerted when CVE-2026-101322 or the next vulnerability affects your stack