CVE-2026-20253
The Splunk web application can proxy requests to the local PostgreSQL API, which does not check credentials. By sending a request to the backup endpoint of that API, an attacker can write empty files anywhere in the file system and with any name by creating a backup without authenticating to a specific database. By using a pg_dump parameter, it is possible to “backup” an external database over the network, for example hosted by the attacker. The same API also contains a restore endpoint that not only allows an attacker to restore the database they dumped, but also to restore a .pgpass file, allowing an attacker to authenticate. This means an attacker can restore attacker-controlled SQL and interact with the local database, which leads to arbitrary file writes, which allows them to execute arbitrary commands.
EPSS 1.73% · 74.7th percentile
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk Enterprise: 10.2 versions below 10.2.4 and 10 versions below 10.0.7 |
Timeline
- CVE Published
- Nov 10, 2022 CrowdSec Sighting
- Mar 9, 2023 CrowdSec Sighting
- Nov 6, 2023 CrowdSec Sighting
- Apr 17, 2025 CrowdSec Sighting
- Apr 27, 2025 CrowdSec Sighting
- Feb 25, 2026 CrowdSec Sighting
- May 13, 2026 CrowdSec Sighting
- Jun 11, 2026 Coalition ESS Score
- Jun 12, 2026 Security Advisory
- Jun 15, 2026 PoC Published
- Jun 18, 2026 CISA KEV Added
References
- https://ccb.belgium.be/advisories/warning-actively-exploited-critical-vulnerability-splunk-enterprise-can-lead-remote-code advisory
- https://advisory.splunk.com/advisories/SVD-2026-0603 vendor
- https://nvd.nist.gov/vuln/detail/CVE-2026-20253 technical
- https://labs.watchtowr.com/why-use-app-level-auth-when-every-database-has-auth-splunk-enterprise-cve-2026-20253-pre-auth-rce/ technical