How severe is CVE-2026-50751?

CVE-2026-50751 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-50751?

Affected package information for CVE-2026-50751 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-50751?

No fixed version has been published for CVE-2026-50751 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2026-50751 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-50751 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-50751?

CVE-2026-50751 has an EPSS (Exploit Prediction Scoring System) score of 17.7%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2026-50751 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-50751 (Check Point Security Gateway Improper Authentication Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-06-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-06-11. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-50751?

CVE-2026-50751 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2026-50751?

CVE-2026-50751 affects checkpoint gaia embedded (2 versions, e.g. r81.10.17, r82.00.10); checkpoint gaia os (3 versions, e.g. r81.20, r82, r82.10). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-50751 published, and has it been updated?

CVE-2026-50751 was published on June 8, 2026 and was last updated on June 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2026-50751: Gaia Embedded Improper Authentication (Critical…

EPSS Exploitation Probability

via FIRST.org ↗

17.7%probability of exploitation in next 30 days

Moderate Risk95th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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 Products

2 products · 73 configurations

OS

gaia embeddedcheckpoint

≥ r80.20.00 && < r82.00.10

2 versions

r81.10.17r82.00.10

OS

gaia oscheckpoint

≥ r80.40 && < r81.20

3 versions

r81.20r82r82.10

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-50751 in your stack?

O3 detects CVE-2026-50751 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works