Medium · CVSS 5.1CVE-2026-107597

jwks_uri from the OIDC discovery document is fetched without checking its origin or schemeCVE-2026-107597

Answer in brief

CVE-2026-107597 records a Medium severity (CVSS 5.1) vulnerability in jwks_uri from the OIDC discovery document is fetched without checking its origin or scheme. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/Eclipse CSI - PIA (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 20, 2026Updated Oct 20, 2026Source checked Oct 20, 2026First seen by HOL Oct 20, 2026Material review Oct 20, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 5.1. 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 CSI - PIA (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Eclipse Foundation/Eclipse CSI - PIAgeneric	>=0 <=0.8.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/Eclipse CSI - PIA.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

PIA's token verification (`verify_token` in `pia/oidc.py`) fetches the OIDC discovery document of an allowlisted issuer and then follows the `jwks_uri` contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty (`pia/oidc.py:42-52`). An approved identity provider — and every registered per-project Jenkins instance under `https://ci.eclipse.org/<project>/oidc` is a separate such party (`pia/models.py`) — can therefore direct PIA to issue a GET request to an arbitrary host and port, including over plaintext `http`, from PIA's own network position. The fetch happens before any signature is verified, as a side effect of an unauthenticated `POST /v1/upload/sbom` request that is ultimately rejected with 401.

Quoted source text, attributed separately from HOL analysis.