Threats / Check Point / CVE-2026-50751

CVE-2026-50751 · EUVD no mirror located · GCVE no mirror located Verified 2026-08-10

Check Point Security Gateway vulnerability

Check Point Security Gateway contains an improper authentication vulnerability in IKEv1 key exchange that could allow an unauthenticated remote attacker to bypass user authentication and establish a remote access VPN connection without a va

Verdict

Today item, not a backlog item.

Known-exploited and flagged for ransomware use. If you run an exposed, unpatched instance, assume-breach is the correct posture — not a patch window.

CISA KEV Yes · 2026-06-08⁵Ransomware use Flagged⁵EPSS 0.82554 (verify live)⁶Exploit Weaponized · public PoC⁷CVSS 9.3 (CISA)⁴CISA SSVC Exploitation: active · Automatable: yes · Impact: total⁴

Is it exploitable?

— the evidence, ranked above the score

Exploit available

Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.

vulncheck.com ↗vulncheck.com ↗Confirmed

Reported exploitation

9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

blog.checkpoint.com ↗cisa.gov ↗rapid7.com ↗guidepointsecurity.com ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-08), flagged for known ransomware use.

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.82554 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N) · Affected: Check Point, Security Gateway. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

Weakness (CWE)

Mapped to CWE-287 Improper Authentication — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.

CVE.org ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

Public exploit available

Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.

nuclei ↗Confirmed

WeaknessCWE-287 · Improper AuthenticationAuthentication

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

Ransomware-use flag (CISA)

EPSS probability (FIRST)

Weaponized exploit available (VulnCheck)

9 reported-exploitation source(s)

CVSS 9.3 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping — CNA-assigned (CVE.org)

Public exploit availability

Catalogued by checkpoint (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.

Attacker/business narrative framing pending triage.

Disclosure & credit²

Catalogued by checkpointCNA

Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2026-50751.html"], ["v", "sha256:beea4e8168c3717ce69edb6d5cbabf2802d69672e2d731fb50570dd6c0d35821"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.