What is CVE-2026-50751?

CVE-2026-50751 is User Authentication Bypass in VPN Remote Access and Mobile Access. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-287 Improper Authentication.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

22 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-50751 using CVSS 9.3, EPSS 84%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: UTA0533 (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

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. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalAuth Bypasspublic exploit

CVE-2026-50751

CVE-2026-50751 — User Authentication Bypass in VPN Remote Access and Mobile Access

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-50751 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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 Jun 8, 2026Updated Aug 4, 2026Sources: NVD, checkpoint (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

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

84%

ahead of 99.7% 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 97 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.

Vendor	Product	Versions	Status
checkpoint	Quantum Security Gateway	R82.10 with Jumbo Hotfix Take 19 or below	Vulnerable
checkpoint	Quantum Security Gateway	R82 with Jumbo Hotfix Take 103 or below	Vulnerable
checkpoint	Quantum Security Gateway	R81.20 with Jumbo Hotfix Take 141 or below	Vulnerable
checkpoint	Quantum Security Gateway	R81.10, R81, and R80.40	Vulnerable
checkpoint	Spark Firewalls	R80.20.X, R81.10.X, and R82.00.X	Vulnerable

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.

Score	Version	Severity	Expl.	Impact	Source
9.3	CVSS 3.1	critical	3.9	4.7	CNA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-287 · Improper Authentication

Read Application Data
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands

Mitigation: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.::

Weakness & attack patterns

CWE-287Improper Authentication

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-114 · Authentication AbuseCAPEC-115 · Authentication BypassCAPEC-151 · Identity SpoofingCAPEC-194 · Fake the Source of DataCAPEC-22 · Exploiting Trust in ClientCAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-593 · Session HijackingCAPEC-633 · Token ImpersonationCAPEC-650 · Upload a Web Shell to a Web ServerCAPEC-94 · Man in the Middle Attack

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.

CISAThat month →

Listed

Jun 8, 2026

Federal deadline

Jun 11, 2026

passed 97 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

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

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 22 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

UTA0533

ip38.60.157.13995
TweetFeed General · Nov 12, 2025
ip38.54.107.16793
TweetFeed General · Nov 12, 2025
ip38.54.88.20181
TweetFeed General · Nov 12, 2025
ip144.208.127.15588
SOCRadar-APT Feed · Oct 27, 2023
ip162.33.177.10195
AbuseIPDB Hourly Update · Jun 8, 2026

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

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

2026
Cve is exploited e4zyy/Project-CVE-2026-50751
Aug 28, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.3 (AV:N)
Aug 4, 2026 · NVD
Added to CISA KEV catalog
Jun 8, 2026 · CISA
Initial · CVE published
Jun 8, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

18×SVRS was changedJun 27, 2026 – Aug 29, 2026 · SOCRadar CTI
18×TweetsJun 30, 2026 – Aug 12, 2026 · SOCRadar CTI
1×Github_Repos · Github repository created, e4zyy/Project-CVE-2026-50751Aug 28, 2026 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelJul 17, 2026 · SOCRadar CTI

References

5 on the record

support.checkpoint.com/results/sk/sk185033
Mitigation, Patch, Vendor Advisory, GITHUB, NIST
blog.checkpoint.com/security/check-point-releases-important-hotfix-for-vulnerabilities-in-deprecated-ikev1-vpn-protocol/
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-50751
US Government Resource, NIST
support.checkpoint.com/results/sk/sk185033?_gl=1*1wqeqhc*_gcl_au*MTI1MzE5MjI2LjE3ODA5MzQ1NTM
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-50751
Vendor Advisory

Coverage

21 stories from the feeds we poll

16 more reports on this CVEShowing 5 of 21 · Vendor research and security press coverageUnlock free

Elsewhere on this site

checkpointevery CVE for this vendor
June 2026what else CISA listed
Auth Bypasssame class
CWE-287other pages naming this weakness

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.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic 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: 22 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 84% 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.