CVE-2026-20253 — Splunk Enterprise Missing Authentication for Critical Function Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, github)+10
- EPSS 96.9% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — advisory.splunk.com (NIST National Vulnerability Database)
CISA required action CISA
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.
US federal deadline: Jun 21, 2026 — passed 116 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Splunk Splunk, Splunk Splunk Enterprise).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the documented mitigations until a definitive fix is available.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Splunk | Splunk | ≥ 10.0.0 and < 10.0.7≥ 10.2.0 and < 10.2.4 | Vulnerable | NIST National Vulnerability Database |
| Splunk | Splunk Enterprise | ≥ 10.2 and < 10.2.4≥ 10.0 and < 10.0.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | psirt@cisco.com via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | cisco via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@cisco.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- watchtowrlabs/watchTowr-vs-Splunk-CVE-2026-20253 ★ 13 Jun 12, 2026
- CVE-2026-20253 ★ 5 Jun 13, 2026
- CVE-2026-20253 - Splunk Enterprise ★ 0 Jun 14, 2026
- PoC de CVE-2026-20253: RCE pre-autenticacion en Splunk Enterprise. ★ 0 Jun 26, 2026
- POC for CVE-2026-20253 ★ 0 Jun 29, 2026
- Het-Kalariya/CVE-2026-20253 ★ 0 Jul 18, 2026
- ivanesk315/CVE-2026-20253 ★ 0 Sep 10, 2026
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 96.94%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
- Hunt retroactively in logs from before Jun 18, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · splunk/splunk
- Source status changed · Published → Analyzed
- Record published
- Affected products added · splunk/splunk enterprise
- CVSS changed · 9.8
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- advisory.splunk.com/advisories/SVD-2026-0603
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- labs.watchtowr.com/why-use-app-level-auth-when-every-database-has-auth-splunk-enterprise
- labs.watchtowr.com/why-use-app-level-auth-when-every-database-has-auth-splunk-enterprise
- github.com/advisories/GHSA-xgm5-jh99-wc4v
- nvd.nist.gov/vuln/detail/CVE-2026-20253
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise 8d
- Critical CVE-2026-76284 Improper Neutralization in Splunk Enterprise 8d
- Medium CVE-2026-76279 Improper Input Validation of Index Names through the collect Command in Splunk Enterprise 8d
- High CVE-2026-76282 Improper Control of a Resource Through its Lifetime in Splunk Enterprise 8d
- Medium CVE-2026-76280 Incorrect Permission Assignment for App Key Value Store Collections in Splunk Secure Gateway 8d
- Medium CVE-2026-76278 Authorization Bypass in SPL2 Module Permissions in Splunk Enterprise 8d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-20253 is "Splunk Enterprise Missing Authentication for Critical Function Vulnerability", rated Critical. It affects Splunk (Splunk); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 96.94% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.