CVE-2025-13036

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.3% (21st 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

Also known asEUVD-2025-210168 (ENISA EUVD) · GHSA-q6qc-22qv-jjr8 (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate 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.3%CVSS: 9.2Exploit: None knownExposed services: Not assessed

Upgrade to v12.00.00 and later (from the CVE record's solution, Rockwell Automation) — apply it.

An authentication bypass security issue exists within FactoryTalk Historian Site Edition. By continually sending requests to the login endpoint, an attacker may obtain a valid authentication token.

CVSS
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.3% × 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 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: Upgrade to v12.00.00 and later (from the CVE record's solution, Rockwell Automation). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
21st
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
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: 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).

Upgrade to v12.00.00 and later (from the CVE record's solution, Rockwell Automation). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 16, 2026

Last Modified

October 7, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
Fix named in the CVE record's solution (Rockwell Automation).

Vendor Advisories for CVE-2025-13036(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 13× in last 7d / 58× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 253 rows 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 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-13036?
CVE-2025-13036 is a critical-severity vulnerability; its CVE record was published on June 16, 2026. An authentication bypass security issue exists within FactoryTalk Historian Site Edition. By continually sending requests to the login endpoint, an attacker may obtain a valid authentication token.
When was CVE-2025-13036 made public?
CVE-2025-13036 was made public on June 16, 2026: that is the date its CVE record's CNA, Rockwell Automation, gives for when the vulnerability was made public. The CVE record itself was published on June 16, 2026. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2025-13036 actively exploited?
CVE-2025-13036 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-13036?
CVE-2025-13036 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-13036?
The CVE record's solution for CVE-2025-13036, written by its CNA Rockwell Automation, names the fix: "Upgrade to v12.00.00 and later". The vendor advisories EchelonGraph has for CVE-2025-13036 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-13036?

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