Splunk Enterprise Missing Authentication for Critical Function
What to do
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 deadline 2026-06-21 · passed 2 months ago · applies to US federal civilian agencies; used elsewhere as a reference SLA
What happened
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.
Who is affected
Splunk Enterprise. Affected version ranges are listed in the vendor advisory and the NVD entry linked under Sources.
Weakness class: CWE-306.
Timeline
- Added to CISA KEVExploitation in the wild confirmed by CISA
- CISA remediation deadlinepassed 2 months ago
Sources
- NVD entry for CVE-2026-20253 nvd.nist.gov/vuln/detail/CVE-2026-20253
- CISA Known Exploited Vulnerabilities catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
- advisory.splunk.com advisory.splunk.com/advisories/SVD-2026-0603
- cisa.gov www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- cisa.gov www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- nvd.nist.gov nvd.nist.gov/vuln/detail/CVE-2026-20253