Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-85102: Pre-authentication RCE in Check Point Security Gateway VPN Certificate Validation

Published Sep 9, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days13 mentions · peak 6 in a dayToday
CVSS9.8Critical · v3.1
EPSS54.1%99th percentile
CISA KEVYesAdded Sep 22, 2026
In the wildActivePer CISA KEV
Vendor
Check Point Software Technologies
IdentifiersCVE-2026-85102CWE-295 · Improper Certificate Validation

CVE-2026-85102 is an improper certificate-trust validation vulnerability in the VPN negotiation functionality of Check Point Quantum Security Gateway and Spark Firewall. An unauthenticated remote attacker can exploit certificate processing to bypass authentication checks and execute arbitrary code on an affected gateway. Affected deployments use certificate-authenticated Remote Access VPN or Site-to-Site VPN, including applicable DAIP and LSV configurations that implicitly enable certificate authentication. Exclusively pre-shared-key-authenticated VPN configurations and release R82.20 are not affected. The vulnerability has a CVSS v3.1 score of 9.8. Exploitation attempts against Spark customers have been observed globally since September 12, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation can compromise gateway confidentiality, integrity, and availability through unauthenticated arbitrary code execution. Compromise of a gateway can expose sensitive information, permit unauthorized changes, disrupt security and VPN services, and establish an initial foothold on infrastructure controlling access to internal resources. Suspicious internal port and service scanning has been associated with post-authentication activity during exploitation investigations.

Mitigation

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

Until patching is complete, restrict VPN negotiation to trusted peers and necessary client networks. For Site-to-Site VPN, disable VPN implied rules and create explicit rules limiting UDP ports 500 and 4500 to specified peer IP addresses. For Remote Access VPN, permit only required services on UDP ports 500 and 4500 and TCP ports 443 and 80, restricting source client address ranges where possible. These network-rule mitigations do not apply to locally managed Spark Firewalls. Review anomalous certificate-based Mobile Access logins, suspicious authenticated sessions, follow-on internal scanning, and unexpected system changes. Access restrictions reduce exposure but do not replace patching; discontinue affected deployments if adequate mitigations cannot be implemented.

Remediation

Patch, then assume compromise.

Apply the fixes specified in Check Point advisory sk1000117. For supported R81.20, R82, and R82.10 gateways, install LivePatch Take 26 and verify that it is active; an older offline LivePatch package does not provide full coverage. Alternatively, install Jumbo Hotfix Accumulator R81.20 Take 166, R82 Take 126, or R82.10 Take 44, or a later applicable fixed take. R81.10 Take 190 is also identified as a fixed release, but end-of-support deployments should migrate to supported software. Update Spark Firewalls to R81.10.17 build 4968 or R82.00.10 build 2325, or later applicable fixed releases. Investigate previously exposed systems because patching does not remove access established before remediation.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-85102The supplied repository contains two Python command-line programs and a README, totaling 51,146 listed file bytes. No repository URL, revision, or archive size was supplied. Both Python files are truncated, limiting verification of the certificate manipulation, IKE exchange, ESP setup, and cleanup implementations. CVE-2026-85102.py is intended to extract a Check Point ICA certificate, generate a forged user certificate, corrupt the ICA signature, negotiate IKE authentication, and install Linux xfrm state for a full ESP tunnel. It attributes the bypass to libcpcert.so::fwKeyHolder_imp::IsChainTrusted() ignoring a CanonizeChain() failure. Visible support code includes RSA certificate generation, SHA-1 HMAC, AES-CBC, Diffie-Hellman group 2 constants, and Check Point vendor identifiers. The visible IKE header uses version 0x10, indicating IKEv1 despite the README's IKEv2 reference. cp_postex.py wraps tunnel creation, parses Office Mode IP and SPIs from subprocess output, persists state in .cp_postex.json, and offers tunnel status, cleanup, gateway port scanning, and internal host discovery. Its TCP probe explicitly binds the source address. Port 19009 is labeled as a possible CVE-2026-16232 reconnaissance target, but no exploit for that separate vulnerability is shown. Important execution defects are visible. Both programs import systext, which is neither supplied nor documented as a dependency. The helper defaults to poc_vpn_tunnel.py although the supplied exploit has a different filename. In the main exploit, assigning success = ike.run_full_exploit(forge) makes success a local variable throughout main(); earlier success(...) calls therefore raise UnboundLocalError if reached. requests is also imported but omitted from the README's dependency installation instructions. Consequently, the code expresses operational exploit intent but is not operational as supplied. The CVE, advisory, affected-version, and remediation details are repository claims, not independently verified facts. No evidence establishes that this is deliberately fake, and no exfiltration or command-and-control endpoint is visible. Private IP addresses in usage examples are illustrative, not hardcoded victims. Cleanup options reportedly flush xfrm configuration, potentially disrupting unrelated local IPsec tunnels.aduli198 · Disclosed Oct 7, 2026 · python · networkOperational
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 TechnologiesGaia Embeddedoperating_system
Check Point Software TechnologiesGaia Osoperating_system
FAQ

Frequently asked questions

Is CVE-2026-85102 exploited in the wild?
Yes. As of Nov 13, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 22, 2026.
Is there a public exploit for CVE-2026-85102?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-85102, the earliest disclosed Oct 7, 2026.
Is there a patch for CVE-2026-85102?
Apply the fixes specified in Check Point advisory sk1000117. For supported R81.20, R82, and R82.10 gateways, install LivePatch Take 26 and verify that it is active; an older offline LivePatch package does not provide full coverage.
What products are affected by CVE-2026-85102?
Check Point Software Technologies Gaia Embedded and Check Point Software Technologies Gaia Os.
How severe is CVE-2026-85102?
CVE-2026-85102 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 54.1% (99th percentile) as of Nov 13, 2026.
Activity feed

Recent activity

221 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+37 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity155Community discussion across Reddit, Mastodon, and other social sources.