Splunk is a widely used enterprise logging/monitoring platform. This bug lets a non-admin obtain a system session token to access all data and alter configuration, posing broad operational risk.
CVE-2026-76351
Non-admin can steal system session token via report notifications to access and alter Splunk.
Is CVE-2026-76351 being exploited?
Not confirmed. CVE-2026-76351 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-76351?
CVE-2026-76351 is rated High with a CVSS score of 8.8. 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-76351?
Yes. A fix has been recorded for CVE-2026-76351. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76351 affect?
CVE-2026-76351 affects Splunk Enterprise < 10.4.2, < 10.2.6, < 10.0.9, < 9.4.14, Splunk Secure Gateway < 3.10.9, < 3.9.23, < 3.8.70. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76351?
Upgrade Splunk Enterprise and Secure Gateway to the fixed versions immediately; restrict reporting access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker can force Secure Gateway to use a system-level session token, obtain a passwordless session token, read all data and modify platform configuration.
Immediate action required
- affected>= 10.4 and < 10.4.2
- affected>= 10.2 and < 10.2.6
- affected>= 10.0 and < 10.0.9
- affected>= 9.4 and < 9.4.14
- affected>= 3.10 and < 3.10.9
- affected>= 3.9 and < 3.9.23
- affected>= 3.8 and < 3.8.70
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.