Unauthenticated SSRF via prefix-matched OIDC issuer
Published Jul 2, 2026 · Updated Jul 2, 2026
SSRF in Eclipse Foundation PIA 0.3.0 and earlier allows remote attackers to issue requests to arbitrary hosts through OIDC discovery. The is_issuer_known function compares the untrusted JWT issuer as a string prefix, so userinfo or hostname-suffix URLs pass while discovery and JWKS retrieval target another host. No authentication is required; attacker-controlled keys can then validate a forged token and compromise the integrity of protected SBOM uploads.
Summary
What happened
SSRF in Eclipse Foundation PIA 0.3.0 and earlier allows remote attackers to issue requests to arbitrary hosts through OIDC discovery. The is_issuer_known function compares the untrusted JWT issuer as a string prefix, so userinfo or hostname-suffix URLs pass while discovery and JWKS retrieval target another host. No authentication is required; attacker-controlled keys can then validate a forged token and compromise the integrity of protected SBOM uploads.
The record
- CVE
- CVE-2026-14336
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- The Eclipse Foundation
- Product
- Project Identity Authority (PIA)
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo