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.5%, top 56% 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

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

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.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No fix on record 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 7× in last 7d / 25× 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.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:11 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 23:21 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-29 15:20 UTCEPSS rescore
  11. 2026-09-28 13:50 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 13:47 UTCEPSS rescore
  14. 2026-09-23 07:33 UTCEG score recompute
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:27 UTCEPSS rescore
  17. 2026-09-18 06:59 UTCEG score recompute
  18. 2026-09-16 05:14 UTCEPSS rescore
  19. 2026-09-14 00:53 UTCEG score recompute
  20. 2026-09-13 16:46 UTCEPSS rescore
  21. 2026-09-12 15:15 UTCEG score recompute
  22. 2026-09-12 15:00 UTCEPSS rescore
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-11 09:36 UTCEPSS rescore
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 14:44 UTCEG score recompute
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:11 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 18:44 UTCEG score recompute
  11. 2026-08-30 01:21 UTCEPSS rescore
  12. 2026-08-28 21:40 UTCEPSS rescore
  13. 2026-08-27 22:48 UTCEG score recompute
  14. 2026-08-27 14:24 UTCEPSS rescore
  15. 2026-08-25 13:48 UTCEPSS rescore
  16. 2026-08-24 12:41 UTCEG score recompute
  17. 2026-08-23 08:56 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 08:58 UTCEG score recompute
  20. 2026-08-21 23:48 UTCEPSS rescore
  21. 2026-08-21 05:37 UTCEG score recompute
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 05:49 UTCEG score recompute
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 23:11 UTCEG score recompute
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-16 21:13 UTCEG score recompute
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 21:25 UTCEG score recompute
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 21:37 UTCEG score recompute
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-12 22:00 UTCEG score recompute
  35. 2026-08-12 13:50 UTCEPSS rescore
  36. 2026-08-11 22:12 UTCEG score recompute
  37. 2026-08-11 13:42 UTCEPSS rescore
  38. 2026-08-10 23:59 UTCEPSS rescore
  39. 2026-08-09 22:31 UTCEG score recompute
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-07 22:55 UTCEG score recompute
  42. 2026-08-06 23:07 UTCEG score recompute
  43. 2026-08-06 13:46 UTCEPSS rescore
  44. 2026-08-05 22:38 UTCEG score recompute
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 22:50 UTCEG score recompute
  47. 2026-08-04 15:09 UTCEPSS rescore
  48. 2026-08-04 10:38 UTCEPSS rescore
  49. 2026-08-03 23:01 UTCEG score recompute
  50. 2026-08-03 10:35 UTCEPSS rescore
  51. 2026-08-02 23:13 UTCEG score recompute
  52. 2026-08-02 02:26 UTCEPSS rescore
  53. 2026-08-01 23:25 UTCEG score recompute
  54. 2026-08-01 04:15 UTCEPSS rescore
  55. 2026-07-30 23:26 UTCEG score recompute
  56. 2026-07-30 16:27 UTCEPSS rescore
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-28 19:45 UTCEG score recompute
  59. 2026-07-28 15:36 UTCEPSS rescore
  60. 2026-07-27 16:55 UTCEG score recompute
  61. 2026-07-27 14:13 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 14:54 UTCEPSS rescore
  64. 2026-07-26 14:17 UTCEG score recompute
  65. 2026-07-25 14:17 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 03:05 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:24 UTCEPSS rescore
  71. 2026-07-20 17:08 UTCEPSS rescore
  72. 2026-07-19 14:30 UTCEPSS rescore
  73. 2026-07-19 02:28 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-16 17:02 UTCEPSS rescore

Related CVEs(same CWE)

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 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 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12616?
CVE-2026-12616 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12616?
No fix for CVE-2026-12616 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

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.

Book a Demo →Browse All CVEs