On September 22, 2026, Check Point disclosed two critical zero-day vulnerabilities that are under active exploitation. The first vulnerability, CVE-2026-93616, is a CVSS 9.8 path traversal flaw in multiple Check Point management server products. The second, CVE-2026-85102, is a CVSS 9.8 authentication bypass and remote code execution (RCE) vulnerability in Quantum Security Gateway and Spark firewalls. Due to confirmed in-the-wild attacks, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added both vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, mandating federal agencies to apply patches promptly. Check Point has confirmed a "handful of customers" were targeted using CVE-2026-93616, with some attacks dating back to July 2026. A global wave of exploitation attempts against CVE-2026-85102 began around September 12, 2026.
This vulnerability is a pre-authentication path traversal flaw within the web service of affected management servers. An unauthenticated, remote attacker can exploit this by sending a specially crafted request to the server. The service fails to properly sanitize the path, allowing the attacker to access, upload, and execute arbitrary scripts on the server, leading to RCE with high privileges. The attack vector is the management interface, specifically TCP port 19009.
This vulnerability resides in the VPN component of Quantum Security Gateways and Spark firewalls. It stems from an improper validation of certificate data during the VPN negotiation process. An unauthenticated attacker can leverage this flaw to bypass authentication, gain unauthorized access to the gateway, and execute arbitrary code. Exploitation attempts have been observed originating from anonymized infrastructure like VPNs and proxies, indicating a broad and opportunistic attack campaign.
CVE-2026-93616 affects the following products:
CVE-2026-85102 affects the following products:
Both vulnerabilities are confirmed to be actively exploited in the wild. CISA added both CVE-2026-93616 and CVE-2026-85102 to its KEV Catalog on September 22, 2026. Check Point reported that attacks targeting CVE-2026-93616 began as early as July 23, 2026, suggesting some threat actors had access to the exploit for months. Widespread exploitation of CVE-2026-85102 against Spark firewall customers was observed starting September 12, 2026.
The active exploitation of these vulnerabilities, particularly the management server flaw which grants deep network access, poses a critical risk to organizations. Compromise of a security management server can lead to the complete takeover of an organization's security infrastructure.
The following patterns could indicate related activity:
portCVE-2026-93616).url_patternPOST /<vulnerable_endpoint>log_sourceCheck Point Audit Logsnetwork_traffic_patternlog_sourceCheck Point VPN LogsCVE-2026-85102, hunt for anomalous certificate-based logins or failed authentication attempts.Security teams should prioritize investigating any anomalous activity related to Check Point management and VPN infrastructure.
Log Analysis: Ingest and analyze logs from Check Point devices. For CVE-2026-93616, focus on web service access logs on port 19009. Look for requests from untrusted IP addresses or patterns indicative of path traversal (../). For CVE-2026-85102, scrutinize VPN authentication logs for unusual patterns, such as a high volume of failed logins followed by a success from an unknown source, or connections with malformed certificate data. This corresponds to D3FEND techniques like Network Traffic Analysis.
Endpoint Detection: On the management server itself, monitor for the creation of unexpected files, particularly web shells or scripts in web-accessible directories. Track for suspicious child processes spawned by the management web service process. This aligns with File Analysis and Process Analysis.
Network Monitoring: Monitor all network traffic to and from the management server's interface. Any connections originating from external, non-whitelisted IPs should be treated as highly suspicious. Establish a baseline of normal traffic patterns and alert on deviations.
The most effective mitigation is to apply the security updates provided by Check Point immediately.
CVE-2026-93616: Install the R82.20 Security Hotfix or the latest Jumbo Hotfix Accumulator for your respective product version. This is a form of Software Update.CVE-2026-85102: Install the hotfix released on September 9, 2026.If patching is not immediately possible, apply the following compensating controls:
Restrict Access (CVE-2026-93616): Implement strict network access control lists (ACLs) to limit access to the management server's web interface (TCP port 19009) to only a small set of trusted IP addresses, such as dedicated management jump boxes. This is a core principle of Network Isolation.
Network Segmentation: Ensure management interfaces are not exposed to the internet and are on a segregated network segment, isolated from general user traffic. This aligns with the D3FEND countermeasure of Broadcast Domain Isolation.
Applying the vendor-supplied patches is the most critical step to remediate these vulnerabilities.
Mapped D3FEND Techniques:
Restricting network access to the management interface (port 19009) to a trusted management zone significantly reduces the attack surface.
Mapped D3FEND Techniques:
Use firewalls or other network security controls to block all traffic to the management interface from untrusted sources.
Mapped D3FEND Techniques:
Organizations must prioritize the immediate deployment of the hotfixes provided by Check Point for both CVE-2026-93616 and CVE-2026-85102. Given that both are actively exploited zero-days, patching should be treated as an emergency change. For CVE-2026-93616, this involves applying the R82.20 Security Hotfix or the latest Jumbo Hotfix Accumulator. For CVE-2026-85102, the fix released on September 9 is required. Use a phased deployment approach, starting with a small number of non-critical systems to test for operational impact, followed by a rapid rollout to all internet-facing and critical production systems. Utilize automated patch management systems to ensure complete coverage and verify successful installation on all affected assets. This is the only definitive way to remediate the underlying flaws.
As a critical compensating control for CVE-2026-93616, organizations must implement strict inbound traffic filtering for the Check Point management interface on TCP port 19009. This interface should never be exposed to the public internet. Configure perimeter firewalls and network ACLs to deny all inbound connections to this port by default. Create an explicit allow rule for a very limited set of trusted IP addresses, such as a dedicated bastion host or a secure management VLAN. This 'deny-by-default' posture drastically reduces the attack surface, preventing remote, unauthenticated attackers from reaching the vulnerable service. Regularly audit these firewall rules to ensure they remain effective and have not been inadvertently relaxed.
Deploy network monitoring tools to analyze traffic to and from Check Point management servers and VPN gateways. For CVE-2026-93616, security teams should create detection rules that alert on any external connection attempts to TCP port 19009. For CVE-2026-85102, monitor for unusual patterns in VPN negotiation traffic, such as malformed certificate exchanges or a high rate of authentication failures from a single source. Furthermore, monitor for any anomalous outbound connections originating from the management server itself, as this could be a sign of a successful compromise and C2 communication. Baselining normal traffic patterns is essential for identifying these deviations.
Earliest observed attack exploiting CVE-2026-93616 against a Check Point customer.
Check Point releases initial patch for CVE-2026-85102, with no evidence of exploitation at the time.
Check Point observes a wave of global exploitation attempts for CVE-2026-85102 against Spark customers.
CISA adds CVE-2026-93616 and CVE-2026-85102 to its Known Exploited Vulnerabilities (KEV) catalog.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.