CVE-2026-123039
LPE in Checkpoint Gaia Os r81 – r81.20
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-123039 is a high-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Checkpoint Gaia Os. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 19% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
OWASP Top 10 for Web (2025)
Advisories
- CISA KEV: PHP2Shell Exploited in Destructive Check Point Gateway Attacks (Nov 13)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-124481
Vulnerability Data
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.
- CWE(s)
- KEV Date Added
- 13 November 2026
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring an access control policy ensures authorization checks are defined and applied for critical functions.
Requiring attribute association with information prevents authorization from being performed without necessary security or privacy context.
Assessments review permission assignments on critical resources to confirm correctness, mitigating exploitation via incorrect permissions.
Requires verification that authorization checks are present and operational for protected resources.
Defining and enforcing access restrictions ensures correct permission assignments on resources that support changes.
Tailoring actions include assigning or restricting permissions on critical resources to the minimum necessary for the system's purpose and threat environment.
Requiring documented authorization for system operation and critical functions ensures missing authorization controls are identified and corrected during the approval process.
Program reviews and corrects overly permissive resource assignments that insiders could exploit for unauthorized access.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.3's purpose is to ensure only authorized access, and its guidance directly mandates the authorization checks that CWE-862 describes as missing, so a well-implemented access restriction control fully blocks exploitation of the missing authorization weakness.
By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.
Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.
Mandating read-only access or proxy execution by an authorized administrator ensures every requested operation is explicitly authorized before it occurs.
Mandatory authorization checks before allowing modifications ensure that every sensitive action on source code is preceded by an explicit access-control decision.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.