Skip to content
major vulnerability· requires attention

Splunk is widely deployed in enterprise logging/SIEM; RCE by a low-privileged user can compromise telemetry, data, and operational integrity across organizations.

Applications

CVE-2026-76319

HIGH
High
EPSS 0.38%Patch availableAug 21, 2026

Splunk federated-search flaw allows low-privileged user to achieve remote code execution.

common questions

Is CVE-2026-76319 being exploited?

Not confirmed. CVE-2026-76319 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.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-76319?

CVE-2026-76319 is rated High. 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-76319?

Yes. A fix has been recorded for CVE-2026-76319. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76319 affect?

CVE-2026-76319 affects Splunk Enterprise < 10.4.2, Splunk Enterprise < 10.2.6, 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-76319?

Upgrade to the listed fixed Splunk versions; restrict federated-search roles and audit activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Splunk Enterprise < 10.4.2Splunk Enterprise < 10.2.6Splunk Enterprise < 10.0.9Splunk Enterprise < 9.4.14Splunk Federated Search feature
impact

Low-privileged user can achieve RCE via federated-search bundle selection, access/exfiltrate data, execute commands, and disrupt integrity/availability.

action required

Immediate action required

affected versions
Splunk Splunk Enterprise
  • 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

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free