CVE-2026-131189

Audit Log Injection through the REST API in Splunk Enterprise

Published Nov 19, 2026 CVSS 3.1 · 5.3 Medium EPSS n/a KEV · Not listed
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 (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/audit-activity-in-splunk-enterprise/auditing-activities-in-a-splunk-platform-instance) and About structured audit trail logs (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/audit-activity-in-splunk-enterprise/about-structured-audit-trail-logs) in the Splunk documentation.

Remediation

Vendor Solution

Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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 (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/audit-activity-in-splunk-enterprise/auditing-activities-in-a-splunk-platform-instance) and About structured audit trail logs (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/audit-activity-in-splunk-enterprise/about-structured-audit-trail-logs) in the Splunk documentation.
Title Audit Log Injection through the REST API in Splunk Enterprise
Weaknesses CWE-117
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Nov 19, 2026, 7:55 PM
Reserved
Nov 17, 2026, 8:26 PM
Status
Received
Published
Nov 19, 2026, 8:17 PM
Modified
Nov 19, 2026, 8:17 PM