CVE-2025-12012

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2025-210462 (ENISA EUVD) · GHSA-3cv6-265j-3gwv (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.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.

A denial-of-service issue exists in 5380/5480/5580 controllers. This vulnerability could potentially allow a malicious user to write invalid file data to the controller, causing the device to enter a major non-recoverable fault (MNRF).

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 14, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
No fix on record yet.

Vendor Advisories for CVE-2025-12012(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 23× in last 7d / 71× 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 98 of 440 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 342 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-12012?
CVE-2025-12012 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. A denial-of-service issue exists in 5380/5480/5580 controllers. This vulnerability could potentially allow a malicious user to write invalid file data to the controller, causing the device to enter a major non-recoverable fault (MNRF).
When was the CVE record for CVE-2025-12012 published?
The CVE record for CVE-2025-12012 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2025-12012 actively exploited?
CVE-2025-12012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-12012?
CVE-2025-12012 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-12012?
No fix for CVE-2025-12012 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-2025-12012 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-12012

Explore →

Is Your Infrastructure Affected by CVE-2025-12012?

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