CVE-2026-91843, Check Point Security Management / Multi-Domain Security Management / Log Server: unauthenticated stack overflow in the login process reaches root RCE (CVSS 9.8)
A stack overflow in Check Point's unauthenticated management login reaches root. Patch or restrict management access now
Defender actions
- Apply the CVE-2026-91843 fix to every Check Point Security Management, Multi-Domain Security Management, Log Server and Multi-Domain Log Server now, preferably as a Jumbo Hotfix take that also fixes the exploited CVE-2026-93616 (R82.20 Take 10, R82.10 Take 45, R82 Take 127, R81.20 Take 170, R81.10 Take 192), otherwise as the LivePatch plus the separate CVE-2026-93616 fix (on R82.20, the R82.20 Security Hotfix) (confirm
cplp listin Expert mode shows it armed), and verify no Trusted Client/GUI access to the login interface reaches it from outside the management network.
Analysis
Check Point disclosed CVE-2026-91843 (CVSS 9.8) on 2026-09-16: a stack overflow in the unauthenticated login process to Check Point Security Management Server, Multi-Domain Security Management Server, Log Server and Multi-Domain Log Server lets an attacker who reaches the login interface run arbitrary code remotely as root (Check Point PSIRT, 2026-09-16). Check Point's attack indicator is a failed administrator login for an over-long username (Check Point PSIRT, 2026-09-16). Neither Check Point's advisory nor CERT-FR reports observed exploitation (Check Point PSIRT, 2026-09-16 · CERT-FR CERTFR-2026-AVI-1193, 2026-09-17).
Check Point ships the fix as a LivePatch: administrators with automatic updates enabled per sk175504 are already protected, and cplp list in Expert mode should show the CVE-2026-91843 patch armed on R82.20, R82.10, R82 and R81.20 (Check Point PSIRT, 2026-09-16). The fix is also in the Jumbo Hotfix Accumulator for R82.20 from Take 10, R82.10 from Take 45, R82 from Take 127, R81.20 from Take 170 and the end-of-support R81.10 from Take 192, while Check Point lists no fix for R80.x and R81 (Check Point PSIRT, 2026-09-16). Check Point's mitigation is to limit Trusted Clients (GUI clients) to trusted IP addresses or subnets and never to use "Any" as the client type (Check Point PSIRT, 2026-09-16). The flaw needs no credentials and yields root (Check Point PSIRT, 2026-09-16), so the absence of exploitation reports does not lower the urgency.
Triage: Check Point's advisory for CVE-2026-93616 treats a login with a username over 1,000 characters that coincides with an FWM or MDS core dump as a potential attempt to exploit that flaw (Check Point Support, sk1000171, 2026-09-20). For CVE-2026-91843, Check Point gives only the "Username too long" login failure as its attack indicator (Check Point PSIRT, 2026-09-16).
Cited evidence
A stack overflow during the unauthenticated login process may allow an attacker to run arbitrary code remotely with root privileges.
In SmartConsole, search for Audit and Admin login logs containing the message: "Administrator failed to log in: Username too long".
Updates2
The LivePatch for this flaw does not cover CVE-2026-93616, a separate pre-authentication directory traversal and file upload flaw in Security Management, Multi-Domain Security Management, Log, Multi-Domain Log and SmartEvent servers, for which Check Point says no LivePatch is available (Check Point Support, sk1000171, 2026-09-20). Check Point says it was exploited in a handful of targeted attacks on July 23 (The Hacker News, 2026-09-22). That flaw needs the R82.20 Security Hotfix or a Jumbo Hotfix take (R82.20 Take 10, R82.10 Take 45, R82 Take 127, R81.20 Take 170 or R81.10 Take 192), and these takes also include the CVE-2026-91843 fix (Check Point Support, sk1000171, 2026-09-20). A server that received only this LivePatch is still exposed. R81.10 is fixable through Jumbo Hotfix Take 192, and only R80.x and R81 have no listed fix (Check Point PSIRT, 2026-09-16). Check Point's hunting guidance for CVE-2026-93616 includes searching cpm.elg for login requests with usernames over 1,000 characters and checking for an FWM or MDS core dump at the same time (Check Point Support, sk1000171, 2026-09-20).
R82.20 also has a Jumbo Hotfix route: Check Point lists the CVE-2026-91843 fix in the Jumbo Hotfix Accumulator for R82.20 starting from Take 10 (Check Point PSIRT, 2026-09-16), and that take also fixes the exploited CVE-2026-93616, which the LivePatch does not; on R82.20 the separate R82.20 Security Hotfix is the other fix for CVE-2026-93616 (Check Point Support, sk1000171, 2026-09-20).
Sources5
Revision history
- Published 2026-09-18T0410Z-intel
- Correction 2026-09-30T0639Z-audit
Adds that the LivePatch for this flaw does not fix CVE-2026-93616, a separate pre-authentication flaw in the same management servers that Check Point disclosed on 2026-09-22 as exploited in targeted attacks on July 23, and links that entry. A sentence of editorial narration in the main text is rephrased. The fix now includes the Jumbo Hotfix route, so R81.10 is shown as fixable through Take 192 and only R80.x and R81 as unfixed. An invented benign-lookalike triage discriminator is replaced by Check Point's own hunting checks, the trigger wording is narrowed to what Check Point states, and the sk1000171 advisory is added to the sources. The CVE-2026-93616 product scope and the missing LivePatch now cite Check Point's own advisory, the Triage line names the CVE its core-dump criterion belongs to, the headline no longer states the oversized-username trigger as fact, and an uncited exposure characterization is replaced by Check Point's Trusted Clients mitigation.
Changed: references sources body summary cves actions headline
- Improvement 2026-10-21T0800Z-audit
Check Point lists the Jumbo Hotfix Accumulator for R82.20 from Take 10 as a fix for CVE-2026-91843 that also closes the exploited CVE-2026-93616, so R82.20 administrators are no longer left with the LivePatch alone; the R82.20 Security Hotfix is named as the separate CVE-2026-93616 fix.
Changed: actions body cves sourcing_note title
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.