CVE-2026-131189: Audit Log Injection through the REST API in Splunk Enterprise
This Splunk advisory covers CVE-2026-131189 in Splunk Enterprise.
- CVE-2026-131189
Key facts
- Vendor rating
- Medium, CVSS 5.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N· base score 5.3, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: low. Availability impact: none.- Weakness
- CWE-117 The software does not neutralize or incorrectly neutralizes output that is written to logs.
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Splunk Enterprise 10.4 before 10.4.5; Splunk Enterprise 10.2 before 10.2.9; Splunk Enterprise 10.0 before 10.0.12 and 1 more below
- Fixed in
- Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9 and 2 more below
- Source published
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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. For more information see Auditing activities in a Splunk platform instance ( ) and About structured audit trail logs ( ) in the Splunk documentation.
Text from the source record.
- Splunk Enterprise 10.4 before 10.4.5
- Splunk Enterprise 10.2 before 10.2.9
- Splunk Enterprise 10.0 before 10.0.12
- Splunk Enterprise 9.4 before 9.4.17
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-131189
Upgrade to a fixed release named by Splunk:
- Splunk Enterprise 10.6.1
- Splunk Enterprise 10.4.5
- Splunk Enterprise 10.2.9
- Splunk Enterprise 10.0.12
- Splunk Enterprise 9.4.17
Vendor guidance
- Upgrade to a fixed release: Splunk Enterprise 10.6.1, Splunk Enterprise 10.4.5, Splunk Enterprise 10.2.9, Splunk Enterprise 10.0.12, Splunk Enterprise 9.4.17.
Support dates for the fixed release lines
- Splunk Enterprise 10.4: support ends
- Splunk Enterprise 10.2: support ends
- Splunk Enterprise 10.0: support ends
- Splunk Enterprise 9.4: support ends
More Splunk advisories
CVE-2026-131197Nov 19, 2026Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk ObservabilityCVE-2026-131196Nov 19, 2026Denial of Service (DoS) through Splunk-to-Splunk Data Forwarding in Splunk EnterpriseCVE-2026-131195Nov 19, 2026Denial of Service (DoS) through HTTP PubSub Channel Subscriptions in Splunk EnterpriseCVE-2026-131194Nov 19, 2026Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk EnterpriseCVE-2026-131193Nov 19, 2026Improper Input Validation through HTTP Event Collector Token Names in Splunk EnterpriseCVE-2026-131192Nov 19, 2026Authentication Bypass through the REST API in Splunk Enterprise
Get an email when Splunk Enterprise publishes the next one.
See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.