CVE Intelligence
Skip to main content
CISA KEVRansomwarecriticalAuth Bypasspublic exploit

CVE-2026-50751

User Authentication Bypass in VPN Remote Access and Mobile Access

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.

Published Updated Sources: NVD, checkpoint (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jun 8, 2026

EPSS

83%

ahead of 99.6% of scored CVEs

Affects

checkpoint

5 products listed

CVSS base

9.3

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Quantum Security Gateway to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

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

Federal deadline Jun 11, 2026 — passed 75 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
checkpointQuantum Security GatewayR82.10 with Jumbo Hotfix Take 19 or belowVulnerable
checkpointQuantum Security GatewayR82 with Jumbo Hotfix Take 103 or belowVulnerable
checkpointQuantum Security GatewayR81.20 with Jumbo Hotfix Take 141 or belowVulnerable
checkpointQuantum Security GatewayR81.10, R81, and R80.40Vulnerable
checkpointSpark FirewallsR80.20.X, R81.10.X, and R82.00.XVulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

Low

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9.3CVSS 3.1critical3.94.7CNA, GHSA

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

Weakness & attack patterns

  • CWE-287Improper Authentication

Inferred from the weakness class — not observed against this CVE.

CAPEC-115 · Authentication BypassCAPEC-94 · Adversary in the Middle
  • T1548Abuse Elevation Control Mechanism
  • T1040Network Sniffing
  • T1185Browser Session Hijacking

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

Jun 8, 2026

Federal deadline

Jun 11, 2026

passed 75 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

20

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Quantum Security Gateway, Spark Firewalls.
  • Monitor for scanner or exploit-pattern traffic after 20 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 9.3 (AV:N)

    Aug 4, 2026 · NVD

  3. Added to CISA KEV catalog

    Jun 8, 2026 · CISA

  4. Initial · CVE published

    Jun 8, 2026 · NVD

  5. Added · GHSA-jqxh-x9f5-wcgw published (critical)

    Jun 8, 2026 · GitHub Security Advisory

References

6 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-50751 is User Authentication Bypass in VPN Remote Access and Mobile Access, a critical vulnerability affecting Quantum Security Gateway, Spark Firewalls from checkpoint. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 20 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.3 describes technical severity, while EPSS 83% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.