CVE-2026-14336: SSRF
PIA's OIDC issuer allowlist for Jenkins tokens uses a bare string-prefix check (issuer.startswith(' https://ci.eclipse.org ') in isissuerknown, pia/models.py:139) instead of validating the issuer as a properly host-bounded URL. An attacker can craft an issuer such as https://ci.eclipse.org@evil.host (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.verifytoken accept a JWT signed with the attacker's own key.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14336?
CVE-2026-14336 has a high severity score of 8.2.
How do I fix CVE-2026-14336?
To fix CVE-2026-14336, ensure that the issuer validation in PIA is updated to use a properly host-bounded URL instead of a bare string-prefix check.
What types of software are affected by CVE-2026-14336?
CVE-2026-14336 affects Jenkins and its PIA module.
What kind of vulnerability is CVE-2026-14336 classified as?
CVE-2026-14336 is classified as a Server-Side Request Forgery (SSRF) vulnerability.
What can an attacker do exploiting CVE-2026-14336?
An attacker can exploit CVE-2026-14336 by crafting a malicious issuer that bypasses the issuer allowlist leading to unauthorized access.