CVE-2026-20163

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-03-11. a secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: 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.4, 9.4.9, and 9.3.10, and Splunk Cloud Platform versions below 10.2.2510.5, 10.0.2503.12, 10.1.2507.16, and 9.3.2411.124, a user who holds a role that contains the high-privilege capability edit_cmd could execute arbitrary shell commands using the unarchive_cmd parameter for the /splunkd/__upload/indexing/preview REST endpoint.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity72% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

March 11, 2026

Last Modified

June 17, 2026

Advisory Details (1)

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

SVD-2026-0302 | Splunk Vulnerability Disclosure

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× 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 49 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 11:53 UTCEG score recompute
  5. 2026-08-16 11:53 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 20:37 UTCGHSA enrichment
  9. 2026-08-14 07:50 UTCEG score recompute
  10. 2026-08-14 07:50 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 23:02 UTCEG score recompute
  13. 2026-08-12 23:02 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 21:51 UTCEG score recompute
  16. 2026-08-11 21:51 UTCGHSA enrichment
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-11 04:59 UTCEG score recompute
  19. 2026-08-11 04:59 UTCGHSA enrichment
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-10 08:55 UTCGHSA enrichment
  22. 2026-08-09 20:13 UTCEG score recompute
  23. 2026-08-09 20:13 UTCGHSA enrichment
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 07:32 UTCEG score recompute
  26. 2026-08-09 07:32 UTCGHSA enrichment
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-08 07:00 UTCGHSA enrichment
  29. 2026-08-07 18:18 UTCEG score recompute
  30. 2026-08-07 18:18 UTCGHSA enrichment
  31. 2026-08-06 19:54 UTCEG score recompute
  32. 2026-08-06 19:54 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 02:03 UTCEG score recompute
  35. 2026-08-06 02:03 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 10:38 UTCEPSS rescore
  39. 2026-08-04 01:21 UTCEG score recompute
  40. 2026-08-04 01:21 UTCGHSA enrichment
  41. 2026-08-03 10:35 UTCEPSS rescore
  42. 2026-08-02 17:37 UTCEG score recompute
  43. 2026-08-02 17:37 UTCGHSA enrichment
  44. 2026-08-02 02:26 UTCEPSS rescore
  45. 2026-08-01 04:15 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-27 14:13 UTCEPSS rescore
  48. 2026-07-27 13:42 UTCEG score recompute
  49. 2026-07-27 13:42 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20163?
CVE-2026-20163 is a high vulnerability published on March 11, 2026. In Splunk Enterprise versions below 10.2.0, 10.0.4, 9.4.9, and 9.3.10, and Splunk Cloud Platform versions below 10.2.2510.5, 10.0.2503.12, 10.1.2507.16, and 9.3.2411.124, a user who holds a role that contains the high-privilege capability editcmd could execute arbitrary shell commands using the…
When was CVE-2026-20163 disclosed?
CVE-2026-20163 was first published in the National Vulnerability Database on March 11, 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-20163 actively exploited?
CVE-2026-20163 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 60.7% of all scored CVEs.
What is the CVSS score of CVE-2026-20163?
CVE-2026-20163 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-20163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20163, 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-20163

Explore →

Is Your Infrastructure Affected by CVE-2026-20163?

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

Start Free Scan →Browse All CVEs