Check Point CVE-2026-91843: Unauth Stack Overflow to Root on Management Servers

By George Bailey   Published: 09/17/26   Updated: 10/10/26   3 min read

The box that pushes your firewall policy has a critical unauthenticated stack overflow in the login path. Check Point Security Management / Log servers can be driven to root code execution before a user authenticates, if an attacker can reach them through Trusted Clients.

Vendor says no known exploitation yet. Severity says do not wait for the first public PoC to become your change ticket.

What happened

On September 16, 2026, Check Point disclosed CVE-2026-91843 (CVSS 9.8): a stack overflow in the pre-authentication login process, triggerable with an oversized username. Successful exploitation yields remote root code execution on Security Management, Multi-Domain Management, Log, and Multi-Domain Log Servers, including standalone management+gateway deployments. Hosted Smart-1 Cloud is already fixed.

The vulnerable path runs through the Trusted Clients setting (which hosts may talk to the management server via SmartConsole). Check Point ships an urgent LivePatch via sk1000155. CISA’s CVE assessment recorded exploitation as none at disclosure; the bug was not in the Sep 16 KEV batch. Patch it now anyway: it gives root on the server that pushes firewall policy.

Why it matters

Root on the management server means policy rewrite, administrator takeover, and trust collapse across every gateway that server controls. This is the latest in a string of critical unauthenticated Check Point management-plane flaws since July.

“Automatic updates enabled” is not the same as “LivePatch landed.” Prior urgent packages have rolled out in stages, so verify with cplp list.

What to do first

Details

Hunt / verify

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].