---
id: CVE-2026-107597
title: >-
  jwks_uri from the OIDC discovery document is fetched without checking its
  origin or scheme
summary: >-
  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 appr…
severity: medium
cvss: 5.1
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N'
cvssSource: cna
cwe:
  - CWE-918
vendor: Eclipse Foundation
product: Eclipse CSI - PIA
affected:
  - eclipse_csi_-_pia <= 0.8.0
published: '2026-10-20'
updated: '2026-10-20'
sourceUpdated: '2026-10-20T10:06:37.127Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-107597'
references:
  - url: 'https://github.com/eclipse-csi/pia/security/advisories/GHSA-97mq-mw55-36px'
  - url: 'https://gitlab.eclipse.org/security/cve-assignment/-/work_items/397'
tags:
  - cve.org
ingestedAt: '2026-10-20T12:05:07.343Z'
---

## Overview

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.

## Affected

- `eclipse_csi_-_pia <= 0.8.0`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.