CVE-2026-14336

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
24.0%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

[Eclipse CSI - PIA] Unauthenticated SSRF via issuer allowlist prefix bypass in OIDC verification (#154) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/154

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 08:56 UTCEG score recompute
  2. 2026-07-13 06:12 UTCEPSS rescore
  3. 2026-07-12 21:19 UTCEG score recompute
  4. 2026-07-12 09:42 UTCEG score recompute
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 22:04 UTCEG score recompute
  7. 2026-07-11 10:27 UTCEG score recompute
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 22:49 UTCEG score recompute
  10. 2026-07-10 11:11 UTCEG score recompute
  11. 2026-07-09 23:32 UTCEG score recompute
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 11:54 UTCEG score recompute
  14. 2026-07-09 00:16 UTCEG score recompute
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-08 12:39 UTCEG score recompute
  18. 2026-07-08 00:57 UTCEG score recompute
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-07 13:20 UTCEG score recompute
  21. 2026-07-07 01:42 UTCEG score recompute
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 14:05 UTCEG score recompute
  24. 2026-07-06 02:28 UTCEG score recompute
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 11 more
  1. 2026-07-05 14:50 UTCEG score recompute
  2. 2026-07-05 03:10 UTCEG score recompute
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 15:33 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 03:55 UTCEG score recompute
  8. 2026-07-03 16:15 UTCEG score recompute
  9. 2026-07-03 04:38 UTCEG score recompute
  10. 2026-07-02 16:59 UTCEG score recompute
  11. 2026-07-02 16:58 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14336?
CVE-2026-14336 is a high vulnerability published on July 2, 2026. 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…
When was CVE-2026-14336 disclosed?
CVE-2026-14336 was first published in the National Vulnerability Database on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14336 actively exploited?
CVE-2026-14336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14336?
CVE-2026-14336 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-14336?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14336, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14336

Explore →

Is Your Infrastructure Affected by CVE-2026-14336?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs