Cybersecurity
Check Point Firewall Zero-Day: What Indian Firms Must Do
Affix Center · · 6 min read

In short: Attackers are breaking into Check Point gateways by chaining the PHP2Shell flaws in the Mobile Access portal with a Gaia OS root flaw, CVE-2026-123039. Reports from 13 and 14 November 2026 say exploitation began in late October. Indian firms using Check Point should apply the hotfixes, disable unused Mobile Access and check logs for signs of compromise.
What Happened
On 13 November 2026, CSO Online reported that attackers were turning Check Point gateways against the customers they protect. According to that report, Check Point said "a couple of dozen" customers were affected and that exploitation had been taking place since late October 2026.
The attack chain uses two sets of flaws:
- PHP2Shell (CVE-2026-109618 and CVE-2026-109619): unauthenticated remote code execution flaws in PHP, rated CVSS 9.2 in the CSO report. Attackers use them against the Check Point Mobile Access portal for the first foothold. We covered PHP2Shell when it was disclosed in our post on the PHP2Shell PHP vulnerability.
- CVE-2026-123039 (CVSS 7.8): a local privilege escalation flaw in the Gaia OS Dynamic CLI interface. GBHackers, in a report dated 14 November 2026, explains that a root-owned process called dynamic_server listens on a local socket that any local user can write to, and does not check who is calling. That lets an attacker who already has a foothold run commands as root.
GBHackers also reports that the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on 13 November 2026 with a short remediation deadline for US federal agencies. The article notes this detail as reported, so readers should confirm it in CISA's catalog.
What the Attackers Did After Getting In
The CSO Online report describes what happened on affected gateways after root access:
- Web shells hidden in the Mobile Access portal's login page templates.
- Backdoor and proxy malware that survives reboots and can be carried in backups and snapshots.
- Copying of the firewall configuration and changes to logs.
- In some cases, movement over SSH to VMware ESXi hosts and the deployment of a wiper.
This is why the advice goes beyond patching. A patch closes the hole, but it does not remove an attacker who is already inside.
Who Is Affected
According to GBHackers, the affected Gaia releases are R82.20, R82.10, R82 and R81.20, plus the end-of-support releases R81.10 and R81. It lists fixes for the supported releases (R82.20 Take 14, R82.10 Take 52, R82 Take 132 and R81.20 Take 174) and names no fixes for the end-of-support releases. The same report says Spark firewalls and Smart-1 Cloud are not affected, citing CISA. CSO Online lists affected product types including Security Gateways, Security Management Servers, Multi-Domain Security Management and Scalable Platforms.
Always confirm your exact version and the right hotfix in Check Point's own advisory and support portal before acting, as details can be updated.
What It Means for Indian Businesses and Departments
Check Point firewalls are widely used by Indian banks, NBFCs, manufacturers, IT companies and government bodies, often with Mobile Access or remote access VPN turned on for staff. A compromised firewall is serious because it sees all traffic, holds VPN settings and is often trusted by internal systems.
Indian organisations should also remember their reporting duties. CERT-In's directions of April 2022 require specified cyber incidents to be reported to CERT-In within six hours of noticing them. If your checks find signs of compromise, involve your incident response team and legal adviser early. Our CERT-In 6-hour incident reporting checklist explains the basics.
What to Do Now
- Find every Check Point device. List all gateways, management servers and clusters, with their Gaia version and whether Mobile Access is enabled.
- Patch internet-facing Mobile Access gateways first. Apply the CVE-2026-123039 hotfixes from Check Point, starting with devices that expose Mobile Access to the internet.
- Use the vendor workaround if you cannot patch today. CSO Online reports that stopping the dynamic_server process and preventing it from restarting blocks this route, though some CLI commands may stop working. Follow Check Point's guidance on this.
- Disable Mobile Access where it is not used. Remove features nobody needs and keep management interfaces off the internet.
- Check logs for signs of abuse. GBHackers suggests reviewing /var/log/dynamicCli.log for unexpected commands and looking for unknown template files and new persistence on the appliance.
- Assume compromise on exposed devices. If a gateway was exposed since late October, review it carefully, and rebuild from trusted images if you find indicators, since patches do not remove existing attackers.
- Send firewall logs off the device. Forward logs in real time to a system the firewall cannot change, and cut trusted paths from the firewall to VMware ESXi hosts.
- Plan for end-of-support releases. If you run R81.10 or R81, plan an upgrade to a supported release.
For a longer-term view on firewall choice and upkeep, see our guide to next-generation firewalls for small business and our patch management process.
Frequently Asked Questions
Is CVE-2026-123039 remotely exploitable on its own?
No. According to GBHackers, it is a local privilege escalation that needs existing code execution on the device. Attackers get that first through PHP2Shell on the Mobile Access portal, then use this flaw to become root.
Is patching enough?
Patching closes the flaw, but if an attacker was already on the device, they may still have access. Check logs and indicators, and rebuild compromised devices from trusted images.
Do we have to report this to CERT-In?
If you find a reportable cyber incident, CERT-In's 2022 directions require reporting within six hours of noticing it. Check the directions with your adviser to confirm what applies to you.
How Affix Center Can Help
Affix Center can help you list your exposed devices, apply vendor fixes in a planned window, review logs for signs of compromise and set up off-device log monitoring. Our cyber security services in Mumbai cover firewall reviews and incident readiness, and our VAPT services can test your internet-facing systems after patching. To talk to our team, contact us.