Quick answers
- Is CVE-2026-14336 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14336 being exploited in the wild.
- How severe is CVE-2026-14336?
- High severity, with a CVSS score of 8.2, published 2 July 2026.
- Which products and versions are affected?
- Eclipse Foundation CSI - PIA <=0.3.0.
- Is there a fix for CVE-2026-14336?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14336 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14336?
- Check whether you run Eclipse Foundation CSI - PIA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the `is_issuer_known` function within `pia/models.py` of Eclipse CSI - PIA. The application uses a simple `startswith()` string check to validate OIDC issuers (e.g., checking for 'https://ci.eclipse.org') rather than performing proper host-bounded URL validation. An unauthenticated attacker can exploit this by providing a malicious issuer URL using 'userinfo' or 'suffix' tricks (e.g., 'https://ci.eclipse.org.evil.host'). This allows the attacker to trigger a Server-Side Request Forgery (SSRF) during OIDC discovery and JWKS fetching, ultimately leading the application to accept a JWT signed with the attacker's own keys via the `/v1/upload/sbom` endpoint.
Affected products
- Eclipse Foundation Eclipse CSI - PIA <=0.3.0
Timeline
- 2026-07-02: disclosed: Initial publication of the CVE record.
- 2026-07-02: advisory