Affects widely used enterprise logging (Splunk); allows access to credentials/indexed data and requires immediate org-wide mitigation.
CVE-2026-20296
CSRF in Splunk Web allows remote SPL execution as splunk-system-user
Is CVE-2026-20296 being exploited?
Not confirmed. CVE-2026-20296 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-20296?
CVE-2026-20296 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20296?
Yes. A fix has been recorded for CVE-2026-20296. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-20296 affect?
CVE-2026-20296 affects Splunk Enterprise < 10.4.1, 10.2.5, 10.0.8, 9.4.13, Splunk Cloud Platform < 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, 10.1.2507.24. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20296?
Upgrade to fixed Splunk versions; restrict list_deployment_server roles; apply CSRF mitigations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CSRF + input injection enables arbitrary SPL execution as splunk-system-user, exposing stored credentials and indexed data.
Immediate action required
- affected>= 10.5.2605 and < 10.5.2605.0
- affected>= 10.4.2604 and < 10.4.2604.7
- affected>= 10.3.2512 and < 10.3.2512.16
- affected>= 10.2.2510 and < 10.2.2510.18
- affected>= 10.1.2507 and < 10.1.2507.24
- affected>= 10.4 and < 10.4.1
- affected>= 10.2 and < 10.2.5
- affected>= 10.0 and < 10.0.8
- affected>= 9.4 and < 9.4.13
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.