No. CVE-2026-20253
A Splunk Enterprise bug is being used in attacks
Being used now
Yes. Attackers are using this right now.
What to do
Apply the vendor's update. If there is none, stop using it or cut it off from the internet.
- Confirmed in attacks
- Jun 18, 2026
- Product
- Splunk Enterprise
- Attack likelihood, next 30 days
- 97%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
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.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is Splunk Enterprise (CVE-2026-20253) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-20253. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.