CVE-2026-20298

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-15) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
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.3%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.4 up to but not including 10.4.1, 10.2 up to but not including 10.2.5, 10.0 up to but not including 10.0.8 and 9.4 up to but not including 9.4.13; Splunk Cloud Platform versions 10.5.2605 up to but not including 10.5.2605.0, 10.4.2604 up to but not including 10.4.2604.6, 10.3.2512 up to but not including 10.3.2512.15, 10.2.2510 up to but not including 10.2.2510.18 and 1 more range as affected. No release containing a fix is confirmed on record.

In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, and 10.1.2507.24, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could view stored credential hashes when they access the /servicesNS/-/-/storage/passwords REST endpoint through the |rest Search Processing Language (SPL) command.The exposure happens because the |rest SPL command returns the encr_password field in the results of the /servicesNS/-/-/storage/passwords REST endpoint.

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 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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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.
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.3%
EPSS %ILE
23rd
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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

July 15, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 16, 2026
No fix on record yet.
Web page

SVD-2026-0704 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-20298(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 8× in last 7d / 38× 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 184 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 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-20298?
CVE-2026-20298 is a medium-severity vulnerability; its CVE record was published on July 15, 2026. In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, and 10.1.2507.24, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could view stored credential hashes…
When was CVE-2026-20298 made public?
CVE-2026-20298 was made public on July 15, 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 July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-20298 actively exploited?
CVE-2026-20298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20298?
CVE-2026-20298 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-20298?
No fix for CVE-2026-20298 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.4 up to but not including 10.4.1, 10.2 up to but not including 10.2.5, 10.0 up to but not including 10.0.8 and 9.4 up to but not including 9.4.13; Splunk Cloud Platform versions 10.5.2605 up to but not including 10.5.2605.0, 10.4.2604 up to but not including 10.4.2604.6, 10.3.2512 up to but not including 10.3.2512.15, 10.2.2510 up to but not including 10.2.2510.18 and 1 more range as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-20298 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20298?

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