CVE-2026-14336
Eclipse PIA OIDC Issuer Allowlist Bypass
Description
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.
INFO
Published Date :
July 2, 2026, 10:16 a.m.
Last Modified :
Oct. 25, 2026, 9:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-14336
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | e51fbebd-6053-4e49-959f-1b94eeb69a2c | ||||
| CVSS 3.1 | HIGH | MITRE-CVE | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Validate OIDC issuer as a properly host-bounded URL.
- Avoid using string prefix checks for OIDC issuers.
- Apply security patches for Jenkins OIDC implementation.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-14336.
| URL | Resource |
|---|---|
| https://gitlab.eclipse.org/security/cve-assignment/-/work_items/154 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-14336 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-14336
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-14336 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-14336 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 25, 2026
Action Type Old Value New Value Added Translation Title: Eclipse CSI - PIA de Eclipse Foundation, Description: La lista blanca de emisores OIDC de PIA para tokens de Jenkins utiliza una comprobación de prefijo de cadena simple (issuer.startswith(’ https://ci.eclipse.org ’) en is_issuer_known, pia/models.py:139) en lugar de validar el emisor como una URL correctamente delimitada por el host. Un atacante puede crear un emisor como https://[email protected] (truco de userinfo) o https://ci.eclipse.org.evil.host (truco de sufijo) que satisface la comprobación de prefijo mientras dirige las recuperaciones de descubrimiento OIDC y JWKS a un servidor que el atacante controla. Un llamador no autenticado de POST /v1/upload/sbom puede usar esto para forzar a PIA a realizar solicitudes HTTP(S) salientes a un host arbitrario elegido por el atacante, y a que oidc.verify_token acepte un JWT firmado con la propia clave del atacante. -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jul. 02, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-14336', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'yes'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-07-02T12:26:02.672416Z'} -
New CVE Received by [email protected]
Jul. 02, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://github.com/eclipse-csi/pia', 'vendor': 'Eclipse Foundation', 'product': 'Eclipse CSI - PIA', 'versions': [{'status': 'affected', 'version': '0', 'versionType': 'semver', 'lessThanOrEqual': '0.3.0'}], 'defaultStatus': 'unaffected'}] Added Description 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. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N Added CWE CWE-918 Added Reference https://gitlab.eclipse.org/security/cve-assignment/-/work_items/154