Check Point Multiple Products Incorrect Permission Assignment for Critical Resource
CVE-2026-123039 is a high-severity incorrect permission assignment for critical resource vulnerability in Quantum Security Gateway from Check Point, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Quantum Security Gateway versions: R82.10 with Jumbo Hotfix Take 50 or below; R82.20 with Jumbo Hotfix Take 10 or below; R82 with Jumbo Hotfix Take 130 or below, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on November 13, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Check which version of Quantum Security Gateway you run against the affected versions below, and install the vendor's latest release.
- CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Check Point | Quantum Security Gateway | R82.10 with Jumbo Hotfix Take 50 or below; R82.20 with Jumbo Hotfix Take 10 or below; R82 with Jumbo Hotfix Take 130 or below; R81.20 with Jumbo Hotfix Take 173 or below | Not stated |
| Check Point | Quantum Security Management | R82.10 with Jumbo Hotfix Take 50 or below; R82.20 with Jumbo Hotfix Take 10 or below; R82 with Jumbo Hotfix Take 130 or below; R81.20 with Jumbo Hotfix Take 173 or below | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (checkpoint.com).
Official description
The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Record last changed materially (score, affected products, status or references).
- Deadline for US federal agencies to remediate, set by CISA.
References
Other references
Other vulnerabilities in Quantum Security Gateway
- 7.3 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.4 High severity
- 9.3 Critical severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 8.4 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.