The Circuitry
THE CIRCUITRYYour one-stop source for all tech news
HOMETODAYNEWSFEEDEVENTS
BOOKMARKS
RSS
© 2026 The Circuitry
About UsSourcesContactCorrectionsPrivacy
  • Today
  • Feed
  • Events
  • Saved
Scroll for more
Verification
VERIFIEDConfidence: HIGH
Source identified
Claims cross-referenced
No discrepancies found
Fact-check summary

CISA's addition of CVE-2026-20253 to its KEV catalog with a June 21 patching deadline for agencies is confirmed by official CISA announcements and coverage from The Hacker News and SecurityWeek.

Sourcing
4independent sources

via BleepingComputer

BleepingComputer · track record
69Stories
100%Verified
830d
All sources →
Home/Tech/CISA Directs Federal Agencies to Secure Splunk Enterprise Systems by Sunday
VERIFIEDBy Xavier Rivera· ·2 min read

CISA Directs Federal Agencies to Secure Splunk Enterprise Systems by Sunday

CISA placed CVE-2026-20253 affecting Splunk Enterprise on its KEV catalog after confirmed active exploitation and required federal agencies to install patches by June 21. The unauthenticated flaw permits remote file creation or truncation and potential RCE, while Shadowserver monitors over 1,400 publicly reachable instances.

Source:BleepingComputer
Post
CISA Directs Federal Agencies to Secure Splunk Enterprise Systems by Sunday
TL;DRAI · 60 sec read

CISA adds a Splunk Enterprise vulnerability to its Known Exploited Vulnerabilities catalog and directs federal agencies to patch CVE-2026-20253 by June 21. The flaw permits unauthenticated remote file operations and code execution on versions 10.2.0-10.2.3 and 10.0.0-10.0.6. Active exploitation makes it a priority risk to government systems.

CISA has placed a high-severity Splunk Enterprise vulnerability on its Known Exploited Vulnerabilities catalog following reports of active exploitation and instructed Federal Civilian Executive Branch agencies to apply fixes no later than June 21.

CISA mandates patching for CVE-2026-20253 by Sunday. The agency determined that attackers are actively abusing the flaw and directed FCEB agencies to remediate it by Sunday under Binding Operational Directive 26-04. This represents the first Splunk entry added to the KEV catalog.
This represents the first Splunk entry added to the KEV catalog.
The directive calls on agencies to prioritize remediation according to each vulnerability's exploitation risk. CISA stated this type of flaw is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise. Agencies must evaluate each asset's internet exposure and ensure compliance with BOD 26-04 guidelines.

The vulnerability allows unauthenticated remote file operations. Tracked as CVE-2026-20253, it affects Splunk Enterprise versions 10.2.0 to 10.2.3 and 10.0.0 to 10.0.6. It stems from the PostgreSQL sidecar service endpoint lacking authentication controls, enabling any network-reachable user to create or truncate arbitrary files without credentials.
From The CircuitryThe Feed — live briefs across tech, all day.See what’s happening →
"The vulnerability exists because the PostgreSQL sidecar service endpoint lacks authentication controls, allowing any network-reachable user to invoke file operations without credentials," the Splunk security team said in a security advisory published last week. Security researchers also noted the flaw can enable unauthenticated remote code execution. Fixes were issued on June 10 for versions 10.2 before 10.2.4 and 10.0 before 10.0.7.
CISA stated this type of flaw is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise.
Exploitation details surfaced rapidly after initial disclosure. Splunk issued patches shortly before WatchTowr released a technical analysis along with proof-of-concept exploit code and alerts about remote code execution attacks on June 12. On June 18 the company revised its advisory after learning of limited exploitation occurring in June 2026 and called for prompt upgrades to corrected releases.

Shadowserver tracks more than 1,400 internet-exposed Splunk instances, with 952 located in North America and 223 in Europe. No data exists on how many of those instances remain vulnerable to the ongoing attacks.
Mitigation options exist for systems that cannot be patched immediately. Splunk recommends disabling the PostgreSQL sidecar service to eliminate the attack surface. Administrators should note that this action breaks Edge Processor, OpAmp, or SPL2 data pipelines on affected instances. The agency and vendor continue to emphasize rapid remediation to limit exposure.

EXPERT TAKE

Federal agencies face a hard Sunday deadline under BOD 26-04 while Splunk users outside government should treat the limited wild exploitation as an immediate patching priority to avoid file system manipulation.

Why this mattersAI · ~100 words

Tap a lens to see what this story means for you.

Reader-supported
DonateBuy me a coffee →Follow@thecircuitry_ →Follow@thecircuitry.to →

Reader-supported · The Brief

Liked this? The Brief brings you the whole day in tech, verified, every morning. Two minutes, free forever.

HELP US IMPROVE
From The Circuitry

See what’s happening right now

The Feed runs all day — short, verified briefs the moment they break.

Open the Feed →
From The Circuitry

Follow @thecircuitry_

Every story we publish, as it happens. No noise between.

Follow on X ↗On Bluesky ↗

Reader-supported

The Circuitry is a passion project I've always wanted to build, and I love the work behind it.

Running it costs real money. APIs, hosting, time. To keep improving the site and growing this into something useful for everyone, those costs have to be covered.

Any contribution is appreciated. If not, no pressure. Thanks for reading.

Buy me a coffee
SecuritySplunkCISAVulnerability
More fromBleepingComputer
  • ChainDrop worm compromises over 1,300 npm packages totaling 2 billion downloads

    Tech · 3d
  • Anthropic confirms worldwide Claude outage

    Tech · 9d
  • MCBS breach impacts records of 1.26 million individuals

    Tech · 11d
More inTech
  • Tesla and SpaceX confirm Terafab chip fab in Texas

    Tech · 1d
  • OpenAI Urges Federal Judge to Throw Out Apple's Trade Secrets Complaint

    Tech · 2d
  • Meta introduces Muse Code, its terminal-based coding agent

    Tech · 2d
SupportThe Work

The Circuitry is reader-supported. If you find the daily brief useful, you can buy me a coffee to keep it going.

Buy a coffee →
SubscribeCircuitry Brief

Liked this? The Brief brings you the whole day in tech, verified, every morning. Free forever.

MORE IN TECH

Tesla and SpaceX confirm Terafab chip fab in Texas

Tesla and SpaceX have confirmed Grimes County, Texas as the site for their Terafab semiconductor megafactory, with the first phase costing roughly $16.8 billion. The project targets the largest chip manufacturing facility on the planet to supply over 1 terawatt of compute per year that exceeds current and future global production capacity.

OpenAI Urges Federal Judge to Throw Out Apple's Trade Secrets Complaint

OpenAI has filed a motion asking a federal judge to dismiss Apple's trade secrets lawsuit, describing the claims as meritless. The dispute, which follows a July suit and this week's injunction request from Apple, highlights tensions after their prior partnership on Siri and OpenAI's hardware push.

Meta introduces Muse Code, its terminal-based coding agent

Meta has released an early beta of Muse Code, a terminal-based coding agent driven by the updated Muse Spark 1.2 model and positioned against Anthropic's Claude Code and OpenAI's Codex. Substantially lower rates, including a contributor plan at $0.10 for every million tokens received, may encourage migration away from higher-priced options such as Anthropic's Sonnet 5.