Skip to content
major vulnerability· requires attention

Affects widely used Splunk Enterprise; unauthenticated access can expose/alter sensitive log/search data — high-impact for many organizations.

Applications

CVE-2026-76312

9.4
Critical
EPSS 0.36%Patch availableAug 21, 2026

Unauthenticated exposure of session material via embedded Splunk reports

common questions

Is CVE-2026-76312 being exploited?

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

How severe is CVE-2026-76312?

CVE-2026-76312 is rated Critical with a CVSS score of 9.4. 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-76312?

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

What does CVE-2026-76312 affect?

CVE-2026-76312 affects Splunk Enterprise < 10.4.1, Splunk Enterprise < 10.2.6, Splunk Enterprise < 10.0.9, Splunk Enterprise < 9.4.14. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76312?

Update Splunk to fixed versions and restrict/remove public embedded-report HTML exposure

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.1Splunk Enterprise < 10.2.6Splunk Enterprise < 10.0.9Splunk Enterprise < 9.4.14
impact

Unauthenticated attacker can extract session material from embedded-report HTML to access archived search-job data, exfiltrate data and affect integrity.

action required

Immediate action required

affected versions
Splunk Splunk Enterprise
  • affected>= 10.4 and < 10.4.1
  • 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