CVE-2026-12357

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.2Exploit: None knownExposed services: Not assessed

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

Heimdall Data Database Proxy generateFileContent CRLF Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Heimdall Data Database Proxy. Authentication is required to exploit this vulnerability.

The specific flaw exists within the generateFileContent function. The issue results from the lack of proper neutralization of CRLF sequences. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-29251.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
33
EG Risk 33/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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 29, 2026
No fix on record yet.
Web page

ZDI-26-447 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-26-447/

Vendor Advisories for CVE-2026-12357(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 229 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-12357?
CVE-2026-12357 is a high-severity vulnerability; its CVE record was published on July 29, 2026. Heimdall Data Database Proxy generateFileContent CRLF Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Heimdall Data Database Proxy. Authentication is required to exploit this vulnerability. The specific…
When was CVE-2026-12357 made public?
CVE-2026-12357 was made public on July 23, 2026: that is the date its CVE record's CNA, Zero Day Initiative, gives for when the vulnerability was made public. The CVE record itself was published on July 29, 2026. EchelonGraph's copy of the record carries a last-modified date of July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-12357 actively exploited?
CVE-2026-12357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12357?
CVE-2026-12357 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12357?
No fix for CVE-2026-12357 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. The vendor advisories EchelonGraph has for CVE-2026-12357 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12357?

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