dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 11 Jun 2026. Known ransomware use
Gaia OsOperating system · Checkpoint

CVE-2026-50751

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A logic flow flaw in Remote Access and Mobile Access VPN certificate validation for the deprecated IKEv1 key exchange protocol allows unauthenticated remote attackers to bypass user authentication and establish VPN connections without providing valid credentials. The vulnerability stems from improper certificate validation logic in the IKEv1 implementation, enabling authentication bypass.

MitigationDisable IKEv1 and enforce IKEv2 for all remote access VPN connections; patch or update the VPN gateway software to the latest version with corrected certificate validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gaia OsOperating system
Affected:>= r80.40, < r81.20= r81.20= r82= r82.10
Gaia EmbeddedOperating system
Affected:>= r80.20.00, < r81.10.17= r81.10.17>= r80.20.00, < r82.00.10= r82.00.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Checkpoint Gaia version
    Run 'cpversion' or check the Gaia portal/SmartConsole for the exact OS version (e.g., r80.40, r81.20, r82, r82.10)
    Affected if The installed version matches any of the following: Gaia Os >= r80.40 but < r81.20, or exactly r81.20, r82, or r82.10; Gaia Embedded >= r80.20.00 but < r81.10.17, or exactly r81.10.17, >= r80.20.00 but < r82.00.10, or exactly r82.00.10
  2. Confirm Remote Access VPN is configured
    Check in SmartConsole under VPN > Remote Access or examine the VPN community settings to verify Remote Access or Mobile Access VPN is enabled
    Affected if Remote Access or Mobile Access VPN is active on the gateway
  3. Verify IKEv1 protocol is enabled for VPN
    Examine the VPN tunnel or Remote Access VPN settings to determine which IKE versions are permitted; look for IKEv1 explicitly enabled or a fallback configuration that allows IKEv1
    Affected if IKEv1 is enabled or permitted as a fallback for Remote Access or Mobile Access VPN connections
  4. Inspect the certificate validation configuration
    Review the VPN certificate settings in SmartConsole or via 'vpn stat' and 'vpn conf' commands to confirm certificate-based authentication is in use for IKEv1
    Affected if Certificate-based authentication is configured for IKEv1 Remote Access VPN

The environment is affected if it runs an affected Gaia OS or Gaia Embedded version AND has IKEv1 enabled for Remote Access or Mobile Access VPN with certificate validation configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch support.checkpoint.com →
Interim mitigation

Disable IKEv1 and enforce IKEv2 for all remote access VPN connections; patch or update the VPN gateway software to the latest version with corrected certificate validation logic.

Recommended fix Moderate confidence

Gaia OS: r82.20 or later; Gaia Embedded: r82.00.20 or later (or latest stable releases)

  1. 1. Identify the current Gaia OS or Gaia Embedded version running on the affected Check Point devices.
  2. 2. Access the Check Point Support Portal (support.checkpoint.com) and download the appropriate fixed version for your platform.
  3. 3. For Gaia OS: Upgrade to r82.20 or later (or the latest available stable release).
  4. 4. For Gaia Embedded: Upgrade to r82.00.20 or later (or the latest available stable release).
  5. 5. Before upgrading, back up the current system configuration.
  6. 6. During the upgrade process, ensure the IKEv1 protocol is disabled or deprecated as part of the remediation, since the vulnerability is in deprecated IKEv1 key exchange.
  7. 7. After upgrade, verify that Remote Access and Mobile Access VPN connections require proper user authentication.
  8. 8. Review VPN logs to confirm the fix is properly applied and no authentication bypass is possible.
Caveat Ensure VPN client configurations are compatible with IKEv2 or the disabled IKEv1 protocol before upgrading; some legacy clients may require configuration updates.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gaia Os Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50751 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data