Vulnerability record

CVE-2026-18353

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 9, 2026.

What it is

Reported

PIA's `POST /v1/upload/sbom` endpoint accepts a Bearer JWT and checks its **unverified** `iss` claim against an issuer allowlist using Python's `urlparse` before performing OIDC discovery with `requests`. Because `urlparse` and `requests`/`urllib3` parse an authority string containing a backslash (e.g. `https://attacker-host\@ci.eclipse.org/`) into *different* hostnames, an attacker can craft an issuer that passes the allowlist check yet drives `requests` — and subsequently `urllib.request.urlopen` for JWKS retrieval — to connect to an arbitrary attacker-chosen host, port, and scheme. Source description excerpt; complete tracked detail loads below.

NVD published: Jul 30, 2026 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

What is affected

Reported

Eclipse Foundation — Eclipse CSI - PIA. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Jul 30, 2026 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Urgency and basis

Reported

Track* · 224.9

Tracker decision tier from the evidence detailed below · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Exploitation evidence

Not reported

Not reported by tracked sources.

What to do

Not reported

Not reported by tracked sources.

Tracker guidance inferred from the decision tier: Monitor more closely. May require action sooner than standard timelines.

Evidence detail

Loading the full tracker evidence record…