CVE-2026-12616: medium-severity vulnerability in Eclipse CSI - PIA
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.5%
The /v1/upload/sbom endpoint extracts the iss claim from the attacker-supplied JWT with signature verification disabled, then interpolates that string into three log statements before any validation gate. Because the configured log format ("%(asctime)s - %(name)s - %(levelname)s - %(message)s") renders newlines literally, an unauthenticated attacker can forge log records that are byte-for-byte indistinguishable from PIA's genuine "Successfully authenticated project" message. PIA is an authentication broker whose logs are explicitly relied upon for incident response (DESIGN.md §5.4 lists "Token verifications" and "Errors" as events to log), so the ability to plant fake auth-success entries directly undermines the audit trail the service exists to produce.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
Eclipse Foundation · Eclipse CSI - PIARelated CVEs — Eclipse CSI - PIA
In the same product, most dangerous first.
CVE-2026-108062MEDIUMPre-authentication OIDC discovery and JWKS fetches run synchronously on the asyncio event loopEPSS 0.5%CVE-2026-107597MEDIUMjwks_uri from the OIDC discovery document is fetched without checking its origin or schemeEPSS 0.4%CVE-2026-14336HIGHCVE-2026-14336EPSS 0.3%CVE-2026-18353HIGHUnauthenticated SSRF in PIA via OIDC issuer allowlist bypassEPSS 0.3%