CVE-2025-12768

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 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-210818 (ENISA EUVD) · GHSA-f7wq-9ch9-3gvp (GitHub Security Advisories)Source: ENISA EUVD

8.6EG
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: 0.4%CVSS: 8.6Exploit: 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 security issue exists within FactoryTalk® Historian Machine Edition. An attacker with low-level authentication could exploit this vulnerability to achieve remote code execution on the affected device.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 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.
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
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 (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-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-25). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; 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

September 1, 2026

Last Modified

October 19, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2025-12768(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 10× in last 7d / 73× 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 174 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 76 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-12768?
CVE-2025-12768 is a high-severity vulnerability; its CVE record was published on September 1, 2026. A security issue exists within FactoryTalk® Historian Machine Edition. An attacker with low-level authentication could exploit this vulnerability to achieve remote code execution on the affected device.
When was the CVE record for CVE-2025-12768 published?
The CVE record for CVE-2025-12768 was published on September 1, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-12768 actively exploited?
CVE-2025-12768 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-12768?
CVE-2025-12768 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-12768?
No fix for CVE-2025-12768 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-12768 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-12768?

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