CVE-2026-20253: Splunk Enterprise unauthenticated file write through the PostgreSQL sidecar chains to RCE, exploited and KEV-listed
An unauthenticated Splunk Enterprise flaw lets attackers write files through the database sidecar, enabled by default on AWS
Defender actions
- Upgrade Splunk Enterprise 10.0.x and 10.2.x to 10.0.7, 10.2.4 or 10.4.0; where an immediate upgrade is impossible and Edge Processor, OpAmp and SPL2 pipelines are unused, set disabled = true under [postgres] in server.conf and restart.
Analysis
CVE-2026-20253 (CVSS 9.8, CWE-306) lets an unauthenticated user create or truncate arbitrary files through a PostgreSQL sidecar service endpoint in Splunk Enterprise 10.0.0 to 10.0.6 and 10.2.0 to 10.2.3; Splunk fixed it in 10.0.7, 10.2.4 and 10.4.0, and 9.4 and earlier are not affected (Splunk SVD-2026-0603). watchTowr showed how the web tier proxies requests to the sidecar's backup and restore API, listening on 127.0.0.1:5435, and chained the file write into code execution (watchTowr Labs, 2026-06-12). The sidecar is installed and enabled by default on Splunk Enterprise on AWS, and not by default on manually installed Windows systems (watchTowr Labs, 2026-06-12). Splunk's workaround is setting disabled = true in the [postgres] stanza of server.conf and restarting, except on instances using Edge Processor, OpAmp or SPL2 data pipelines, which it would break (Splunk SVD-2026-0603).
Cited evidence
In June 2026, the Splunk Product Security Incident Response Team (PSIRT) became aware of limited exploitation of this vulnerability.
Updates2
Splunk updated its advisory to say its PSIRT became aware of limited exploitation in June 2026 (Splunk SVD-2026-0603), and CISA added CVE-2026-20253 to its Known Exploited Vulnerabilities catalog on 2026-06-18 (CISA KEV catalog, 2026-06-18). SecurityWeek reported the exploitation days after disclosure (SecurityWeek, 2026-06-19). The fixes have been available since the advisory of 2026-06-10 (Splunk SVD-2026-0603).
Splunk's advisory confirms limited exploitation and CISA's KEV catalog lists the flaw since 2026-06-18 (Splunk SVD-2026-0603) (CISA KEV catalog, 2026-06-18); the table that showed it as unexploited is removed. The fixes date from 2026-06-10, and Splunk's interim measure is disabling the PostgreSQL sidecar in server.conf, not restricting search-job submission (Splunk SVD-2026-0603). No cited source mentions NCSC-NL.
Sources4
Revision history
- Published 2026-06-14-e1d80e78
- Update 2026-06-20-4cfd00ef
Splunk Enterprise CVE-2026-20253 (pre-auth RCE) now under confirmed limited targeted exploitation per Splunk PSIRT and NCSC-NL, patch urgency for SOC SIEM platforms jumps from routine to emergency (§ 4).
Changed: actions cves evidence regions sectors sources tags body
- Correction 2026-10-11T1307Z-audit
The main analysis carried a table, copied from a daily brief, that listed the flaw as not KEV-listed and not exploited, contradicting a later update, along with rows for unrelated CVEs. The June update attributed confirmation to NCSC-NL, dated the fixes to 2026-06-14 instead of 2026-06-10, advised restricting search-job submission instead of Splunk's sidecar workaround, and asserted SOC deployment patterns with no source. The entry is rewritten from Splunk's advisory and watchTowr with the mechanism, default exposure, workaround, detection and takeaway lines, an action, verbatim evidence, a rating and an ATT&CK mapping; the update section is corrected in place.
Changed: title headline summary sectors techniques affected_products cves sources evidence classification actions body
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.