Back to Blog
2026-06-23· 6 min read

CVE-2026-20253: Critical Splunk Enterprise RCE Vulnerability Under Active Attack

A CVSS 9.8 critical vulnerability in Splunk Enterprise allows unauthenticated remote code execution. CISA confirms active exploitation. Patch immediately to versions 10.2.4 or 10.0.7.

CVE Vulnerability Splunk RCE CISA Enterprise Security

The Vulnerability


**CVE-2026-20253** is a critical (CVSS 9.8) missing authentication vulnerability in Splunk Enterprise that allows unauthenticated remote code execution. The flaw affects the PostgreSQL sidecar service endpoint, which accepts requests without any authentication.


Affected Versions


  • |Version Branch | Vulnerable Range | Fixed Version
  • |----------------|------------------|---------------|

  • |Splunk Enterprise 10.2.x | 10.2.0 – 10.2.3 | 10.2.4
  • |Splunk Enterprise 10.0.x | 10.0.0 – 10.0.6 | 10.0.7
  • |Splunk Enterprise 10.4.x | None | Safe
  • |Splunk Enterprise 9.4 and below | Not affected | N/A

  • **Note**: Splunk Cloud Platform is NOT affected — it doesn't use the PostgreSQL sidecar architecture.


    Timeline of Exploitation


  • |Date | Event
  • |------|-------|

  • |June 10 | Splunk releases patches and discloses CVE-2026-20253
  • |June 12 | watchTowr publishes full RCE proof of concept
  • |June 15 | Active exploitation confirmed in the wild
  • |June 18 | CISA adds to Known Exploited Vulnerabilities catalog
  • |June 21 | Federal agency patch deadline (3 days)

  • The patch-to-exploitation window was just **five days** — and public PoC code was available from day two.


    How the Attack Works


    The vulnerability resides in the PostgreSQL sidecar service that supports Edge Processor, OpAmp, and SPL2 data pipelines. The attack chain:


    1. **Attacker sends unauthenticated request** to the sidecar endpoint

    2. **Connection string injection** redirects PostgreSQL tools to attacker-controlled server

    3. **PostgreSQL's lo_export function** overwrites Python scripts in Splunk directories

    4. **When Splunk re-runs scripts**, attacker code executes with full process privileges


    The sidecar accepts any credentials — including empty strings — making authentication completely bypassed.


    What You Should Do


    Immediate Actions

    1. **Upgrade to patched versions** (10.2.4, 10.0.7, or 10.4.0)

    2. **If patching is delayed**, disable the PostgreSQL sidecar service (temporarily)

    3. **Check for indicators of compromise**:

  • Unexpected files in '/opt/splunk/var/lib/splunk/' or '/opt/splunk/etc/'
  • Outbound connections to unknown IPs on port 5432
  • Anomalous Python script execution

  • Detection Check

    Send a request to the vulnerable endpoint:

  • 400 response = You're vulnerable
  • 401 response = You're patched or not affected

  • Impact Assessment


    Over **1,400 internet-exposed Splunk instances** are tracked by Shadowserver, with more than 950 in North America. If your organization runs Splunk Enterprise on-premises and faces the internet, you're a target.


    Check Your Domain


    Scan your domain for exposed services and security misconfigurations.


    [Free security scan at Vaarta.space](https://vaarta.space)


    Ready to check your domain security?

    Run a free scan to identify potential vulnerabilities.

    Start Free Scan