CVE-2026-20140: Local Privilege Escalation in Splunk Enterprise for Windows via DLL Search-Order Hijacking
CVE-2026-20140 is a high-severity local privilege escalation vulnerability affecting Splunk Enterprise for Windows. The flaw arises from unsafe DLL resolution during Splunk service startup, allowing DLL search-order hijacking. A low-privileged local attacker who can place a malicious DLL in a location that is searched during service initialization may cause the Splunk service to load attacker-controlled code. Because the service starts with elevated privileges on Windows, successful exploitation can result in execution as NT AUTHORITY\SYSTEM. The issue affects Windows deployments only and does not impact non-Windows installations. Reported affected versions include Splunk Enterprise for Windows 10.0.0 through 10.0.2, 9.4.0 through 9.4.7, 9.3.0 through 9.3.8, and 9.2.0 through 9.2.11.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a local attacker with low privileges to escalate to NT AUTHORITY\SYSTEM on the affected Windows host. SYSTEM-level execution can enable full compromise of the host, including disabling security controls, accessing protected data, dumping credentials, modifying Splunk or operating system configuration, establishing persistence, and deploying additional tooling such as ransomware.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce the ability of low-privileged users to create directories or write files in locations that can influence DLL resolution for the Splunk installation, especially on the system drive. Restrict who can restart Splunk services, alert on unexpected service restarts, and monitor for suspicious DLL drops, anomalous file writes near Splunk installation paths, and unusual DLL loading behavior during service startup.
Remediation
Patch, then assume compromise.
Upgrade Splunk Enterprise for Windows to a fixed release. Reported fixed versions are 10.0.3, 9.4.8, 9.3.9, and 9.2.12, with 10.2.0 and later in the 10.2.x branch reported as not affected. Ensure all Windows-based Splunk Enterprise installations are updated to a vendor-fixed version appropriate for the deployed branch.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-20140 exploited in the wild?
- As of Jul 31, 2026, Mallory has no reports of CVE-2026-20140 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-20140?
- As of Jul 31, 2026, Mallory has found no public exploit for CVE-2026-20140.
- Is there a patch for CVE-2026-20140?
- Upgrade Splunk Enterprise for Windows to a fixed release. Reported fixed versions are 10.0.3, 9.4.8, 9.3.9, and 9.2.12, with 10.2.0 and later in the 10.2.x branch reported as not affected.
- How severe is CVE-2026-20140?
- CVE-2026-20140 has a CVSS score of 0.0 (Low) as of Jul 31, 2026.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.