# Check Point Security Gateway VPN Flaw Is Under Active Attack

- **Canonical URL:** https://www.probackend.com/active-vulnerability-exploitation/check-point-security-gateway-vpn-flaw-is-under-active-attack
- **Section:** Vulnerabilities & Exploits
- **Published:** 2026-11-17
- **Summary:** Check Point confirms active exploitation of CVE-2026-85102 in Security Gateway VPN. Review exposure, vendor remediation, and incident-response steps.

---

## Check Point VPN vulnerability: what’s happening

Check Point has confirmed active exploitation of CVE-2026-85102, a pre-authentication remote code execution vulnerability affecting its Security Gateway VPN. That makes this an incident-response issue, not a theoretical patching exercise: an attacker may be able to reach the vulnerable service without first authenticating. The vendor’s advisory calls for action, and BleepingComputer reports the exploitation confirmation. ([Check Point advisory](https://blog.checkpoint.com/security/security-advisory-action-required-active-exploitation-of-cve-2026-85102-and-a-management-pre-authentication-vulnerability-cve-2026-93616/); [BleepingComputer](https://www.bleepingcomputer.com/news/security/check-point-warns-of-hackers-exploiting-security-gateway-vpn-rce-flaw/))

The key distinction is scope. CVE-2026-85102 concerns VPN functionality on Security Gateways. Check Point’s advisory also discusses a separate Management pre-authentication vulnerability, CVE-2026-93616. Don’t treat those identifiers as interchangeable, and don’t assume that guidance for one automatically resolves the other. Check the vendor advisory for the affected products and remediation that match your own deployment.

An externally reachable gateway deserves priority. Pre-authentication remote code execution can expose a device before the normal sign-in boundary; that is why a routine “we’ll patch next cycle” response is the wrong call here. Verify exposure, follow the applicable vendor fix, and look for evidence of access rather than presuming that a successful update settles the incident.

## What administrators should establish first

Start with an inventory, not guesswork. Identify every Check Point Security Gateway in service, its software version and hotfix level, and whether VPN services are enabled or reachable from the internet. Include appliances that are managed by another team or provider; they still need an owner and a decision.

Then compare each device against the affected-version and fix instructions in Check Point’s advisory. The supplied advisory includes specific remediation material and links to supporting Check Point SK articles. Use those instructions for the relevant release rather than applying an unrelated package or assuming all gateways share the same update path. If applicability is unclear, contact Check Point Support through the channel specified by the vendor.

Record the result per gateway: affected or not, exposed or not, fixed or pending, and who is responsible. A short, accurate list beats a broad statement that “the firewalls are patched.” It also makes it much easier to spot the one appliance that was missed.

## Practical security response

Treat CVE-2026-85102 as urgent. If your gateway is affected, apply the Check Point-recommended fix for its version as soon as operationally possible. Follow the vendor’s installation and mitigation guidance closely, including any prerequisites; don’t improvise a workaround based on a different product or vulnerability. Check Point says customers who need help assessing exposure, applying mitigation, or installing the fix should contact its support team.

If you can’t patch immediately, use the temporary mitigations Check Point specifies for the affected configuration. Keep the gateway under close observation and make a named owner accountable for the remaining work. A mitigation is a bridge, not closure: set a deadline to install the supported fix and confirm the device’s final status afterward.

Investigate the gateway as a potentially targeted system, especially if it was exposed and remained unpatched during the relevant period. Review available device and perimeter logs for unusual access or activity, preserve evidence before making changes that could erase it, and escalate suspicious findings through your incident-response process. The source reporting confirms active exploitation but does not establish that every vulnerable gateway has been compromised; verify your own telemetry rather than assuming either outcome.

Separate the VPN issue from CVE-2026-93616. Check Point’s advisory covers both CVEs, but they are distinct vulnerabilities and may require different assessment and remediation. Review each part of the advisory against the systems you operate, and track the two items independently so a fix for one does not create false confidence about the other.

## Keep remediation tied to the right device

A fix is only useful if it reaches the vulnerable system. Confirm the installed version or hotfix on the gateway itself after deployment, and retain the change record. If the device is part of a cluster or a multi-site estate, verify each relevant member rather than relying on a single successful change report.

Where maintenance constraints prevent immediate action, document the specific blocker, the temporary protection in place, and the next review time. This is a live exploitation warning, so an open-ended exception is not an acceptable plan. Revisit the exposure until the vendor-supported remediation is confirmed.

## References

- [Check Point security advisory: CVE-2026-85102 and CVE-2026-93616](https://blog.checkpoint.com/security/security-advisory-action-required-active-exploitation-of-cve-2026-85102-and-a-management-pre-authentication-vulnerability-cve-2026-93616/)
- [BleepingComputer: Check Point warns of exploitation of Security Gateway VPN RCE flaw](https://www.bleepingcomputer.com/news/security/check-point-warns-of-hackers-exploiting-security-gateway-vpn-rce-flaw/)
- [Check Point support article SK1000117](https://support.checkpoint.com/results/sk/sk1000117)
- [CVE-2026-85102 vulnerability reference](https://www.wiz.io/vulnerability-database/cve/cve-2026-85102)
