CVE-2026-76354: Splunk Enterprise · The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 8.1 High · fixed in 10.4.2 : patch Splunk Enterprise soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2, 10.2.6, 10.0.9 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9 or 9.4.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
A fix is available in Splunk Enterprise versions 9.4.14, 10.0.9, 10.2.6, and 10.4.2. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated in the advisory.
Description
CVE-2026-76354 is a high-severity vulnerability in Splunk Enterprise affecting versions 9.4 through 9.4.14, 10.0 through 10.0.9, 10.2 through 10.2.6, and 10.4 through 10.4.2. It allows users without admin or power roles to send crafted REST API requests that can delete or temporarily overwrite files writable by the Splunk Enterprise process on non-captain search head cluster members. The issue arises from improper handling of NUL bytes in bundle replication paths during search head clustering, which can affect system integrity and availability.