Audit-log forgery via unneutralized JWT issuer
Published Jun 29, 2026 · Updated Jun 29, 2026
Log injection in Eclipse Foundation Project Identity Authority 0 through 0.2.1 allows remote attackers to forge authentication log entries. The /v1/upload/sbom handler decodes the untrusted JWT without signature verification and writes its newline-bearing iss claim into three log messages. No authentication is required, and crafted issuers can create entries indistinguishable from genuine authentication successes, corrupting the incident-response audit trail.
Summary
What happened
Log injection in Eclipse Foundation Project Identity Authority 0 through 0.2.1 allows remote attackers to forge authentication log entries. The /v1/upload/sbom handler decodes the untrusted JWT without signature verification and writes its newline-bearing iss claim into three log messages. No authentication is required, and crafted issuers can create entries indistinguishable from genuine authentication successes, corrupting the incident-response audit trail.
The record
- CVE
- CVE-2026-12616
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- The Eclipse Foundation
- Product
- Project Identity Authority (PIA)
- Classifications
- CWE-117
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 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.2.1
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