CVE-2025-20384 Unauthenticated Log Injection in Splunk Enterprise
Unauthenticated attackers can inject ANSI escape codes into Splunk logs via HTTP requests, compromising log integrity and detection capabilities.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-20384?
CVE-2025-20384 is a medium-severity vulnerability in Splunk Splunk, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In Splunk Enterprise versions below 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.4, 10.0.2503.6, and 9.3.2411.117.125, an unauthenticated attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files due to improper validation at the /en-US/static/ web endpoint. This may allow them to poison, forge, or obfuscate sensitive log data through specially crafted HTTP requests, potentially impacting log integrity and detection capabilities.
Weakness: CWE-117
Which versions are affected by CVE-2025-20384?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2025-20384?
No fix has been published for CVE-2025-20384 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-20384 being exploited?
There is no known exploitation of CVE-2025-20384 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-2x78-c45h-phqx.