Vulnary
← back to the feed
Critical· 9.8actively exploitedofficial fix available

CVE-2026-20253

An unauthenticated attacker can create or delete any file on a Splunk Enterprise system by calling a PostgreSQL sidecar service that lacks authentication. The flaw exists in versions 10.2 and 10 before 10.2.4 and 10.0.7, respectively. Upgrading to a fixed release or disabling the sidecar service stops the attack.

publishedJun 10, 2026
last modifiedJul 23, 2026
sourcesNVD · CISA-KEV
severity · cvss
9.8
critical · how bad it is
exploitation · epss
96%
100th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 22, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Splunk Enterprise 10.2.x (below 10.2.4) and 10.0.x (below 10.0.7). Versions 9.4 and earlier are not affected.

02

Real-world impact

An attacker could write or erase files on the host, potentially installing malware, deleting logs, or corrupting data, leading to loss of confidentiality, integrity, and availability.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability is exploitable over the network with no authentication, and it allows complete compromise of confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Splunk Enterprise to version 10.2.4 or later, or 10.0.7 or later.

NVD-referenced vendor advisory

05

Timeline

  1. Jun 10, 2026 · Jun 10, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jun 18, 2026 · Jun 18, 2026
    Confirmed exploited (CISA KEV)
    CISA added it to the Known Exploited Vulnerabilities catalog — attackers are using it in the wild.
  3. Jun 21, 2026 · Jun 21, 2026
    CISA remediation deadline
    Federal agencies are required to remediate by this date.
  4. Jul 23, 2026 · 7d ago
    Advisory updated
    The NVD record was last revised.
  5. Jul 23, 2026 · 7d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →