CVE-2026-101322: High severity Eclipse BaSyx AAS Web UI vulnerability
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Eclipse BaSyx AAS Web UIto a version that resolves this vulnerability.Fixed in v2-260924
Event History
Frequently Asked Questions
Which deployments are exposed to credential disclosure?
Deployments of the affected Web UI versions that use authentication are exposed when a user opens a crafted link. The disclosed credential may be Basic Authentication credentials, a Bearer token, or an OAuth2 access token available to the user's browser session.
What does an attacker need to exploit this issue?
The attacker needs to induce a user to open a crafted Web UI URL with an aas or path query parameter directed at an attacker-controlled endpoint. Exploitation relies on the victim's browser having access to credentials configured for the selected infrastructure.
What can be done if upgrading is not immediately possible?
Prevent users from opening untrusted Web UI links, especially links containing aas or path query parameters, and restrict access to the Web UI where possible. Upgrading to v2-260924 removes the vulnerable request-handler behavior.
How can I determine whether my instance is affected?
Instances running v2-241220 through versions before v2-260924 are affected. Review whether the Web UI is configured to use Basic Authentication, Bearer tokens, or OAuth2, as these credentials can be sent to an attacker-controlled destination through crafted links.