In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 10.4.5 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 22:55 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 10.4.5, 10.2.9, 10.0.12 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 19 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12 or 9.4.17.
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
The vulnerability affects versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17. Users should upgrade to at least these versions where the issue is fixed. No alternative mitigations or workarounds are specified.
Description
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user can inject arbitrary fields into audit records via the REST API. This allows forging of audit evidence, potentially compromising audit integrity and security detections relying on legacy audit parsing. The issue arises because field delimiters in user data are not neutralized before writing to legacy audit records, and no structured audit record is created for this workflow.