CVE-2026-14336
HighCVSS 8.2Exploitation Probability (EPSS)
Low risk24th percentile — higher than 24% of all known CVEs
Summary
The vulnerability in PIA uses a bare string-prefix check for the OIDC issuer allowlist instead of validating the issuer as a properly host-bounded URL. An attacker can craft an issuer that passes the prefix check but points to a controlled server. This allows an unauthenticated caller of POST /v1/upload/sbom to force outbound HTTP(S) requests to an arbitrary host and accept a JWT signed with the attacker's key.
Risk Assessment
The risk includes Server-Side Request Forgery (SSRF) and JWT token forgery, potentially leading to unauthorized access to organizational systems and data.
Recommendation
Immediately update PIA to a version where OIDC issuer validation uses full host-bounded URL verification. Until then, restrict access to the /v1/upload/sbom endpoint and monitor outbound HTTP(S) requests.
Original NVD description (English source)
PIA's OIDC issuer allowlist for Jenkins tokens uses a bare string-prefix check (issuer.startswith(' https://ci.eclipse.org ') in is_issuer_known, pia/models.py:139) instead of validating the issuer as a properly host-bounded URL. An attacker can craft an issuer such as https://[email protected] (userinfo trick) or https://ci.eclipse.org.evil.host (suffix trick) that satisfies the prefix check while pointing the OIDC discovery and JWKS fetches at a server the attacker controls. An unauthenticated caller of POST /v1/upload/sbom can use this to force PIA to make outbound HTTP(S) requests to an arbitrary attacker-chosen host, and to have oidc.verify_token accept a JWT signed with the attacker's own key.