CVE-2026-18353
Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedPIA'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 reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:
What is affected
ReportedEclipse Foundation; Eclipse CSI - PIA. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedTrack* · 224.9
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
Not reportedNot reported by tracked sources.
What to do
Not reportedNot reported by tracked sources.
Evidence detail
Loading the full tracker evidence record…