Actively exploitedKnown ransomware use

CVE-2026-50751 Check Point Security Gateway Improper Authentication Vulnerability

Check Point Security Gateway contains an improper authentication vulnerability in IKEv1 key exchange that could allow an unauthenticated remote attacker to bypass user authentication and establish a remote access VPN connection without a valid user password.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 8 Jun 2026.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated Critical severity (CVSS 9.3, scored by CISA).
  • This product type is often exposed to the internet, which is where attackers scan for it first.
  • It has been in the catalogue for 151 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

A logic flow weakness in Remote Access and Mobile Access certificate validation in deprecated IKEv1 key exchange allows an unauthenticated remote attacker to bypass user authentication and establish a remote access VPN connection without a valid user password.

Affected Versions

ProductVersions
checkpoint Quantum Security GatewayR82.10 with Jumbo Hotfix Take 19 or below
R82 with Jumbo Hotfix Take 103 or below
R81.20 with Jumbo Hotfix Take 141 or below
R81.10, R81, and R80.40
checkpoint Spark FirewallsR80.20.X, R81.10.X, and R82.00.X

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Check Point Security Gateway. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2026-50751 and every other exploited flaw on the list.

Check My Exposure