CVE
CVE-2026-20253
Splunk · Splunk Enterprise
- First Reported
- Jun 13, 2026
- Latest Reported
- Oct 14, 2026
CVE Enrichment
- CVSS
- 9.8 CRITICAL
- EPSS
- 96.94%
- EPSS Percentile
- 99.89%
- CISA KEV
- YES — Known Exploited Vulnerability
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.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 11-Jun-2026 01:16
- Last Modified
- 23-Jul-2026 16:10
- EPSS Date
- 2026-11-10
- CWE
- CWE-306
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:N /
UI:N /
S:U /
C:H /
I:H /
A:H
CISA KEV Details
- Date Added
- 2026-06-18
- Remediation Due
- 2026-06-21
- Known Ransomware Campaign Use
- Unknown
- 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.
- Notes
- https://advisory.splunk.com/advisories/SVD-2026-0603 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-20253
CNA Products / Version Status
- Splunk · Splunk Enterprise
Source: CNA · [email protected]
Default status: unknown
10.2 ≤ version < 10.2.4 — affected (custom)
10.0 ≤ version < 10.0.7 — affected (custom)
Affected Products / Versions
- splunk / splunk
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 10.0.0 · before (exclusive) 10.0.7
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* - splunk / splunk
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 10.2.0 · before (exclusive) 10.2.4
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
References
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (6)
- 8. Splunk Enterprise RCE (CVE-2026-20253) 10 RCE Vulnerabilities Defenders Should Prioritize, Including Exploited Zero-Days
- CVE-2026-20253 Recorded Future Reported 59 High-Impact Vulnerabilities in June, 56 Actively Exploited
- a critical unauthenticated remote code execution (RCE) vulnerability in Splunk Enterprise tracked as CVE-2026-20253 on June 10, 2026. The vulnerability has a CVSS score of 9.8 and stems from missing authentication on Critical Splunk Enterprise Flaw Enables Unauthenticated Remote Code Execution
- CISA has ordered federal agencies to patch a critical Splunk Enterprise flaw, CVE-2026-20253, after confirming it is being actively exploited in attacks. CISA Orders Federal Agencies to Patch Actively Exploited Splunk Flaw
- Resecurity is tracking the exploitation of CVE-2026-20253, a critical pre-authentication Remote Code Execution (RCE) vulnerability affecting Splunk Enterprise's PostgreSQL Sidecar Service. CVE-2026-20253: Pre-Authentication RCE Flaw in Splunk Enterprise
CVE (73)
Malware (6)
People (6)
Threat Actors (4)
MITRE ATT&CK (4)
Vendors (28)
Products (75)
Tools (8)
Industries (6)
Countries (13)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
