Skip to content
eastbaycyber

CVE-2026-123039: Check Point Gaia OS Privilege Escalation

CVSS · High
7.8
In CISA KEV
Yes
Published
Nov 18
Patch SLA & TriageVector: Local
Immediate (BOD 22-01 due 2026-11-16)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 7.8
Decode Vector & Sub-Scores →
CVE explainers 9 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-18
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-13. Federal agencies must patch by 2026-11-16.

Everything CISA added on 2026-11-13

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-123039 is a high-severity local privilege-escalation flaw in the Gaia OS DynamicCLI daemon. - A local authenticated user can abuse the world-writable /tmp/dynamic_socket to execute commands as root. - CISA lists the vulnerability in KEV, confirming exploitation in the wild. - Apply the fixed Jumbo Hotfix Accumulator or Check Point’s temporary mitigation immediately.

What Is the Root Cause?

The flaw results from several insecure design and configuration choices operating together. The dynamic_server process runs with root privileges, listens on /tmp/dynamic_socket, and exposes that socket with world-writable permissions. It also does not authenticate or authorize local clients before processing commands.

A local authenticated user does not need to bypass the appliance’s network perimeter to reach the socket. If that user can execute local commands on an affected system, the socket’s permissions allow interaction with the privileged daemon. The daemon then performs the requested operation in its root security context.

The relevant security failures are represented by:

  • CWE-732 — Incorrect Permission Assignment for Critical Resource: the local control socket is world-writable despite controlling a root-privileged service.
  • CWE-862 — Missing Authorization: the daemon does not establish whether the connecting local process is permitted to request privileged operations.

This is a privilege-boundary failure rather than a remote unauthenticated network exploit. Local privilege escalation on a security gateway or management server can still be operationally severe. An attacker who already obtained a low-privilege shell, compromised an administrative account, or gained access through another weakness could use this issue to reach root.

AnalystImpact · assess the risk

What Happened?

CVE-2026-123039 is a Check Point Gaia OS vulnerability affecting multiple Check Point products and release trains. The vulnerable dynamic_server daemon runs as root and accepts connections through a world-writable local Unix socket without authenticating or authorizing the connecting process.

An authenticated local user can submit commands that the daemon executes with root privileges. The issue is especially serious on security gateways and management infrastructure, where root access can expose configuration, credentials, traffic-handling logic, administrative interfaces, and connected systems.

CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on November 13, 2026, with a remediation due date of November 16, 2026.

Field Details
CVE CVE-2026-123039
Vendor Check Point
Affected area Gaia OS DynamicCLI daemon
CVSS base score 7.8, High
Attack vector Local
Authentication / privileges Authenticated local access is required; the vulnerable daemon does not authenticate the connecting local process
Root cause Incorrect permissions and missing authorization, mapped to CWE-732 and CWE-862
Patch available Yes
Exploitation status Confirmed exploited in the wild through CISA KEV listing
Public PoC No verified public proof-of-concept repository was identified in the reviewed primary sources

The exact CVSS vector string was not exposed in the available NVD response. Defenders should not infer missing vector components from the base score alone. The reliable facts are that exploitation requires local access and that the resulting impact can include root-level control.

Analyst’s Take: Treat this as a patching and triage issue, not just a version-checking exercise. KEV status raises the priority, while the lack of a verified public PoC or named campaign limits what defenders can conclude about the specific intrusion path.

For background on related security terminology, see our ransomware response checklist and extended detection and response glossary.

Who Needs to Act?

Check Point identifies affected Gaia OS product releases as:

  • R82.20
  • R82.10
  • R82
  • R81.20
  • R81.10
  • R81

The affected product scope includes Check Point security gateways, Quantum Security Gateway products, Quantum Security Management products, and other Check Point Gaia OS-based products covered by the vendor advisory. Applicability depends on the product type, release train, and installed Jumbo Hotfix Accumulator take.

The vendor identifies the following fixed release levels:

Gaia OS release Fixed Jumbo Hotfix Accumulator
R82.20 Take 14 and later
R82.10 Take 52 and later
R82 Take 132 and later
R81.20 Take 174 and later
R81.10 End of life; the advisory identifies this release as EOS

Organizations should also account for products that Check Point identifies as non-affected. Check Point Spark Firewalls and Smart-1 Cloud are listed as non-affected in the supplied advisory information. Do not extend that status to every Check Point product; verify each appliance and management system against the vendor advisory and inventory.

R81.10 requires special handling because it is identified as end of life. If an organization still operates that release, routine patching should not be treated as a long-term solution. Confirm the vendor-supported remediation path, plan migration to a supported release, and treat the system as a high-priority asset while the transition is pending.

Why Is the CVSS Score 7.8?

The recorded CVSS base score is 7.8 High. The available NVD response did not expose the complete vector string, so the individual metric values cannot be stated reliably. Use the score as a severity indicator, not as evidence for unreported details such as user-interaction requirements or exact impact metric values.

The technical characteristics explain why the issue is high severity despite requiring local access. The vulnerable service executes as root, and successful exploitation can result in complete control of the affected Gaia OS system.

The score should not be interpreted as an exploitation-priority ceiling. CISA’s KEV inclusion provides additional operational context: the vulnerability has been exploited in the wild. Organizations should prioritize remediation based on asset exposure, administrative importance, and evidence of compromise rather than waiting for a higher CVSS score or a public exploit release.

Has CVE-2026-123039 Been Exploited?

Yes. Exploitation is confirmed in the wild. CISA added CVE-2026-123039 to the Known Exploited Vulnerabilities catalog on November 13, 2026. The catalog lists a remediation due date of November 16, 2026 and directs organizations to apply vendor mitigations and follow applicable CISA guidance, including forensic triage requirements.

CISA’s record does not identify a known ransomware campaign for this vulnerability; that field is listed as unknown. Unknown ransomware use does not weaken the exploitation finding. It means only that the available CISA data does not attribute the CVE to a known ransomware campaign.

No verified public proof-of-concept repository was identified in the primary sources reviewed. The absence of a public PoC should not reduce urgency. KEV status establishes that exploitation has occurred even though public exploit code, a named intrusion set, and detailed campaign reporting are not available in the supplied authoritative records.

ResponderRunbook · act now

Detection Guidance

Start with asset and version discovery. Identify all Check Point gateways, management systems, and other Gaia OS appliances running the affected release trains. Record the installed Jumbo Hotfix Accumulator take, product role, administrative users, local shell access, and whether the system is exposed to untrusted or semi-trusted administrative paths.

Check Point’s advisory directs defenders to review dynamicCli.log for suspicious commands received by the DynamicCLI process. Look for activity involving command strings or related indicators such as whoami, /etc/shadow, ncat, nc, /dev/tcp, curl, wget, base64, useradd, and authorized_keys.

These terms are detection leads, not proof of exploitation. Correlate them with user identity, timestamps, process activity, and outbound connections.

Technical Notes: Log Review

A basic review can begin with:

grep -Ei 'whoami|/etc/shadow|ncat|(^|[^a-z])nc([^a-z]|$)|/dev/tcp|curl|wget|base64|useradd|authorized_keys' \\
  /var/log/dynamicCli.log

Log locations and formatting can vary by product and configuration. If the file is elsewhere, use the Check Point advisory and local logging configuration to identify the correct path. Preserve original logs before rotation or cleanup, and record the system time and timezone used for correlation.

A SIEM detection can normalize command text and alert when these indicators appear in DynamicCLI events. A conceptual query is:

process_name = "dynamic_server"
AND (
  command CONTAINS "whoami"
  OR command CONTAINS "/etc/shadow"
  OR command MATCHES "(^|[^A-Za-z])nc([^A-Za-z]|$)"
  OR command CONTAINS "ncat"
  OR command CONTAINS "/dev/tcp"
  OR command CONTAINS "curl"
  OR command CONTAINS "wget"
  OR command CONTAINS "base64"
  OR command CONTAINS "useradd"
  OR command CONTAINS "authorized_keys"
)

Investigate unexpected local accounts, changes to privileged files, new or modified SSH keys, persistence mechanisms, shell history, unusual outbound connections, and administrative configuration changes.

Because root-level compromise is possible, do not treat a suspicious log entry as an isolated application event. Preserve evidence and follow applicable CISA forensic triage requirements before rebuilding or making extensive changes.

Remediation and Patching

The preferred remediation is to install the applicable fixed Jumbo Hotfix Accumulator for the affected release. The fixed levels identified by Check Point are:

  • R82.20 Take 14 or later
  • R82.10 Take 52 or later
  • R82 Take 132 or later
  • R81.20 Take 174 or later

R81.10 is identified as end of life and should be handled through an upgrade or supported migration path rather than treated as a normal current-release patch target.

Confirm the appliance’s product type, release, current take, backup status, and change window before deployment. Obtain the package and installation instructions from Check Point’s official advisory and support channels. Validate the installation afterward and confirm that the running take meets or exceeds the fixed level.

The exact package command can vary by Gaia OS release and deployment model, so administrators should use the vendor-provided installation procedure rather than an unverified generic command.

Temporary Mitigation

If immediate patching is not possible, Check Point documents a mitigation that disables the dynamic_server process and prevents it from restarting:

dbset process:dynamic_server
dbset :save

This mitigation disables Dynamic CLI functionality. Check Point warns that Dynamic CLI commands listed in advisory SK144112 will fail, so test the operational effect before applying it broadly and document the change in the appliance configuration record.

Technical Notes: Mitigation and Restoration

Apply the documented mitigation from an authorized administrative session:

dbset process:dynamic_server
dbset :save

To re-enable the process after the fixed hotfix has been installed and the risk has been addressed, Check Point documents:

dbset process:dynamic_server t
dbset :save

Do not use re-enablement as a substitute for patching on a system that remains vulnerable.

If exploitation is suspected, isolate the appliance according to operational and incident-response procedures, preserve logs and relevant forensic data, rotate credentials that may have been exposed, and assess trust relationships with connected management and gateway infrastructure.

Because the issue is in CISA KEV, organizations should treat any delay as an exception requiring explicit risk acceptance. If no supported mitigation is available, applicable CISA guidance may require discontinuing use of the affected product. Confirm the requirements that apply to your organization, sector, and jurisdiction.

Incident-Response Priorities

If detection indicates possible exploitation:

  1. Preserve dynamicCli.log, authentication records, shell history, process data, and relevant network telemetry.
  2. Identify the local account or process associated with suspicious DynamicCLI activity.
  3. Check for unauthorized accounts, SSH keys, scheduled tasks, startup modifications, and changes to privileged files.
  4. Review outbound connections and administrative changes made after the suspected exploitation time.
  5. Isolate or rebuild the affected appliance according to your incident-response plan.
  6. Rotate credentials and secrets that may have been accessible from the compromised system.
  7. Review adjacent gateways, management servers, and connected infrastructure for related activity.
  8. Report or coordinate the incident according to applicable regulatory, contractual, and CISA requirements.

References

These sources establish the vulnerability description, affected Check Point release trains, fixed hotfix levels, mitigation commands, and exploitation status. The vendor advisory should remain the source of truth for product-specific applicability, package selection, installation sequencing, and any revisions to affected or fixed versions.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Last verified: 2026-11-18

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.