CVE-2026-20239

HIGHNVD 6.57.5
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 6.5; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.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.5%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 and 10.0 up to but not including 10.0.5; Splunk Cloud Platform versions 10.3.2512 up to but not including 10.3.2512.8, 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 10.0.2503 up to but not including 10.0.2503.13 as affected. No release containing a fix is confirmed on record.

In Splunk Enterprise versions below 10.2.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a role that has access to the _internal index could view session cookies and response bodies that contain sensitive data.

CVSS v3
6.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 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.5%
EPSS %ILE
39th
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

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

SVD-2026-0503 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-20239(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 266 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 166 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.5% · 39th 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.5% · 39th percentile
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-08-23 16:53 UTCEG score recompute
  20. 2026-08-23 16:53 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-08-21 22:53 UTCEG score recompute
  24. 2026-08-21 22:53 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-08-20 18:54 UTCEG score recompute
  27. 2026-08-20 18:54 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  30. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-08-17 09:52 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  32. 2026-08-16 16:52 UTCEG score recompute
  33. 2026-08-16 16:52 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-08-16 03:29 UTCEG score recompute
  36. 2026-08-16 03:29 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  37. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-08-15 01:56 UTCEG score recompute
  39. 2026-08-15 01:56 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  40. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-08-14 13:58 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  42. 2026-08-14 02:01 UTCEG score recompute
  43. 2026-08-14 02:01 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-13 02:12 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  46. 2026-08-12 14:15 UTCEG score recompute
  47. 2026-08-12 14:15 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  48. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-12 01:49 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  50. 2026-08-11 13:51 UTCEG score recompute
  51. 2026-08-11 13:51 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-08-11 01:33 UTCEG score recompute
  54. 2026-08-11 01:33 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-08-10 13:35 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-08-10 01:26 UTCEG score recompute
  58. 2026-08-10 01:26 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-08-09 13:28 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-08-09 01:31 UTCEG score recompute
  62. 2026-08-09 01:31 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-08 09:05 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  65. 2026-08-07 21:08 UTCEG score recompute
  66. 2026-08-07 21:08 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-08-07 09:10 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  68. 2026-08-06 21:12 UTCEG score recompute
  69. 2026-08-06 21:12 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  71. 2026-08-06 09:14 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-08-05 21:16 UTCEG score recompute
  73. 2026-08-05 21:16 UTCGHSA enrichmentGHSA-7mj7-jqh4-hc7f · GitHub severity HIGH · GitHub CVSS 7.5
  74. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  75. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20239?
CVE-2026-20239 is a high-severity vulnerability; its CVE record was published on May 20, 2026. In Splunk Enterprise versions below 10.2.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a role that has access to the _internal index could view session cookies and response bodies that contain sensitive data.
When was CVE-2026-20239 made public?
CVE-2026-20239 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-20239 actively exploited?
CVE-2026-20239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20239?
CVE-2026-20239 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5 (HIGH).
How do I remediate CVE-2026-20239?
No fix for CVE-2026-20239 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 and 10.0 up to but not including 10.0.5; Splunk Cloud Platform versions 10.3.2512 up to but not including 10.3.2512.8, 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 10.0.2503 up to but not including 10.0.2503.13 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-20239 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20239?

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

Book a Demo →Browse All CVEs