Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Certificate validation bypass in Check Point IKEv1 site-to-site VPN

IdentifiersCVE-2026-50752CWE-295· Improper Certificate Validation

CVE-2026-50752 is a vulnerability in the certificate validation logic of Check Point's deprecated IKEv1 key exchange implementation affecting Security Gateways and Spark Firewall products. Under certain IKEv1 site-to-site VPN configurations that use certificate-based authentication, an unauthenticated attacker in a man-in-the-middle position may be able to bypass certificate validation during VPN establishment. The flaw is described as residing in the same legacy IKEv1 code path investigated during analysis of CVE-2026-50751. Successful exploitation could undermine trust in the peer certificate presented during tunnel negotiation and enable adversary interference with site-to-site VPN communications.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could allow an attacker positioned between VPN peers to defeat certificate-based peer validation for affected IKEv1 site-to-site tunnels. This could enable interception, inspection, and modification of traffic traversing the VPN tunnel, compromising confidentiality and integrity of communications between connected sites. The available reporting states no in-the-wild exploitation has been observed for this CVE at the time of disclosure.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling deprecated IKEv1 for site-to-site VPNs, migrating affected tunnels to IKEv2, and avoiding certificate-based authentication over the vulnerable IKEv1 path. Disable or reconfigure affected site-to-site VPN connections where possible until fixes are applied. More generally, limit opportunities for adversary-in-the-middle positioning through network path hardening and monitoring, though this does not replace patching.

Remediation

Patch, then assume compromise.

Apply the vendor hotfixes and updates released by Check Point for affected Security Gateway and Spark Firewall products. Where affected deployments are on unsupported or end-of-support branches, upgrade to a supported fixed release. Because the issue is in deprecated IKEv1, remediation should also include migrating site-to-site VPN configurations to supported protocols such as IKEv2 where feasible.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Check Point Software TechnologiesSecurity Gatewaysapplication
Check Point Software TechnologiesSpark Firewallapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity15

Community discussion across Reddit, Mastodon, and other social sources.