On this page (7 sections)
CVE-2026-123039 is a local privilege escalation flaw in the Gaia OS DynamicCLI daemon used by several Check Point products. SecurityWeek reports that, according to Check Point, attackers used the PHP2Shell vulnerabilities for initial access to Check Point gateways and then used CVE-2026-123039 to gain root. In one wave of attacks a wiper was deployed.
If you administer Check Point gateways or management servers, this deserves a same-day review. CISA has added CVE-2026-123039 to its Known Exploited Vulnerabilities (KEV) catalog. Separately, PHP2Shell is reported to affect all PHP versions from PHP 5 onwards, so PHP site operators should also check their own patch status.
What happened
According to SecurityWeek's summary of Check Point's report, the campaign came in two waves. The first, destructive round began on October 30 and targeted Israeli organizations. The second began on November 2 and targeted organizations in multiple countries, and no destructive activity was observed in it.
PHP2Shell refers to two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, which SecurityWeek says affect all PHP versions from PHP 5 onwards. SecurityWeek states they were patched on October 21, that exploitation started days before the patches, and that mass exploitation followed shortly after. The article does not name fixed PHP releases.
How the attack chain worked
As reported, the attackers used PHP2Shell for initial access, then CVE-2026-123039 to reach root, then deployed PHP webshells and set up persistence. In the first wave, webshells were placed in a directory the Mobile Access portal uses to build login pages. The attackers then reportedly deployed TSGA and TSProxy, variants of the PhiliKit malware framework, did internal asset discovery, moved laterally to a VMware ESXi host and ran a wiper. A note mentioning Dream Security was left behind.
The local privilege escalation flaw
The NVD record describes the Gaia OS DynamicCLI daemon as running as root and listening on a world-writable local socket without authenticating connecting processes. The GitHub advisory names the socket path as /tmp/dynamic_socket and classifies the weakness as CWE-732, Incorrect Permission Assignment for Critical Resource.
In plain terms, any authenticated local user, including an attacker who has already landed through another flaw, can hand the daemon a command and have it run as root. The same advisory lists affected and patched versions as unknown. It also references Check Point's page sk1000362. We did not review that page, so we cannot say what mitigation or version information it contains.
Attribution is unclear
Check Point says the actors worked during typical Chinese working hours and used China-linked malware and infrastructure, but that the wiper and the destructive nature of the attacks do not align with known Chinese cyber operations. In its words, the evidence does not allow a high-confidence assessment. Scenarios it considers plausible include one actor running the whole campaign, an initial access broker, or a false-flag operation. Treat attribution as unconfirmed.
Check Point also notes that neither wave showed a clear sector preference, which it reads as opportunistic initial-access attempts rather than sector-specific targeting.
Who is affected
- Organizations running the Check Point products named in the NVD record: Firewall, Multi-Domain Security Management Server, Scalable Platforms, Security Gateway and Security Management Server.
- In the reported attacks, Check Point Mobile Access gateways (first wave) and Security Gateways (second wave) were targeted. The reporting does not say whether other product roles were hit.
- Operators of PHP applications, for the separate PHP2Shell issue: SecurityWeek says it affects all PHP versions from PHP 5 onwards. The research does not show that PHP sites are at risk because of Check Point appliances.
A local flaw alone needs an account on the appliance first. The reported risk comes from chaining it with a remote flaw that provides that foothold.
What to do now
- Open Check Point's page sk1000362, which the GitHub advisory references, and check whether it gives mitigation or update guidance for your products. Its contents were not reviewed for this article.
- Identify which of the named Check Point products you run and which Gaia OS versions they use, then confirm fixed versions directly with Check Point.
- Limit who holds local accounts on gateways and management servers, since exploitation needs an authenticated local user.
- Look for unexpected PHP files in directories the Mobile Access portal uses to build login pages, and for other unfamiliar files on the appliance.
- Review accounts, scheduled tasks and outbound connections on gateways for signs of persistence or backdoors.
- Check VMware ESXi hosts reachable from any potentially compromised gateway, and confirm backups are offline and restorable.
- If you run PHP applications, confirm your PHP version and check your vendor's advisory for fixes to CVE-2026-109618 and CVE-2026-109619, which SecurityWeek says were reportedly patched on October 21.
- If you find signs of compromise, follow an incident process and preserve evidence before cleaning up.
On a Linux web server you administer, this read-only command lists PHP files modified in the last 14 days under a web root. Replace /var/www with your path; any file you did not expect to change deserves a look.
find /var/www -type f -name '*.php' -mtime -14 -lsDetection and monitoring
Webshell and wiper activity is mostly visible from inside the network, so rely on appliance and host logs first. From the outside you can still watch your public PHP sites for unexpected changes. A free malware scanner gives a quick outside view, and our page on what outside-in detection can and cannot see explains its limits. It cannot see inside a gateway appliance.
For longer-term hygiene, keep PHP and applications on a patch schedule. See our guide to checking whether a website is hacked and, if the answer is yes, website hacked: what to do.
Timeline
| Date | Event |
|---|---|
| Oct 21, 2026 | PHP2Shell patches released (as stated by SecurityWeek) |
| Oct 30, 2026 | First, destructive wave begins, targeting Israeli organizations |
| Nov 2, 2026 | Second wave begins across multiple countries; no destructive activity observed |
| Nov 12, 2026 | CVE-2026-123039 published to the GitHub Advisory Database |
| Nov 13, 2026 | CVE-2026-123039 added to CISA KEV |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
