CISA Gives 3 Days to Agencies to Fix Check Point Vulnerability
CISA adds CVE-2026-123039 to the KEV catalog linked to PHP2Shell for root access on Check Point gateways. The vendor reports exploitation against dozens of clients and wiper attacks on Israeli targets.

The CISA, the cybersecurity agency of the United States government, added CVE-2026-123039, a privilege escalation vulnerability in Check Point products, to the Known Exploited Vulnerabilities (KEV) catalog on Friday, November 13. Federal civilian agencies have until Monday, November 16, to remediate, and the inclusion comes with a requirement for forensic triage under directive BOD 26-04, according to the agency's alert.
The Chain: PHP2Shell at the Door, Root on the Gateway
The vulnerability is in the DynamicCLI component of the Gaia system. A process running as root listens to a local socket with write permissions for any user and does not authenticate who connects, according to Check Point's advisory. Those who already have local access to the equipment can then execute commands as root. The CISA catalog records the flaw as improper permission assignment on a critical resource across multiple products from the vendor.
Local access came from another breach. Attackers entered through the Mobile Access portal by exploiting PHP2Shell, a pair of vulnerabilities in the core of PHP (CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2) that allow remote code execution without authentication. The PHP project released emergency versions on October 21. After gaining root access, the intruders wrote PHP webshells in the directory that the portal uses to render login pages, ensuring persistence. Some technical reports describe the subsequent jump via SSH to VMware ESXi hosts, where files were deleted.
Israel First, the World Next
According to Check Point Research, activity from the address 130.94.19.204 began on October 30, about a week after the patch became available, targeting Israeli organizations. In some of these victims, the attackers executed a Linux wiper named destroy_v6, which leaves a note in Hebrew referencing the Israeli-Palestinian conflict. A second, broader wave targeted organizations in several countries, some of which had already been affected in the first round, but without destructive actions.
Check Point reports active exploitation against "dozens of clients" but has not named any of them. The company also did not make a high-confidence attribution: it claims that the wiper and the focus on Israel do not rule out other explanations and suggests that the destruction may have served as a smokescreen for the operation. The recommended fix is the November Jumbo Hotfix across all management servers and gateways, starting with those exposing Mobile Access to the internet.
Three Countries, Three Takes on the Same Incident
In Israel, home to Check Point and the target of the first wave, the situation is the most severe: perimeter defense equipment used as an entry point, and then to destroy data. It's the scenario that boards typically treat as hypothetical, a compromised firewall turning into a weapon against the very network it protects.
In the United States, the effect comes through the regulatory calendar. The November 16 deadline only obligates the federal government, but the KEV catalog has long served as a priority list for the private sector, cybersecurity insurance, and auditors. A three-day deadline, combined with the requirement for forensic triage, tells teams that simply applying the patch is not enough: they must prove that the equipment was not compromised before the fix.
In the Netherlands, the NCSC-NL, the national cybersecurity center, maintains a public repository on GitHub with operational information about PHP2Shell. This detail matters because the entry vulnerability is not Check Point's: it resides in PHP, a language running on a significant portion of the world's web servers. The Israeli gateway was just the target where the exploitation has been more thoroughly documented so far.
The Gap Between the Hotfix and the Package
The most uncomfortable point for CISOs lies in the timeline. A fix was available about a week before the first recorded attack, yet dozens of clients remained exposed. Many operations apply only Check Point's cumulative packages, the Jumbo Hotfixes, treating individual fixes as exceptions requiring a change window and approval. In this campaign, it was precisely during that gap that the attackers operated. The question this case leaves for risk committees is not whether the vendor fixed it on time, but how long the internal change policy takes to turn a published fix into protected equipment.
Sources
- cisa.govhttps://www.cisa.gov/news-events/alerts/2026/11/13/cisa-adds-two-known-exploited-vulnerabilities-catalog
- research.checkpoint.comhttps://research.checkpoint.com/2026/php2shell-exploitation-on-check-point-gateway/
- blog.checkpoint.comhttps://blog.checkpoint.com/security/security-advisory-active-exploitation-of-php2shell-and-local-privilege-escalation/
- thehackernews.comhttps://thehackernews.com/2026/11/hackers-exploit-php2shell-flaws-in.html
- securityweek.comhttps://www.securityweek.com/php2shell-exploited-in-destructive-check-point-gateway-attacks/
- github.comhttps://github.com/NCSC-NL/php2shell