Skip to content
Log inRegister

Check Point Gaia CVE-2026-123039: Root Privilege Escalation Exploited After PHP2Shell Attacks

Dr. Abeer Alshammari · Published 11/17/2026

IntermediateProfessionalsCISOsExecutives

Check Point has confirmed that attackers chained a remote code execution flaw on its firewall web portal with a local privilege escalation in Gaia OS (CVE-2026-123039) to gain root on gateways, and CISA lists the Gaia flaw as exploited. Patching is the only remediation Check Point describes.

What happened

Check Point published a security advisory on 12 November 2026 describing active exploitation of its security gateways. Between 30 October and 4 November, attackers first used the PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2) against the Mobile Access Portal for unauthenticated remote code execution. They then used CVE-2026-123039, a local privilege escalation in the Gaia OS Dynamic CLI service (CVSS 7.8), to become root and establish persistence. Secondary coverage reports that CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on 13 November.

Why it matters

A 7.8 score looks modest on its own, but this flaw turned an initial foothold into full control of a security device. The firewall that protects the network became the attacker's entry point. Check Point states that only a couple dozen unpatched systems in a single region were compromised, and that in a limited number of cases the activity was destructive.

Who is affected

CVE-2026-123039 affects Gaia R82.20, R82.10, R82 and R81.20. The PHP2Shell flaws affect Security Gateways with the Mobile Access Portal across R80 to R82.20. Organisations that expose gateway portals to the internet, including many in the MENA region that rely on Check Point perimeter devices, should treat this as a priority.

Technical impact

The chain gives an unauthenticated remote attacker code execution, then root on the gateway. Check Point lists these indicators of compromise: PHP session files containing the string upload_progress_pwn, a process named CPconfigdaemon masquerading as a Check Point component, scanner or wiper tools in temporary directories, a ransom-style note, and gaps in firewall traffic logs. The advisory warns that the absence of these indicators does not rule out compromise.

Governance impact

Perimeter devices sit outside many endpoint monitoring programmes, so a compromise can go unseen. This case shows why asset inventories, patch service levels and logging for security appliances belong in the risk register. A gap in firewall logs is itself a reportable warning sign.

What security teams should do

Install the November Jumbo Hotfix on all management servers and security gateways as soon as operationally possible, starting with internet-facing Mobile Access deployments. The PHP2Shell fix has been available since 23 October and is included in the same hotfix. Hunt for the indicators above, review firewall log continuity, and restrict portal exposure where possible. Check Point's advisory describes no workaround.

What executives should know

This is an actively exploited issue on core network infrastructure, with some destructive outcomes. Ask your security lead for confirmation that the hotfix is installed, that exposed portals have been reviewed, and whether any indicators were found. Treat an unpatched gateway as an open incident risk, not routine maintenance.

Sources: Check Point security advisory (blog.checkpoint.com, opened and read), plus secondary coverage from Ciphers Security for the CISA KEV listing. CISA's own catalog page could not be opened during verification, so the KEV date is attributed to secondary reporting.

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights