Under attack right now? Skip the queue: a responder reads incident reports first.Open an incident

Published
Under
Threat Intelligence
Reference
CVE-2026-20253
Reading time
3 min

CVE-2026-20253: Active Exploitation in Splunk Enterprise

Summary

Critical Splunk Enterprise vulnerability CVE-2026-20253 actively exploited, enabling RCE. Understand the threat, affected versions, and urgent mitigations.

Cover art

CVE-2026-20253: Unauthenticated RCE in Splunk Enterprise Under Active Exploitation

The cybersecurity landscape is currently contending with the active exploitation of CVE-2026-20253, a critical vulnerability impacting Splunk Enterprise. This flaw, rated with a CVSS score of 9.8, enables unauthenticated attackers to execute arbitrary code remotely on affected systems. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-20253 to its Known Exploited Vulnerabilities (KEV) catalog, underscoring the immediate and severe risk it poses to organizations globally. This intelligence brief details the vulnerability, its exploitation mechanics, the threat landscape, and critical mitigation strategies.

Understanding CVE-2026-20253: A Deep Dive

CVE-2026-20253 stems from a critical lack of authentication controls (CWE-306) within a PostgreSQL sidecar service endpoint in Splunk Enterprise. This architectural oversight allows any network-reachable entity to initiate file operations without requiring prior authentication. Splunk publicly disclosed this vulnerability on June 10, 2026, prompting an immediate call to action for all affected users.

Affected Splunk Enterprise Versions

The vulnerability specifically targets and impacts several versions of Splunk Enterprise. It is crucial for organizations to accurately identify if their deployments fall within the affected range:

  • Splunk Enterprise 10.0.0 through 10.0.6 (Fixed in version 10.0.7)

  • Splunk Enterprise 10.2.0 through 10.2.3 (Fixed in version 10.2.4)

Notably, Splunk Enterprise 10.4.x (specifically 10.4.0 and later) and Splunk Cloud Platform are not affected. Splunk Cloud Platform's architecture does not incorporate PostgreSQL sidecars, rendering it immune to this specific vulnerability.

The Exploitation Chain: From Unauthenticated Access to RCE

Cybersecurity researchers, including watchTowr Labs, have published technical details and proof-of-concept (PoC) code illustrating the full exploitation chain for CVE-2026-20253. This public disclosure significantly lowers the barrier for opportunistic threat actors, accelerating the window for widespread attacks. The attack typically unfolds in a multi-stage process:

Stage 1: Initial Connection and Database Dump

Attackers initiate the exploitation by leveraging the /v1/postgres/recovery/backup endpoint. This endpoint, lacking authentication, allows the attacker to connect to an attacker-controlled PostgreSQL database. The critical step here is that the contents of this attacker-controlled database can then be dumped into an arbitrary file on the vulnerable Splunk server.

Stage 2: Loading Malicious Data and Credential Theft

Following the initial dump, the attacker uses the /v1/postgres/recovery/restore endpoint. This allows them to load the previously dumped database contents into the local PostgreSQL instance running on the Splunk server. Crucially, this process can include a

Written by BreachModal analysts · 20 June 2026

Spotted an error in this advisory? Tell us through the disclosure policy and we will correct the record.

After the advisory

Is this in your estate?

Thirty minutes with our team. We will check your exposure to this and the advisories around it, and show you what containment would look like, and who would approve it.