← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-20253 exploited? Yes: in CISA KEV since 18 Jun 2026

Gociux · Splunk Enterprise · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-20253, Splunk Enterprise Missing Authentication for Critical Function Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 18 Jun 2026, 8 days after it was published. It affects Splunk Enterprise. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 18 Jun 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.8CVSS 3.1 · critical
US federal due21 Jun 2026BOD 22-01 deadline

What it is

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.

VendorSplunk (1 exploited CVE in KEV)
ProductEnterprise
VulnerabilitySplunk Enterprise Missing Authentication for Critical Function Vulnerability
WeaknessCWE-306
Published10 Jun 2026
Added to KEV18 Jun 2026
Reported by (CNA)cisco

What to do

  1. Check whether you run it. Look for Enterprise in your asset inventory, including appliances and cloud images. Stack check lists every exploited Splunk CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 10 Jun 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Splunk.

References

Questions

Is CVE-2026-20253 being exploited?

Yes. CISA added CVE-2026-20253 to the Known Exploited Vulnerabilities catalog on 18 Jun 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-20253 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-20253?

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. Check Splunk's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Enterprise and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in June 2026 · act-now radar.

Running Splunk in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →