CVE-2026-20144

MEDIUMNVD 4.96.8
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-02-18. NVD baseline CVSS 4.9; sources differ by 1.9.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.8, and 9.2.11, and Splunk Cloud Platform versions below 10.2.2510.0, 10.1.2507.11, 10.0.2503.9, and 9.3.2411.120, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the the Splunk _internal index could view the Security Assertion Markup Language (SAML) configurations for Attribute query requests (AQRs) or Authentication extensions in plain text within the conf.log file, depending on which feature is configured.

CVSS v3
4.9
EG Score
6.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 9, 2026
No patch confirmed yet.
generic

SVD-2026-0209 | Splunk Vulnerability Disclosure

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 36 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 09:47 UTCEG score recompute
  7. 2026-08-14 09:47 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 02:04 UTCEG score recompute
  10. 2026-08-13 02:04 UTCGHSA enrichment
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 07:26 UTCEG score recompute
  14. 2026-08-11 07:26 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 14:06 UTCEG score recompute
  17. 2026-08-09 14:06 UTCGHSA enrichment
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 21:40 UTCEG score recompute
  21. 2026-08-07 21:40 UTCGHSA enrichment
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 03:34 UTCEG score recompute
  24. 2026-08-06 03:34 UTCGHSA enrichment
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-04 15:10 UTCEPSS rescore
  27. 2026-08-04 10:38 UTCEPSS rescore
  28. 2026-08-03 10:35 UTCEPSS rescore
  29. 2026-08-02 20:20 UTCEG score recompute
  30. 2026-08-02 20:20 UTCGHSA enrichment
  31. 2026-08-02 02:26 UTCEPSS rescore
  32. 2026-08-01 04:15 UTCEPSS rescore
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-27 14:13 UTCEPSS rescore
  35. 2026-07-27 13:28 UTCEG score recompute
  36. 2026-07-27 13:28 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-20144?
CVE-2026-20144 is a medium vulnerability published on February 18, 2026. In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.8, and 9.2.11, and Splunk Cloud Platform versions below 10.2.2510.0, 10.1.2507.11, 10.0.2503.9, and 9.3.2411.120, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the the Splunk _internal index…
When was CVE-2026-20144 disclosed?
CVE-2026-20144 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20144 actively exploited?
CVE-2026-20144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.0% of all scored CVEs.
What is the CVSS score of CVE-2026-20144?
CVE-2026-20144 has a CVSS v3 base score of 4.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.8.
How do I remediate CVE-2026-20144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20144, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-20144?

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