An authenticated local process with low privileges can reach a permissive control interface and obtain root command execution.Check Point scores the issue 7.8 High under CVSS 3.1. Its research describes confirmed use after attackers first gained access through a vulnerable Mobile Access portal. For related product information, see Brandefense's vulnerability intelligence platform.
What it allows
How Does CVE-2026-123039 Reach Root?
Check Point's CVE record says DynamicCLI runs as root and accepts local connections through a control socket that other local processes can access. It does not authenticate the connecting process before executing its command. The weakness therefore needs an authenticated local user or process; it is not a standalone remote entry point.
In Check Point Research's investigated intrusion, the attacker first used PHP2Shell against a Mobile Access portal. The attacker then used CVE-2026-123039 to move from the portal service account to root and install persistent access. The PHP initial access was associated with CVE-2026-109618 and CVE-2026-109619; the report does not isolate which PHP flaw each attempt used.
Is CVE-2026-123039 Being Exploited?
Yes. Check Point Research documents use of the DynamicCLI flaw after initial access in its investigation of the October 30 campaign. The report describes a wider November 2 scanning wave, but does not establish that every scanned organization suffered a successful intrusion.
CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on November 13, 2026, with a November 16, 2026, remediation due date for US federal civilian agencies. Brandefense Blackhole counted two dark chat posts mentioning CVE-2026-123039 from August 14 through November 12, 2026; these mentions are research signals, not incident confirmations.
Who is affected
Which Check Point Releases Are Affected by CVE-2026-123039?
Check Point's CVE record names Quantum Security Gateway and Quantum Security Management. For each product, it marks four Gaia OS branches and their listed Jumbo Hotfix Takes as affected. Compare both the release branch and installed Take; a release number alone is insufficient.
| Gaia OS branch | Affected Jumbo Hotfix Take |
|---|---|
| R81.20 | 173 or below |
| R82 | 130 or below |
| R82.10 | 50 or below |
| R82.20 | 10 or below |
The CVE record marks these boundaries as affected; it does not explicitly name a fixed Take. Check Point's linked support article presents a verification wall in the available public copy. Obtain the vendor-confirmed corrective Take for each branch through Check Point support, apply it, and verify the running Take after maintenance.
Prioritize exposed Mobile Access gateways because Check Point documented this entry path in the campaign. For a separate Check Point issue, see the Check Point VPN login bypass profile. A consistent patch management process can record the branch, Take and post-update check for each appliance.
Timeline
- 2026-10-30
Check Point Research observed the first campaign wave against Mobile Access gateways and documented a chain from PHP2Shell initial access to DynamicCLI privilege escalation.
- 2026-11-02
Check Point Research observed a broader second scanning wave across multiple countries.
- 2026-11-12
Check Point Research published its investigation and Check Point published the CVE record with affected Jumbo Hotfix Take boundaries.
- 2026-11-13
CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog, with a 16 November 2026 remediation due date for US federal civilian agencies.
What to do
-
Inventory the two affected product families
Identify Quantum Security Gateway and Quantum Security Management systems. Record each Gaia OS branch, installed Jumbo Hotfix Take and whether a Mobile Access portal is reachable.
-
Apply a vendor-confirmed corrective Take
Use Check Point support to identify the corrective Jumbo Hotfix Take for each affected branch. Apply that update, then verify the running branch and Take against the vendor's current guidance.
-
Investigate gateways with suspicious portal activity
Review Mobile Access service crashes, unexpected portal file changes and unusual privilege transitions from the portal account to root. Check for unexplained persistence and outbound access before closing the incident.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-123039 in Brandefense Atlas
The Atlas record of CVE-2026-123039: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can CVE-2026-123039 be exploited remotely by itself?
The CVE record describes a local flaw requiring an authenticated, low-privilege user or process. Check Point Research observed attackers gaining that foothold through a separate Mobile Access issue.
Is CVE-2026-123039 the same as PHP2Shell?
No. PHP2Shell was the initial-access path associated with two PHP CVEs. CVE-2026-123039 was the subsequent DynamicCLI local privilege escalation to root.
Does the vulnerability affect Quantum Security Management?
Yes. Check Point's CVE record lists Quantum Security Management alongside Quantum Security Gateway, with the same four affected Gaia OS branch and Take boundaries.
Which Jumbo Hotfix Take fixes CVE-2026-123039?
The public CVE record lists affected Take ceilings but does not explicitly name fixed Takes. Confirm the corrective Take for each branch with Check Point support and verify the installed Take afterward.
Sources
- PHP2Shell Exploitation on Check Point GatewayCheck Point Research
- CVE-2026-123039 RecordCheck Point CVE Numbering Authority
- Known Exploited Vulnerabilities CatalogCISA