Splunk Enterprise is widely deployed across organizations; an unauthenticated SPL injection that executes when admins open a workflow can expose data and disrupt logging/monitoring—high impact and broad reach.
CVE-2026-76316
Unauthenticated SPL injection in Splunk Add Data forwarder workflow allows data access and disruption.
Is CVE-2026-76316 being exploited?
Not confirmed. CVE-2026-76316 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-76316?
CVE-2026-76316 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-76316?
Yes. A fix has been recorded for CVE-2026-76316. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76316 affect?
CVE-2026-76316 affects Splunk Enterprise < 10.4.1, Splunk Enterprise < 10.2.5, Splunk Enterprise < 10.0.9, Splunk Enterprise < 9.4.14, 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-76316?
Upgrade to fixed Splunk versions, restrict management port access, and audit forwarder registrations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can inject SPL that runs when an admin opens the Add Data forwarder workflow, enabling data access, integrity compromise, and service disruption.
Immediate action required
- affected>= 10.4 and < 10.4.1
- affected>= 10.2 and < 10.2.5
- affected>= 10.0 and < 10.0.9
- affected>= 9.4 and < 9.4.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.