Splunk Enterprise is widely deployed across enterprises; local token interception can lead to full compromise of Splunk data and service account, causing broad operational and security impact.
CVE-2026-76259
Local user can bind Splunk Windows management port and hijack authentication tokens.
Is CVE-2026-76259 being exploited?
Not confirmed. CVE-2026-76259 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.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-76259?
CVE-2026-76259 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-76259?
Yes. A fix has been recorded for CVE-2026-76259. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76259 affect?
CVE-2026-76259 affects Splunk Enterprise for Windows < 10.4.2, Splunk Enterprise for Windows < 10.2.6, Splunk Enterprise for Windows < 10.0.9, Splunk Enterprise for Windows < 9.4.13, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76259?
Upgrade Splunk Enterprise (Windows) to 10.4.2/10.2.6/10.0.9/9.4.13/9.3.14 or later.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can bind management port before service start, intercept child-process auth tokens, and access/compromise all data and system integrity of the Splunk service account.
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.13
- affected>= 9.3 and < 9.3.14
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.