Check Point's CVE-2026-123039 Scores 7.8, but Attackers Chained It Behind a 9.2 Flaw to Reach Root
Security / news
Check Point's CVE-2026-123039 Scores 7.8, but Attackers Chained It Behind a 9.2 Flaw to Reach Root
A local flaw in Gaia's Dynamic CLI service went into CISA's KEV catalog on Nov. 13 after attacks on about two dozen unpatched gateways.

An attacker who already has a foothold on a Check Point Gaia gateway (R81.20, R82, R82.10 or R82.20) can run commands as root through CVE-2026-123039, a local privilege escalation in the Dynamic CLI service that Check Point says was exploited against "a couple of dozen" systems. CISA added it to its Known Exploited Vulnerabilities catalog on 13 November 2026. The fix is the November Jumbo Hotfix.
The score understates the chain
CVE-2026-123039 carries a CVSS score of 7.8 in Check Point's security advisory, published 12 November under the name of Lotem Finkelstein, VP Research at Check Point Research. On its own that rating is fair: the attacker needs local access first. The advisory shows how they got it. Attackers entered through PHP2Shell (CVE-2026-109618 and CVE-2026-109619, rated 9.2), an unauthenticated remote code execution flaw in the Mobile Access Portal, then used the Gaia flaw to reach root and set up persistence.
BleepingComputer quotes Check Point's description of the bug: "The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket." A local user can write a command to that socket and have it executed as root. Chained behind a remote entry point, the 7.8 stops being the number that matters.
| CVE | What it is | CVSS | Exploited |
|---|---|---|---|
| CVE-2026-109618, CVE-2026-109619 | PHP2Shell, unauthenticated RCE via Mobile Access Portal | 9.2 | Yes |
| CVE-2026-123039 | Gaia Dynamic CLI privilege escalation to root | 7.8 | Yes |
| CVE-2026-107484 | Gaia Portal backend privilege escalation, authenticated | 7.3 | No |
| CVE-2026-120490 | Management-to-gateway access via NAT rule | 3.8 | No |
Timeline: October 23 to November 13
The PHP2Shell fix shipped on 23 October, a week before the attacks. Check Point observed exploitation between 30 October and 4 November. The advisory went out on 12 November, and CISA listed CVE-2026-123039 the next day. In its alert CISA names the entry "Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability" and gives no separate due date on the page, pointing to Binding Operational Directive 26-04.
Check Point's scope claim is narrow: "Only a couple of dozen unpatched systems, in a single region, were compromised in the observed incidents." The advisory adds that the activity gave initial access to customer networks and, "in a limited number of cases", destructive activity. BleepingComputer reports that after root, the attackers dropped webshells, installed the TSGA backdoor and TSProxy malware (both previously seen on Ivanti appliances), and in some cases pivoted to a VMware ESXi host and deployed a wiper it does not name. That detail is not in the part of the advisory I read, so treat it as BleepingComputer's account.
Who is affected and what to do
The Gaia flaw affects R82.20, R82.10, R82 and R81.20. PHP2Shell affects Security Gateways with the Mobile Access Portal on R80 through R82.20 and several Spark Firewall branches. Check Point's instruction is to install the November Jumbo Hotfix on all Management Servers and Security Gateways, starting with internet-facing Mobile Access deployments. The advisory gives no build numbers. Until the hotfix is on, BleepingComputer relays a stopgap: stop the dynamic_server process and keep it from restarting.
Check Point lists these indicators of compromise:
- Scanning from 130.94.19[.]204 and 130.94.19[.]168
- PHP session files containing the string
upload_progress_pwn - A process masquerading as a Check Point component, named
CPconfigdaemon - Files with "scanner" or "wiper" in the name under
/tmpor/temp - A ransom-style note referencing "Dream Annexation" with no payment demand
- Gaps in firewall traffic logs after a logging daemon crash
The advisory says no match does not rule out compromise. Because the entry point was patched on 23 October and the attacks began a week later, any gateway that had not taken the October fix by 30 October is the one to inspect first. The November KEV analysis covers how CISA has been setting deadlines this month, and the Java4Shell scoring dispute is a second case this month of one number hiding the real exposure.
What remains unknown: Check Point does not say which region was hit, who is behind it, or why the ESXi wiper reached only some victims. Check Point's own advisory is the place to look for the build numbers once they are published.
Sources
More in Security
- 01Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still OpenHundreds of settings are on from first boot, Microsoft warns Server 2025 workloads may break, and the 33 percent of servers still on 2019 are untouched.
- 02VicOne's 28 Robotics Zero-Days Come From a Sponsored Article With No CVE IDs and No Named ProjectsThe Tokyo security firm's count ran as paid content on IEEE Spectrum and The Robot Report. An independent March paper counted 38 flaws in three named consumer robots.
- 03Synology's Third Critical DSM Advisory in 62 Days Hits OAuth, and the Last Patch Does Not Cover ItCVE-2026-120382 scores 9.8 and needs no login. DSM 7.4 and 7.3 builds ending -2 and -6 fix it; 7.2 and 7.1 have none yet.
- 04Codex's Sandbox Uses Seatbelt, bubblewrap and MXC, and Lets Commands Read Broadly by DefaultOpenAI's Nov. 18 engineering post says writes are confined to the workspace and the network is off, while reads stay wide open.