CISA's Check Point Deadline Was November 16. The Fix Was Out Before the Attacks.
If you run a Check Point firewall, or you support clients who do, this is the follow-up to my PHP2Shell Short. The same PHP bug turned into root on internet-facing gateways, and the systems that got hit were the ones that had not been patched.
I re-checked everything below against Check Point's advisory and support articles and CISA's catalog on November 17, 2026.
What happened
On November 12, 2026, Check Point reported active attacks against its Security Gateways. The chain had two steps:
Get in. Attackers used PHP2Shell (CVE-2026-109618 and CVE-2026-109619) in the Mobile Access Portal to run code on the gateway without logging in. Check Point rates PHP2Shell 9.2.
Get root. They then used CVE-2026-123039, a local privilege escalation bug in the Gaia OS Dynamic CLI service, to take full control of the device. Check Point rates it 7.8. On its own it needs a foothold on the box first, which is exactly what PHP2Shell gave them.

Check Point says the activity ran from October 30 to November 4. In its advisory it says a couple of dozen unpatched systems, in a single region, were compromised, and that in a limited number of cases the attack involved destructive activity.
One update since I recorded the Short: Check Point's research team says there were two waves. The first, on October 30, targeted organizations in Israel and included destructive activity against some of them. A broader second wave on November 2 targeted organizations across multiple countries and sectors, with no evidence of destructive activity. So "single region" describes the confirmed compromises, not who was targeted. If your gateway was exposed in that window, do not assume you were out of scope because of where you are.
The timeline, and what "the fix was out" really means
October 23: Check Point released a hotfix for PHP2Shell, the way in.
October 30 to November 4: the attacks.
November 12: Check Point published the advisory and the November Jumbo Hotfix, which includes both the PHP2Shell fix and the fix for the privilege bug.
November 13: CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog.
November 16: the federal deadline to remediate.
Here is the nuance I want MSPs to catch. The fix for the front door, PHP2Shell, was out a week before the attacks started. The fix for the privilege bug arrived with the November Jumbo Hotfix on November 12, after the attacks. The October hotfix carries the PHP fix only.
So if a gateway got the October hotfix and nothing since, the way in is closed, but the root step is still open. The November Jumbo Hotfix closes both.
Where it stands today
As of November 17, 2026:
Exploitation: Check Point lists CVE-2026-123039 as exploited in the wild, and CISA's record marks exploitation as active.
CISA KEV: listed, added November 13, 2026, federal due date November 16, 2026.
Fix: available in the November Jumbo Hotfix. Check Point's guidance has not changed since November 12: install it on all Management Servers and Security Gateways, and prioritize internet-facing Mobile Access deployments.
That federal deadline applies to US federal civilian agencies. CISA also says it encourages all organizations to prioritize the vulnerabilities on its KEV list. I treat that as the standard for our clients too.
Which builds are fixed
Check Point's support article for the privilege bug (sk1000362) names the fixed Jumbo Hotfix takes:
Version | Fixed starting from |
R82.20 | Jumbo Hotfix Take 14 |
R82.10 | Jumbo Hotfix Take 52 |
R82 | Jumbo Hotfix Take 132 |
R81.20 | Jumbo Hotfix Take 174 |
Two things in that article are not in the Short:
Older versions are affected and have no fix. sk1000362 also lists R81 and R81.10 as affected. Both are end of support, and no fixed take is named for them. If you have a gateway on R81.10 or older, the answer is an upgrade to a supported version.
Some products are not affected. Check Point lists Spark Firewalls and Smart-1 Cloud as not affected by the privilege bug.
If you truly cannot patch today, sk1000362 describes an interim mitigation: stopping the Dynamic CLI service, with the trade-off that some Dynamic CLI commands stop working. Treat that as a bridge to the Jumbo Hotfix, not a replacement, and follow the exact steps in the article.
Three ways to protect the firewall in front of your network

One. Install the November Jumbo Hotfix on every Check Point management server and security gateway. Start with any box that exposes Mobile Access to the internet. Confirm the take number against the table above rather than assuming the update landed.
Two. Read the vendor advisory and check the indicators of compromise Check Point published. A patch does not remove an attacker who is already in. Check Point published indicators in its advisory, and sk1000362 explains what to look for in the Dynamic CLI log and how to confirm a box is actually fixed. If anything matches, widen the review to the systems that gateway could reach, not just the gateway.
Three. Ask who patches your firewall, and how fast. The systems that got hit were unpatched, and a fix for the way in had been out for a week. A monthly calendar is too slow when a known exploited bug is on the front door.
Why this matters to MSP owners and executives
The firewall is a computer on the internet. We tend to treat it as the thing that protects everything else, so it gets patched last and watched least. This incident is a reminder that the edge device needs the same patch discipline as anything else, and usually faster.
Know your exposure before the next advisory. Can you list, today, every client gateway that has Mobile Access or another portal open to the internet, and its current Jumbo take? If that takes a day to answer, that is the gap to close.
Separate "exploited" from "scheduled." My advice is a simple rule: when a vendor says a bug is exploited, or CISA adds it to KEV, it leaves the monthly cycle and goes into an emergency change window.
Plan for end of support. A box on R81.10 cannot get this fix. If clients are running out-of-support firewall software, put the upgrade on their roadmap with a date.
Watch and share
If you want a second set of eyes on your firewall patch process, we are happy to talk shop at hello@chibitek.com.
We make IT effortless so you can create, disrupt, and grow!
Sources
Check Point Support, sk1000302: Check Point response to the PHP2Shell vulnerabilities
Check Point, R81.20 Jumbo Hotfix Take 174 release notes (released Nov 12, 2026)
Check Point, R82.20 Jumbo Hotfix Take 14 release notes (released Nov 12, 2026)
Check Point Research, "PHP2Shell Exploitation on Check Point Gateway"
CISA Known Exploited Vulnerabilities catalog, CVE-2026-123039
CISA alert, "CISA Adds Two Known Exploited Vulnerabilities to Catalog" (Nov 13, 2026)
Field Effect, "Check Point Gateway Vulnerabilities Chained in Destructive Attacks" (Nov 16, 2026)








Comments