# CVE-2026-50751: Check Point Security Gateway Improper Authentication

> Unauthenticated attackers can bypass user authentication in deprecated IKEv1 to establish remote access VPN connections without valid credentials.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Yes, since 8 Jun 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-jqxh-x9f5-wcgw

## What is CVE-2026-50751?

CVE-2026-50751 is a critical authentication bypass vulnerability in checkpoint Quantum Security Gateway, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-50751?

It affects 2 products.


Products: Checkpoint Gaia Embedded, Checkpoint Gaia Os.

## How do I fix CVE-2026-50751?

No fix has been published for CVE-2026-50751 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 11 Jun 2026.

## Is CVE-2026-50751 being exploited?

Yes. Attackers have exploited CVE-2026-50751 in the wild since at least 8 Jun 2026, including in ransomware campaigns.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-Check-Point-CVE-2026-50751 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-Check-Point-CVE-2026-50751
- CVE-2026-50751 (github_poc): https://github.com/0xredash/CVE-2026-50751
- Mitigation scripts for CVE-2026-50751 (github_poc): https://github.com/WadesWeaponShed/CVE-2026-50751-Mitigation-Scripts
- PoC de CVE-2026-50751: bypass de autenticacion IKEv1 en Check Point Remote/Mobile Access. (github_poc): https://github.com/fevar54/CVE-2026-50751---Check-Point-IKEv1-Authentication-Bypass-Exploit
- A web version of the bash scripts wrote for Check Point CVE-2026-50751 and CVE-2026-50752.  This uses a local server to scan and make changes using Check Point Web API (github_poc): https://github.com/WadesWeaponShed/CheckPoint-CVE-Webscanner
- Bypass de autenticación por certificado en la VPN Remote-Access de Check Point (IKEv1). (github_poc): https://github.com/uLl0a/CVE-2026-50751

## Other vulnerabilities in checkpoint Quantum Security Gateway

- [CVE-2026-85102](https://insights.sbomify.com/CVE-2026-85102/): Check Point Multiple Products Improper Certificate Validation (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50751 and fix it if it is affected.

What it is: CVE-2026-50751 is a critical authentication bypass vulnerability in checkpoint Quantum Security Gateway, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-50751 in the wild since at least 8 Jun 2026, including in ransomware campaigns.

Affected product: checkpoint Quantum Security Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50751/ (Markdown: https://insights.sbomify.com/CVE-2026-50751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50751
- OSV: https://osv.dev/vulnerability/CVE-2026-50751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50751/
Summaries are generated and may contain mistakes; the official description above is the record.