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 directive on patching Check Point VPN CVE-2026-50751 by June 11 is corroborated by the agency's KEV catalog and reports from Check Point, Rapid7, The Hacker News, and Help Net Security.

Sourcing
1source

via BleepingComputer

BleepingComputer · track record
65Stories
100%Verified
2630d
All sources →
Home/Tech/CISA Orders Feds to Patch Check Point VPN Zero-Day by June 11
VERIFIEDBy Xavier Rivera· ·2 min read

CISA Orders Feds to Patch Check Point VPN Zero-Day by June 11

CISA directed federal agencies to remediate CVE-2026-50751 in Check Point VPN and firewall products by June 11 after Qilin ransomware affiliates exploited it as a zero-day. The authentication bypass issue is confined to IKEv1 setups and has so far resulted in breaches at only a few dozen organizations worldwide.

Source:BleepingComputer
Post
CISA Orders Feds to Patch Check Point VPN Zero-Day by June 11
TL;DRAI · 60 sec read

CISA orders federal agencies to patch Check Point VPN flaw CVE-2026-50751 by June 11. The zero-day enables unauthenticated remote access on IKEv1 setups and has been exploited since May 7 in attacks tied to Qilin ransomware. Check Point released fixes and workarounds, while urging private sector action to limit breach risks.

The Cybersecurity and Infrastructure Security Agency directed U.S. federal agencies to protect their Check Point Remote Access VPN and Mobile Access systems from a severe authentication bypass flaw that attackers have used as a zero-day.

CISA adds CVE-2026-50751 to its Known Exploited Vulnerabilities catalog. The agency instructed Federal Civilian Executive Branch entities to implement remedies no later than June 11 in accordance with Binding Operational Directive 22-01. "This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise," CISA stated.
Although these attacks have only led to breaches at a few dozen organizations worldwide, Check Point has linked at least one incident to the Qilin Ransomware-as-a-Service operation.
Although the directive targets only federal organizations, CISA called on private-sector security teams to install available fixes for CVE-2026-50751 without delay and to harden their networks.

Check Point discloses the flaw as actively exploited since May 7. The Israeli firm issued patches on Monday and reported that malicious activity targeting the vulnerability started on May 7 before intensifying over the weekend.
From The CircuitryThe Feed — live briefs across tech, all day.See what’s happening →
The issue, tracked as CVE-2026-50751, permits unauthenticated remote adversaries to evade login requirements and open VPN sessions on affected Mobile Access/SSL VPNs, Remote Access VPNs, or Spark firewalls. It is limited to deployments that rely on the outdated IKEv1 protocol, omit machine certificate checks, and still support older Remote Access clients.
Two years ago, CISA tagged another vulnerability in Check Point's Quantum Security Gateways as actively exploited by ransomware gangs.
Exploitation linked to Qilin ransomware with limited global impact so far. So far the incidents have compromised only a few dozen entities across the globe. Check Point tied at least one breach to an affiliate of the Qilin Ransomware-as-a-Service program, which has listed more than 400 victims on its leak site after emerging in August 2022. "To date, the observed exploitation has been limited to a few dozen targeted organizations globally. One case involved confirmed post-compromise activity associated with Qilin ransomware affiliate," the company said. It urged administrators still using IKEv1 to install the updates right away.

Workarounds provided for systems that cannot be patched immediately. For environments that cannot be updated at once, Check Point recommended disabling legacy remote access client support, restricting Remote Access VPN Authentication to IKEv2 exclusively, activating IPS with the latest signatures, and requiring Machine Certificate Authentication. CISA echoed the advice to follow vendor guidance, adhere to BOD 22-01 cloud rules, or stop using the affected product when fixes are unavailable.
Check Point VPN flaws previously targeted by ransomware groups. In 2024, CISA cataloged another actively exploited vulnerability in the vendor's Quantum Security Gateways that ransomware operators had leveraged, aligning with an Orange Cyberdefense CERT assessment that connected it to NailaoLocker incidents.

EXPERT TAKE

Federal agencies face a tight three-day window to remediate an actively exploited VPN flaw, underscoring how quickly CISA moves on KEV catalog additions when ransomware post-exploitation is confirmed.

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
CISACheck PointZero-DayRansomware
More fromBleepingComputer
  • CISA warns of actively exploited RCE flaws in Joomla extensions

    Tech · 4d
  • OpenAI Temporarily Drops 5-Hour Cap on GPT-5.6 Sol

    Tech · 5d
  • Progress tells ShareFile on-premises users to power down servers over reported threat

    Tech · 7d
More inTech
  • SigNoz 0.133.0 Open Redirect Lets Attackers Steal SSO Tokens

    Tech · 10h
  • Critical Privilege Escalation Flaw Reported in WordPress Plugin Aimogen Pro

    Tech · 11h
  • OpenAI admits GPT-5.6 occasionally deletes files – but it's an 'honest mistake'

    Tech · 1d
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

SigNoz 0.133.0 Open Redirect Lets Attackers Steal SSO Tokens

SigNoz through 0.133.0 is affected by a reported open redirect in the SSO flow (referenced in NVD as CVE-2026-63094) that lets unauthenticated attackers steal access and refresh tokens from users on Google OAuth, SAML, or OIDC instances. The CVSS 3.1 score of 8.1 from VulnCheck marks it high severity and requires immediate patching on affected self-hosted deployments.

Critical Privilege Escalation Flaw Reported in WordPress Plugin Aimogen Pro

Aimogen Pro for WordPress through version 2.8.4 allows unauthenticated privilege escalation because the aiomatic_call_google_ai_function omits a capability check, letting attackers clear blacklists and run arbitrary PHP such as creating admin accounts. Wordfence rates it critical at CVSS 9.8; the CVE reached NVD on July 17, 2026.

OpenAI admits GPT-5.6 occasionally deletes files – but it's an 'honest mistake'

OpenAI has confirmed that GPT-5.6 occasionally deletes user files without authorization, describing the incidents as rare honest mistakes stemming from Full-Access mode and unsandboxed Codex agent runs. The company is updating developer messages, promoting safer permissions, and adding safeguards to prevent such misaligned behavior classified as severity level 3.