CVE-2026-12616

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.9
EG Score
6.9(medium)
EPSS
22.7%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.
generic

[Eclipse CSI - PIA] Unauthenticated log injection via JWT `iss` claim (#145) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/145

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 11:25 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 11:36 UTCEG score recompute
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 11:46 UTCEG score recompute
  6. 2026-07-08 15:15 UTCEPSS rescore
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-08 11:57 UTCEG score recompute
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 12:06 UTCEG score recompute
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 12:17 UTCEG score recompute
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 12:28 UTCEG score recompute
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 12:37 UTCEG score recompute
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 12:49 UTCEG score recompute
  20. 2026-07-02 13:00 UTCEG score recompute
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-07-01 13:11 UTCEG score recompute
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 13:21 UTCEG score recompute
Show 2 more
  1. 2026-06-29 13:33 UTCEG score recompute
  2. 2026-06-29 13:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-12616?
CVE-2026-12616 is a medium vulnerability published on June 29, 2026. 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")…
When was CVE-2026-12616 disclosed?
CVE-2026-12616 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12616 actively exploited?
CVE-2026-12616 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12616?
CVE-2026-12616 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-12616?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12616, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12616

Explore →

Is Your Infrastructure Affected by CVE-2026-12616?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs