Loading vulnerability…
CVE-2025-20384 is an input validation flaw affecting Splunk Enterprise before versions 10.0.1, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform before versions 10.1.2507.4, 10.0.2503.6, and 9.3.2411.117.125. An unauthenticated attacker can send specially crafted HTTP requests to the /en-US/static/ web endpoint and inject ANSI escape sequences into Splunk log files. Because the endpoint does not properly validate or neutralize this input before it is written to logs, an attacker may poison, forge, hide, or visually obfuscate log entries. The vulnerability primarily affects the integrity and trustworthiness of security-relevant logging and can interfere with analyst visibility and downstream detection workflows that rely on accurate log content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.