Unauthenticated log poisoning via ANSI escape injection
Published Dec 3, 2025 · Updated Dec 3, 2025
Log injection in Splunk Web allows remote attackers to corrupt Splunk Enterprise and Splunk Cloud Platform logs via HTTP requests. The /en-US/static/ endpoint writes unvalidated ANSI escape codes from crafted requests into Splunk log files. No authentication is required, but Splunk Web must be enabled; successful injection can poison, forge, or obfuscate records and impair detection.
Summary
What happened
Log injection in Splunk Web allows remote attackers to corrupt Splunk Enterprise and Splunk Cloud Platform logs via HTTP requests. The /en-US/static/ endpoint writes unvalidated ANSI escape codes from crafted requests into Splunk log files. No authentication is required, but Splunk Web must be enabled; successful injection can poison, forge, or obfuscate records and impair detection.
The record
- CVE
- CVE-2025-20384
- Published
- Dec 3, 2025
- Updated
- Dec 3, 2025
- Vendor
- Splunk, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-117, CAPEC-81, CAPEC-93, CAPEC-268, T1562
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <10.0.1
- Affected versionversion=9.2 <9.2.10
- Affected versionversion=9.3 <9.3.8
- Affected versionversion=9.4 <9.4.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo