Check Point addresses a critical remote access vulnerability in its VPN gateways

Check Point has addressed a critical authentication bypass vulnerability, tracked as CVE-2026-50751, affecting its remote access gateways. Rated 9.3 on the CVSS scale, this flaw allowed attackers to establish a VPN session without valid credentials when the deprecated IKEv1 protocol was still enabled. Exploitation of this vulnerability has been active since May 7, 2026, with links to the Qilin ransomware. The Cybersecurity and Infrastructure Security Agency (CISA) has added this vulnerability to its catalog of actively exploited vulnerabilities.

The company released its security bulletin following an investigation that began on June 4, prompted by signs of suspicious activity. CVE-2026-50751 impacts components including Remote Access VPN, Mobile Access, and Spark firewall, spanning various versions from R80.20 to R82.10, some of which are no longer supported. The vulnerability arises from a logic flaw in certificate validation during IKEv1 key exchanges, allowing an unauthenticated attacker to create a remote access connection without credentials.

Importantly, the scope of the vulnerability is limited to initial access. According to Check Point, additional authentication is necessary for an attacker to access internal resources or escalate privileges after establishing a connection. While the gateway opens the door, it does not provide access to the entire information system on its own. This distinction necessitates a focused response: the immediate priority is to secure the entry point, followed by an investigation into any activities that may have occurred after a successful intrusion.

Exploitation Linked to Qilin Ransomware

Check Point Research assesses with moderate confidence that the actors behind these attacks are profit-driven and deploying the Qilin ransomware. Researchers have noted overlaps between Qilin binaries for Linux and attempts to download malicious ELF files from an attacker-controlled infrastructure. The same threat actor is also believed to exploit other VPN vulnerabilities, including those discovered by Palo Alto Networks, Fortinet, and F5.

The operational techniques exhibit characteristics typical of financially motivated groups. The actor utilizes the Tox protocol for communications and relies on virtual private servers hosted by Vultr, Shock Hosting, and Kaupo Cloud. Researchers observed a correlation between the locations of targeted organizations in Taiwan and the servers used, with activity indicating a focus on local infrastructure. So far, exploitation appears limited to a few dozen targeted organizations globally, without signs of a mass campaign.

This is not an isolated incident. Remote access gateways have increasingly become a focal point over recent quarters for ransomware groups due to their direct access to internal networks while being continuously exposed to the internet. Check Point’s association of its own vulnerability with those of Palo Alto Networks, Fortinet, and F5 illustrates a pattern of threat actors industrializing their search for entry points in security devices themselves. For Chief Information Security Officers (CISOs), this situation extends beyond a single vendor’s issues: remote access layers have emerged as a critical attack surface that requires close monitoring, regardless of brand.

Deprecated Protocol Still Active

The vulnerability specifically affects deployments where IKEv1 is still operational, a key exchange protocol that the industry now considers obsolete. Its continued use in production environments underscores the persistence of legacy configurations on edge devices, often outlasting best practices. This flaw aligns edge devices with entry points that ransomware operators prioritize.

The investigation also uncovered a second vulnerability, CVE-2026-50752, rated at 7.4. This flaw also pertains to certificate validation issues in IKEv1 and could, under certain conditions, enable man-in-the-middle attacks on site-to-site VPN links. Check Point has not detected any exploitation of this second vulnerability. The company identified it using BLAST, its AI-assisted code analysis platform, which will likely resonate with CISOs as a signal of the utility of AI in defensive code reviews.

Patch, Disable IKEv1, and Retrospective Audit

Check Point recommends that organizations apply the patch immediately across all affected gateways and has published detailed tech notes, sk185033 and sk185035, outlining vulnerable configurations, mitigation measures via remote access settings, and indicators of compromise. Where immediate patching is not feasible, disabling IKEv1 in favor of IKEv2 is a crucial step to mitigate the attack vector.

Beyond patching, incident response teams should conduct a retrospective audit. Check Point advises prioritizing the examination of logs and configurations from May 7, 2026, the earliest observed exploit date. The audit should include the indicators of compromise provided by the company, such as nine IP addresses associated with the attacking infrastructure and malicious file signatures. Since the deployment of Qilin involves Linux binaries and ELF files downloaded after initial access, the search for signs of compromise should extend beyond gateway logs to any internal Linux servers that may have been reached from the pivot. Given the stealthy nature of post-intrusion techniques, it’s essential to analyze multiple telemetry sources rather than relying on a single alert.

The addition of this vulnerability to CISA’s catalog of actively exploited vulnerabilities on June 8, with a remediation deadline of June 11 for U.S. federal agencies, sets a significant benchmark that French organizations with vulnerability management obligations should heed. The window between disclosure and mass exploitation closes rapidly.

Scroll to Top