CVE-2026-20240

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory published 2026-05-20. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: 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 CVE record's CNA (Cisco Systems, Inc.) lists Splunk Enterprise versions 10.2 up to but not including 10.2.2, 10.0 up to but not including 10.0.5, 9.4 up to but not including 9.4.11 and 9.3 up to but not including 9.3.12; Splunk Cloud Platform versions 10.4.2603 up to but not including 10.4.2603.1, 10.3.2512 up to but not including 10.3.2512.9, 10.2.2510 up to but not including 10.2.2510.11, 10.1.2507 up to but not including 10.1.2507.21 and 2 more ranges as affected. No release containing a fix is confirmed on record.

In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, and Splunk Cloud Platform versions below 10.4.2603.1, 10.3.2512.9, 10.2.2510.11, 10.1.2507.21, 10.0.2503.13, and 9.3.2411.129, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause a Denial of Service by exploiting the coldToFrozen.sh script in the splunk_archiver app to rename critical Splunk directories, making the instance non-functional.The Denial of Service is possible because of missing input validation in the coldToFrozen.sh script, which accepts arbitrary file paths and renames them without restricting operations to safe directories.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
The EG Score, 6.5 of 10.
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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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 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)60 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 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

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
No fix on record yet.
Web page

SVD-2026-0504 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2026-0504

Vendor Advisories for CVE-2026-20240(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 / 26× 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 232 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 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20240?
CVE-2026-20240 is a medium-severity vulnerability; its CVE record was published on May 20, 2026. In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, and Splunk Cloud Platform versions below 10.4.2603.1, 10.3.2512.9, 10.2.2510.11, 10.1.2507.21, 10.0.2503.13, and 9.3.2411.129, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause a Denial of…
When was CVE-2026-20240 made public?
CVE-2026-20240 was made public on May 20, 2026: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 20, 2026. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-20240 actively exploited?
CVE-2026-20240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20240?
CVE-2026-20240 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-20240?
No fix for CVE-2026-20240 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 CVE record's CNA (Cisco Systems, Inc.) lists Splunk Enterprise versions 10.2 up to but not including 10.2.2, 10.0 up to but not including 10.0.5, 9.4 up to but not including 9.4.11 and 9.3 up to but not including 9.3.12; Splunk Cloud Platform versions 10.4.2603 up to but not including 10.4.2603.1, 10.3.2512 up to but not including 10.3.2512.9, 10.2.2510 up to but not including 10.2.2510.11, 10.1.2507 up to but not including 10.1.2507.21 and 2 more ranges as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-20240 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20240?

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

Book a Demo →Browse All CVEs