Someone left the castle gate's lock mechanism exposed, and any passerby can jam a skeleton key into it
CVE-2026-85103 is a heap-based buffer overflow in the ASN.1 certificate-parsing code of Check Point's VPN stack. When a Quantum Security Gateway or Security Management Server processes a maliciously crafted X.509 certificate during VPN negotiation, the overflow allows an unauthenticated remote attacker to achieve arbitrary code execution on the appliance. Affected releases are R81.20 (Jumbo Hotfix Take 165 and below), R82 (JHF Take 125 and below), and R82.10 (JHF Take 43 and below). End-of-support versions R80 through R81.10 are also vulnerable. R82.20 is unaffected. Spark Firewall models share the same vulnerable code path.
Check Point rated this CVSS 9.8 CRITICAL, and for once, the vendor score is dead accurate. There is zero friction in the attack path: the VPN listener *must* be internet-facing for the product to function, ASN.1 parsing fires before any authentication occurs, and the attacker needs nothing more than a TCP connection to the VPN port. This is a perimeter appliance RCE with no prerequisites — the 9.8 is earned.
4 steps from start to impact.
Identify exposed VPN endpoint
- Target runs Check Point Quantum Security Gateway or Spark with VPN blade enabled
- VPN port (443/4434) is reachable from the internet
- None — the VPN port is exposed by design for remote access
http.title:"Check Point" or ssl.cert.issuer.cn:"Check Point" queries. Censys similarly indexes these. runZero can enumerate internal Check Point assets.Send malformed X.509 certificate with oversized ASN.1 field
- Ability to initiate a VPN handshake to the target
- Target firmware is in the vulnerable range (R81.20 JHF ≤165, R82 JHF ≤125, R82.10 JHF ≤43)
- No public PoC exists yet — attacker must independently develop the exploit
- Heap layout must be groomed for reliable code execution, which varies across firmware versions
Achieve code execution as root on the gateway
- Successful heap grooming and exploitation
- ASLR and other hardening on Gaia OS may reduce reliability, though embedded appliance ASLR is historically weak
- No public exploit chain yet
/bin/sh from the VPN daemon). Check Point's SmartEvent may log crashes or unexpected daemon restarts as precursors.Pivot to internal network and exfiltrate traffic
- Persistent root access on the gateway
- Network segmentation behind the firewall may limit blast radius
- East-west monitoring (NDR) may detect anomalous traffic from the gateway IP
cpinfo -y all or SmartConsole that the LivePatch took.vpnd, sslvpn), daemon crashes, or core dumps. These are precursor indicators of exploitation attempts. Feed gateway logs to your SIEM with a 15-minute alert SLA.- WAF in front of the VPN — The VPN handshake occurs at the TLS/IKE layer, below the HTTP layer where WAFs operate. A WAF cannot inspect or filter malformed X.509 certificates in a VPN negotiation.
- Disabling Remote Access VPN blade — If you still need site-to-site VPN, the ASN.1 parsing code may still be reachable during IKE negotiation with crafted certificates from a spoofed peer. Only fully disabling all VPN blades eliminates the attack surface, which defeats the purpose of the appliance.
- Network-level IP allowlisting on the VPN port — Impractical for Remote Access VPN deployments where the whole point is to accept connections from arbitrary remote IPs. Only viable if you exclusively use site-to-site with known peer IPs.
The supporting signals.
| In-the-Wild Exploitation | No confirmed exploitation as of 2026-09-09. Disclosed today — monitoring is critical in the next 72 hours. |
|---|---|
| PoC Availability | No public proof-of-concept available. No known private exploit circulating. Heap overflows in ASN.1 parsers on network appliances historically attract rapid researcher attention (cf. Heartbleed, CVE-2024-3400, CVE-2024-24919). |
| EPSS Score | Not yet scored — CVE reserved 2026-09-03, published 2026-09-09. Expect EPSS to populate within 24–48 hours. |
| CISA KEV Status | Not listed as of 2026-09-09. Given the 9.8 CVSS and Check Point's history of KEV additions (CVE-2024-24919 was added within days), watch for imminent KEV listing. |
| CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — Network-accessible, low complexity, no auth, no user interaction. Every impact metric maxed. This is the worst possible base score for Scope:Unchanged. |
| Affected Versions | R81.20 (JHF Take ≤165), R82 (JHF Take ≤125), R82.10 (JHF Take ≤43), plus end-of-support R80–R81.10. Spark Firewalls on same branches also affected. |
| Fixed Versions | R81.20 JHF Take 166+, R82 JHF Take 126+, R82.10 JHF Take 44+. R82.20 is unaffected. LivePatch auto-deploys the fix if enabled. |
| Internet Exposure | Historical scans show 20,000–45,000 internet-facing Check Point gateways (Shodan/FOFA). Censys enumerated ~1,021 Quantum Security Gateways and ~12,321 Quantum Spark gateways in a 2024 scan. The real 2026 number is likely higher. |
| Disclosure Timeline | Reserved 2026-09-03, published 2026-09-09. Check Point advisory sk1000118 released same day. |
| Related Vulnerabilities | CVE-2026-85102 (CWE-295, Improper Certificate Validation) — companion flaw in same VPN negotiation flow, also CVSS 9.8. Both should be patched together. |
Sources.
- SecurityOnline – CVE-2026-85102 & 85103: Check Point VPN Flaws
- THREATINT – CVE-2026-85103
- OffSeq Threat Radar – CVE-2026-85103
- Check Point Advisory sk1000118 (referenced)
- Red Hat Advisory RHSA-2026:25237
- The Record – Check Point Devices Vulnerable
- runZero – Check Point Device Identification
- CVE.org – CVE-2026-85103
Why this verdict
- Unauthenticated pre-auth RCE: The overflow triggers during VPN certificate parsing before any authentication occurs. The attacker needs nothing but a TCP connection to the VPN port — no credentials, no user interaction, no special configuration.
- Role multiplier: Check Point Quantum Security Gateway is *canonically* a network edge appliance. 100% of deployments sit at the internet perimeter. Compromise yields root on the firewall itself — the blast radius is fleet-scale (all traffic, all VPN users, direct L3 path to every internal subnet). If the Management Server is co-located or also vulnerable, the attacker controls the entire Check Point policy infrastructure. This alone sets the verdict floor at CRITICAL.
- Zero effective friction: Unlike vulns that require internal network access or authentication, this one targets a service that *must* be internet-exposed. There are no prerequisites that narrow the reachable population. ASN.1 parsing is deterministic and occurs in every VPN handshake.
- Large attack surface: 20,000–45,000 internet-facing Check Point devices historically indexed. Spark Firewalls in SMB deployments share the same code path, broadening the victim pool.
- Historical precedent: Check Point VPN vulns (CVE-2024-24919, CVE-2026-50751) were weaponized and KEV-listed rapidly. Ransomware affiliates have specifically targeted Check Point appliances. The time-to-exploit for this class of bug is measured in days to weeks, not months.
Why not higher?
There is no severity above CRITICAL. CVSS 9.8 is already the maximum for Scope:Unchanged. The only reason this isn't 10.0 is that Check Point scores it as Scope:Unchanged (compromise of the gateway doesn't automatically change the security scope of other components in the CVSS model, even though operationally it clearly does).
Why not lower?
Every downgrade factor is absent here. There are no authentication requirements, no unusual configuration prerequisites, no limited version range, and no friction from deployment topology — the VPN port is exposed by design. The affected component is the perimeter firewall itself, which is the highest-value network role. No PoC is the only temporal mitigant, and that is a countdown timer, not a structural defense. Check Point appliances have been targeted by ransomware groups (cf. CVE-2024-24919 campaign) and this bug class (pre-auth heap overflow on a network appliance) is the #1 priority for exploit developers.
Crowdsourced verification payload.
Run this script on each Check Point gateway via SSH or console as admin (or expert mode). Example: ssh [email protected] 'bash -s' < check_cve_2026_85103.sh. Requires cpinfo and fw ver commands available in Gaia OS.
#!/bin/bash
# check_cve_2026_85103.sh
# Checks whether a Check Point Gaia gateway is vulnerable to CVE-2026-85103
# Run on the gateway itself in expert mode or via SSH as admin.
# Exit codes: 0 = PATCHED, 1 = VULNERABLE, 2 = UNKNOWN
set -euo pipefail
RESULT="UNKNOWN"
# Get the installed version and JHF take
VERSION=$(fw ver 2>/dev/null | grep -oP 'R\d+\.?\d*' | head -1)
JHF_TAKE=$(cpinfo -y all 2>/dev/null | grep -i 'Jumbo.*Take' | grep -oP '\d+' | tail -1)
if [ -z "$VERSION" ]; then
echo "UNKNOWN - Could not determine Check Point version."
exit 2
fi
echo "Detected version: $VERSION, JHF Take: ${JHF_TAKE:-none}"
case "$VERSION" in
R82.20|R83*)
RESULT="PATCHED"
;;
R82.10)
if [ -n "$JHF_TAKE" ] && [ "$JHF_TAKE" -ge 44 ]; then
RESULT="PATCHED"
else
RESULT="VULNERABLE"
fi
;;
R82)
if [ -n "$JHF_TAKE" ] && [ "$JHF_TAKE" -ge 126 ]; then
RESULT="PATCHED"
else
RESULT="VULNERABLE"
fi
;;
R81.20)
if [ -n "$JHF_TAKE" ] && [ "$JHF_TAKE" -ge 166 ]; then
RESULT="PATCHED"
else
RESULT="VULNERABLE"
fi
;;
R81.10|R81|R80.40|R80.30|R80.20|R80)
RESULT="VULNERABLE"
echo "WARNING: End-of-support version detected. No patch available."
;;
*)
RESULT="UNKNOWN"
;;
esac
# Also check LivePatch status
LIVEPATCH=$(cpinfo -y all 2>/dev/null | grep -i 'livepatch\|LP-' | head -3)
if [ -n "$LIVEPATCH" ]; then
echo "LivePatch info: $LIVEPATCH"
fi
echo "$RESULT"
case "$RESULT" in
PATCHED) exit 0 ;;
VULNERABLE) exit 1 ;;
*) exit 2 ;;
esac