TL;DR: Apply Check Point's vendor-supplied patches and mitigations immediately; this vulnerability is listed in the CISA Known Exploited Vulnerabilities catalog and carries a CVSS score of 9.8 (Critical).
What Is the Vulnerability?
CVE-2026-85102 is an improper certificate validation vulnerability (classified under CWE-295) present in Check Point's VPN processing logic. During VPN negotiation — either Site-to-Site VPN or Remote Access VPN — the affected products fail to properly validate certificate trust chains. This failure creates a pathway for an unauthenticated remote attacker to supply a maliciously crafted certificate or intercept the trust process and ultimately achieve arbitrary code execution directly on the gateway itself.
The vulnerability was published to the National Vulnerability Database (NVD) on September 9, 2026, and was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on September 22, 2026. Its CVSS v3.1 score is 9.8 (Critical), with the attack vector classified as network-reachable, requiring no privileges and no user interaction.
- CVSS Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CWE: CWE-295 — Improper Certificate Validation
- Impact Triad: High Confidentiality / High Integrity / High Availability
Who and What Is Affected?
The following Check Point products are confirmed affected based on NVD and CISA KEV records:
- Check Point Quantum Security Gateway — when configured with Site-to-Site VPN or Remote Access VPN
- Check Point Spark Firewall — when configured with Site-to-Site VPN or Remote Access VPN
Because the vulnerable code path is exercised during VPN negotiation, any deployment of these products that exposes VPN endpoints to untrusted networks — including the public internet — should be considered at risk. Organizations using these products for remote workforce connectivity or inter-site tunnels are particularly exposed.
Note: The specific firmware, software, or hardware revision ranges affected are not detailed in the available facts. Consult Check Point's official advisory directly for a definitive affected-version list.
What Is the Impact?
Successful exploitation of CVE-2026-85102 would grant an unauthenticated attacker the ability to execute arbitrary code on the Check Point gateway. Because security gateways occupy a privileged position at network perimeters, the downstream consequences are severe:
- Full gateway compromise: An attacker with code execution on the gateway can alter firewall rules, disable inspection, or pivot deeper into internal networks.
- Confidentiality breach: VPN traffic flowing through the gateway — including credentials and sensitive data — could be exposed or captured.
- Integrity loss: Routing policies, VPN tunnels, and security policies could be modified or destroyed.
- Availability impact: The gateway itself could be rendered inoperable, taking down VPN connectivity for all users relying on it.
The CVSS score of 9.8 reflects the absence of any meaningful barrier to exploitation: no authentication, no special privileges, and no victim interaction are required. The attack can be launched remotely over any network path that reaches the gateway's VPN interface.
CISA has added this CVE to the KEV catalog, indicating that exploitation has been observed. All organizations operating the affected products should treat this as an active threat.
What Should You Do Now?
CISA's required action for this KEV entry is explicit: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA's Forensics Triage Requirements. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable."
- Consult Check Point's official advisory immediately. Obtain the specific patched versions and hotfix details from Check Point's support portal or security advisories page. Do not rely on third-party summaries alone.
- Apply patches or mitigations as directed by Check Point. Prioritize internet-facing gateways first. Adhere to the patching timelines required under CISA BOD 26-04 based on each asset's exposure classification.
- Conduct forensic triage per CISA's Forensics Triage Requirements, as referenced in the KEV catalog entry. Because this vulnerability has been exploited, assume that unpatched systems may already be compromised and investigate accordingly before simply patching.
- Restrict VPN endpoint exposure where operationally possible. If patching cannot be completed immediately, consider whether VPN endpoints can be placed behind additional access controls or rate-limited to reduce attack surface while remediation proceeds.
- Audit VPN logs for anomalous certificate negotiation events, unexpected connections, or configuration changes that could indicate prior exploitation.
- Discontinue use of affected products in VPN roles if mitigations are unavailable and the exposure cannot be eliminated, per CISA guidance.
Federal civilian executive branch (FCEB) agencies are bound by BOD 26-04 timelines. All other organizations should treat this as a high-priority remediation given the severity and confirmed exploitation.
How External Security Testing Surfaces This Exposure
Identifying exposure to CVE-2026-85102 through external testing is a valuable complement to internal patch verification. The following testing approaches are relevant from a defensive posture:
- VPN endpoint enumeration: External scanning can identify whether Check Point VPN endpoints are reachable from the internet and confirm whether they respond to IKE/IPsec or SSL-VPN negotiation attempts, establishing the attack surface that needs to be patched.
- Version fingerprinting: Banner responses and protocol-level fingerprinting during VPN handshake can sometimes indicate the product version in use, allowing confirmation of whether a patched or unpatched release is responding.
- Certificate handling probes: Security assessments may include presenting malformed or unexpected certificates during VPN negotiation to observe gateway behavior — strictly in a controlled, authorized test environment — to validate that the vulnerability has been remediated.
- Attack surface mapping: Identifying all public IP addresses and hostnames associated with Check Point gateway products in your environment ensures that no exposed instance is overlooked during the patching process.
External penetration testing and attack surface management practices help validate that remediation is complete and that no shadow or unmanaged instances of the affected product remain reachable from untrusted networks.
Sources & further reading: NVD CVE-2026-85102 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: support.checkpoint.com, blog.checkpoint.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need valid credentials or an existing VPN account to exploit CVE-2026-85102?
No. According to NVD and CISA, the vulnerability can be exploited by an unauthenticated remote attacker. No prior credentials, privileges, or user interaction are required, which is reflected in the CVSS score of 9.8.
Is CVE-2026-85102 being actively exploited in the wild?
Yes. CISA added this vulnerability to its Known Exploited Vulnerabilities (KEV) catalog on September 22, 2026, which indicates that exploitation has been observed. Organizations should treat unpatched gateways as potentially already compromised and follow CISA's Forensics Triage Requirements in addition to applying patches.
Are Check Point gateways only vulnerable if they are internet-facing?
The vulnerability is exploitable over any network path that can reach the gateway's VPN interface. Internet-facing deployments represent the highest-risk scenario because they are reachable by any attacker globally, but gateways reachable from less-trusted internal network segments also carry risk and should be patched. CISA advises stakeholders to evaluate each asset's internet exposure individually.
Where can I find the official patch and detailed remediation guidance?
Check Point's official support portal and security advisories are the authoritative source for patched versions, hotfixes, and step-by-step remediation instructions. The CISA KEV catalog entry for CVE-2026-85102 also references relevant BOD 26-04 and Forensics Triage Requirements URLs. Do not rely solely on third-party summaries — consult Check Point and CISA directly.