CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2026-50751 remediation guide

checkpoint Quantum Security Gateway, Spark Firewalls, gaia os

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.

Open CVE record
Productcheckpoint Quantum Security Gateway, Spark Firewalls, gaia os
Affected versions>= R82.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, >= R80.20.X, R81.10.X, and R82.00.X, >= r80.40 < r81.20, r81.20, r82, r82.10, >= r80.20.00 < r81.10.17, r81.10.17, >= r80.20.00 < r82.00.10, r82.00.10
Fixed versionsr81.20, r81.10.17, r82.00.10
Priority basisImmediate · CVSS 9.3 · EPSS 82.6%
01

Identify the affected asset

Confirm whether checkpoint Quantum Security Gateway, Spark Firewalls, gaia os is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= R82.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, >= R80.20.X, R81.10.X, and R82.00.X, >= r80.40 < r81.20, r81.20, r82, r82.10, >= r80.20.00 < r81.10.17, r81.10.17, >= r80.20.00 < r82.00.10, r82.00.10. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

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

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.