CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 5 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing5d
- Last KEV listing3d
- Last sighting3mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jun 18, 2026
- EUVDENISA, European Unionlisted Jun 18, 2026
- VulnCheck KEVcommercial researchlisted Jun 15, 2026
- CIRCLaggregator, mirrors the abovelisted Jun 18, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
35 public reports collected from VulnCheck and CIRCL, first on Jun 15, 2026. Each links to its original source. We have not verified them.
Description
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.
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.