Unauthenticated remote root RCE in widely deployed Check Point network security products; enables full compromise and lateral movement across enterprise networks.
CVE-2026-91843
Unauthenticated stack overflow RCE to root in Check Point network products
Is CVE-2026-91843 being exploited?
Not confirmed. CVE-2026-91843 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-91843?
CVE-2026-91843 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-91843?
Yes. A fix has been recorded for CVE-2026-91843. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91843 affect?
CVE-2026-91843 affects Check Point security appliances and management servers (see vendor advisory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91843?
Apply vendor patch immediately; isolate affected devices and restrict admin access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution as root via login stack overflow; full system compromise, persistent access, and network pivoting.
Immediate action required
- affectedR82.10 with Jumbo Hotfix Take 44 or below
- affectedR82 with Jumbo Hotfix Take 126 or below
- affectedR81.20 with Jumbo Hotfix Take 166 or below
- affectedR81.10 (EOS) with Jumbo Hotfix Take 190 or below
- affectedR81 (EOS)
- affectedR80.40 (EOS)
- affectedR80.30 (EOS)
- affectedR80.20 (EOS)
- affectedR80.10 (EOS)
- affectedR80 (EOS)
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- HORKimhab/CVE-2026-91843 · 0 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 17 Sept 2026 (SSVC 2.0.3).
timeline
- 16 Sept 2026Published
- 17 Sept 2026CISA SSVC assessment: exploitation none · 1 day later
- 17 Sept 2026CVE record last updated · same day later
- 18 Sept 2026First proof-of-concept repository on GitHub (unvetted) · 1 day later
- 18 Sept 2026Analysed by vulneraibility.com · 1 day later
- Linksupport.checkpoint.com /results/sk/sk1000155
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.