All vulnerabilities

Servers and applications

CVE-2026-131189

Audit Log Injection through the REST API in Splunk Enterprise

Severity
Medium 5.3
Published
19 Nov 2026
Last changed
19 Nov 2026
Added to UpHeron
19 Nov 2026
Fixed in
9.4.17, 10.0.12, 10.2.9, 10.4.5
Weakness
CWE-117
Attack
Over the network · No login needed · No user action needed
Attacker can
Change some data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Sources
CVE Program

Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject arbitrary fields into Splunk Enterprise audit records via the Representational State Transfer (REST) API. Successful exploitation could allow the unauthenticated user to forge audit evidence, compromising the integrity of audit reviews and security detections that rely on legacy audit-field parsing. The vulnerability exists because Splunk Enterprise does not neutralize field delimiters in user-supplied data before writing the data to a legacy audit record. The affected workflow also does not create a corresponding structured audit record.

From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Splunk EnterpriseServers and applications · cna:splunk|splunk enterprise
  • From 9.4 before 9.4.17
  • From 10.0 before 10.0.12
  • From 10.2 before 10.2.9
  • From 10.4 before 10.4.5

About Splunk Enterprise

log aggregator software

From Wikidata, CC0 1.0.
Docker Hub pulls
93,960,955Docker Hub, 15 Nov 2026

Release lines

ReleaseLatestSecurity fixes
10.410.4.0Until 18 May 2028
10.210.2.4Until 15 Jan 2028
10.010.0.7Until 28 Jul 2027
9.49.4.12Until 16 Dec 2026
9.39.3.13Ended 24 Jul 2026
9.29.2.12Ended 31 Jan 2026

From endoflife.date.

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-131189