CISA ADP Vulnrichment

Answer in brief

CVE-2026-101322 records a High severity (CVSS 8.3) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/Eclipse BaSyx AAS Web UI (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 1, 2026Updated Oct 1, 2026Source checked Oct 1, 2026First seen by HOL Oct 1, 2026Material review Oct 1, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Eclipse Foundation/Eclipse BaSyx AAS Web UI (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Eclipse Foundation/Eclipse BaSyx AAS Web UIgeneric	>=v2-241220 <v2-260924	v2-260924

Recommended response

Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/Eclipse BaSyx AAS Web UI.
Review the reported fix. Update Eclipse Foundation/Eclipse BaSyx AAS Web UI to v2-260924 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 1, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.