Skip to content
Server Security Center
KEVcritical9.8

CVE-2026-20253: Splunk Enterprise Missing Authentication for Critical Function

Splunk Enterprise · listed in the CISA catalog of actively exploited vulnerabilities since 2026-06-18.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
97%
higher than 99.8% of all CVEs
Added to CISA KEV
2026-06-18
US federal due date 2026-06-21
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-20253 explained

CVE-2026-20253 is a missing authentication flaw in Splunk Enterprise. A PostgreSQL sidecar service endpoint lacks authentication controls, so any network-reachable user can create or truncate arbitrary files without credentials. CISA lists it as known to be exploited, which makes prompt patching or mitigation a priority.

Impact

An unauthenticated attacker who can reach the PostgreSQL sidecar service endpoint over the network can create or truncate arbitrary files. No privileges or user interaction are needed, and attack complexity is low. Confidentiality, integrity and availability impacts are all rated high. CISA rates it automatable, meaning attackers can exploit it at scale, and its technical impact as total. CISA also lists it as known to be exploited.

Who is affected

Splunk Enterprise versions ≥ 10.0, < 10.0.7 and ≥ 10.2, < 10.2.4 are affected. The fix is in 10.0.7 and 10.2.4. According to the description, Splunk Enterprise versions 9.4 and earlier are not affected.

Written with AI from the data on this page and checked against it automatically.

Official description

In Splunk Enterprise 10.2 versions below 10.2.4 and 10 versions below 10.0.7, an unauthenticated user could create or truncate arbitrary files through a PostgreSQL sidecar service endpoint. The vulnerability exists because the PostgreSQL sidecar service endpoint lacks authentication controls, allowing any network-reachable user to invoke file operations without credentials.

Splunk Enterprise versions 9.4 and earlier are not affected. If you cannot immediately upgrade to a fixed version, you can mitigate this vulnerability by disabling the PostgreSQL sidecar service.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Splunk Enterprise
    Affected
    • ≥ 10.0, < 10.0.7
    • ≥ 10.2, < 10.2.4
    Fixed in
    • 10.0.7
    • 10.2.4

How to fix it

What to do

  1. Upgrade Splunk Enterprise 10.0 to 10.0.7 or later, and 10.2 to 10.2.4 or later.
  2. If you cannot upgrade immediately, disable the PostgreSQL sidecar service as the vendor recommends.
  3. Restrict network access to Splunk Enterprise servers so that only trusted hosts can reach their services.
  4. Check affected servers for signs of compromise, such as unexpected or truncated files.
  5. Follow the vendor advisory and CISA's required action, including its forensics triage requirements.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-306 The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources

Questions about CVE-2026-20253

Is Splunk Enterprise 9.4 affected?
No. The description states that Splunk Enterprise versions 9.4 and earlier are not affected. Only the 10.0 branch before 10.0.7 and the 10.2 branch before 10.2.4 are affected.
What can we do if we cannot upgrade right away?
The vendor says you can mitigate the vulnerability by disabling the PostgreSQL sidecar service until you can upgrade to 10.0.7 or 10.2.4. Also limit network access to the server.
Is this vulnerability being exploited?
Yes. CISA added CVE-2026-20253 to its Known Exploited Vulnerabilities catalog on 2026-06-18, with a US federal due date of 2026-06-21. Whether it has been used in ransomware campaigns is unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.