# CVE-2026-12616: Eclipse CSI - PIA log injection in /v1/upload/sbom

Source: https://junglewise.ai/threats/cve-2026-12616-eclipse-csi-pia-log-injection-in-v1-upload-sbom  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-29. Updated: 2026-06-29  
License: CC BY 4.0 with a link back

CVE-2026-12616 · Severity: info · CVSS 6.9 · Published 2026-06-29

Eclipse CSI - PIA, an authentication broker used to manage security tokens, contains a flaw that allows unauthorized users to manipulate system logs. By sending a specially crafted request, an attacker can insert fake 'successful authentication' entries into the audit trail. This undermines the reliability of the system's logs, making it difficult for security teams to accurately investigate incidents or verify who has actually accessed the system.

Technologies: [Eclipse Foundation CSI - PIA](https://junglewise.ai/threats/technologies/csi-pia). Vendors: [Eclipse Foundation](https://junglewise.ai/threats/vendors/eclipse-foundation).

## Quick answers

**Is CVE-2026-12616 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-12616 being exploited in the wild.

**How severe is CVE-2026-12616?** Informational severity, with a CVSS score of 6.9, published 29 June 2026.

**Which products and versions are affected?** Eclipse Foundation CSI - PIA <=0.2.1.

**Is there a fix for CVE-2026-12616?** 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-12616 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-12616?** 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

A log injection vulnerability (CWE-117) exists in the /v1/upload/sbom endpoint of Eclipse CSI - PIA. The application extracts the 'iss' claim from a user-provided JSON Web Token (JWT) without verifying the cryptographic signature. This claim is then interpolated into log statements before any validation occurs. Because the logging configuration renders newline characters literally, a remote, unauthenticated attacker can inject malicious strings containing newlines to forge log entries. These forged entries can be made identical to legitimate 'Successfully authenticated project' messages, effectively corrupting the audit trail used for incident response. The vulnerability is present in versions up to and including 0.2.1.

## Affected products

- Eclipse Foundation Eclipse CSI - PIA <=0.2.1

## Timeline

- 2026-06-29: disclosed
- 2026-06-29: advisory

## References

- [https://gitlab.eclipse.org/security/cve-assignment/-/work_items/145](https://gitlab.eclipse.org/security/cve-assignment/-/work_items/145)

## Related threats

- [Eclipse Foundation Eclipse CSI - PIA SSRF via OIDC issuer allowlist bypass](https://junglewise.ai/threats/cve-2026-18353-eclipse-foundation-eclipse-csi-pia-ssrf-via-oidc-issuer-allowlist)
- [Eclipse CSI - PIA SSRF and auth bypass via OIDC issuer allowlist prefix check](https://junglewise.ai/threats/cve-2026-14336-eclipse-csi-pia-ssrf-and-auth-bypass-via-oidc-issuer-allowlist)