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

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run Splunk Enterprise. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-06-18, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-06-21; treat that as the outer limit, not the target.
• EPSS 96.9%, percentile 99.9: FIRST’s model estimates a 96.9% chance of exploitation activity in the next 30 days, higher than 99.9% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.

What it is

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’s summary

Splunk Enterprise contains a missing authentication for critical function vulnerability which could allow an unauthenticated user to create or truncate arbitrary files through a PostgreSQL sidecar service endpoint.

Weakness type: CWE-306.

Product: Splunk Enterprise · Assigned by: cisco · Published: 2026-06-10

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2026-06-18; federal due date 2026-06-21. Known ransomware use: Unknown.
• CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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 SSVC assessment: exploitation active, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 96.94% probability of exploitation activity in the next 30 days; percentile 99.9.

Timeline

• 2026-06-10 — CVE record published by cisco
• 2026-06-18 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2026-06-19 — CVE record last updated
• 2026-06-21 — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (advisory.splunk.com) advisory.splunk.com

Vulnerability records

1. CVE.org record CVE-2026-20253 cve.org
2. NVD entry CVE-2026-20253 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov
2. Listed in CISA KEV notes (cisa.gov) cisa.gov
3. Listed in CISA KEV notes (cisa.gov) cisa.gov

Other references from the CVE record and advisory

1. labs.watchtowr.com labs.watchtowr.com

All exploited Splunk vulnerabilities · Today’s Security Digest