Skip to content
CVE-2026-123039

Check Point Multiple Products Incorrect Permission Assignment for Critical Resource (CVE-2026-123039)

Privilege Escalation Initial Access Last updated:

Detects exploitation and post-exploitation activity related to CVE-2026-123039, an incorrect permission assignment for a critical resource (CWE-732, CWE-862) affecting multiple Check Point products. The weakness allows actors to access or modify critical resources that should be restricted, due to overly-permissive permissions and missing authorization checks. The CVE is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, so detection focuses on anomalous administrative access, configuration/permission changes, and access to sensitive Check Point management resources by unauthorized or unexpected principals.

Vulnerability Intelligence

KEV — Known Exploited

CVSS

7.8
High (7.0–8.9)
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What is CVE-2026-123039 Check Point Multiple Products Incorrect Permission Assignment for Critical Resource (CVE-2026-123039)?

Check Point Multiple Products Incorrect Permission Assignment for Critical Resource (CVE-2026-123039) (CVE-2026-123039) maps to the Privilege Escalation and Initial Access tactics — the adversary is trying to gain higher-level permissions in MITRE ATT&CK.

This page provides production-ready detection logic for Check Point Multiple Products Incorrect Permission Assignment for Critical Resource (CVE-2026-123039), covering the data sources and telemetry it touches: Check Point Firewall/Management logs (CEF/Syslog), Network Security Appliance Logs. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Privilege Escalation Initial Access
Microsoft Sentinel / Defender
kusto
// df00tech DF00-da7ea78acd · https://df00tech.com/detections/CVE-2026-123039 · licence: https://df00tech.com/detections/licence
// Check Point syslog/CEF ingested into Sentinel (CommonSecurityLog or Syslog)
CommonSecurityLog
| where DeviceVendor has "Check Point"
| where Activity has_any ("Administrator", "Permission", "Role", "Configuration", "Login", "Policy Installation", "Object Modification")
| extend SrcIp = SourceIP, DstIp = DestinationIP, AdminUser = coalesce(column_ifexists("SourceUserName", ""), DestinationUserName)
| where Activity has_any ("Permission", "Role", "Administrator") or AdditionalExtensions has_any ("permission", "authorization", "privilege")
| summarize EventCount = count(), Activities = make_set(Activity, 20), SrcIps = make_set(SrcIp, 20) by AdminUser, DeviceName, bin(TimeGenerated, 1h)
| where EventCount > 0
| sort by EventCount desc

Flags Check Point administrative permission/role/configuration changes that may indicate abuse of the incorrect permission assignment weakness. Correlate the administering user and source IP against your known-good management jump hosts.

high severity medium confidence

Data Sources

Check Point Firewall/Management logs (CEF/Syslog) Network Security Appliance Logs

Required Tables

CommonSecurityLog Syslog

False Positives

  • Scheduled policy installations and object changes performed by authorized administrators during change windows
  • Automation/orchestration accounts (e.g., Ansible, Terraform, API integrations) performing routine configuration
  • Onboarding of new administrators or legitimate role/permission reviews

Query fingerprint DF00-da7ea78acd · licence

Sigma logsource & community rules

The detection logic for Check Point Multiple Products Incorrect Permission Assignment for Critical Resource (CVE-2026-123039) (CVE-2026-123039) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: network_connection
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.

  1. Test 1 Simulate Check Point administrator role change log event

    Expected signal: A Check Point CEF event with operation 'Role Modified' ingested into the SIEM.

  2. Test 2 Simulate unexpected administrator account creation event

    Expected signal: A Check Point CEF event with operation 'Administrator Created' from an unexpected source IP.

  3. Test 3 Simulate permission/authorization keyword event

    Expected signal: A Check Point CEF event containing 'permission'/'authorization'/'privilege' text.


Response Playbook

Triage

  1. Identify the Check Point product and version involved and confirm whether it is within scope of CVE-2026-123039 per Check Point advisory sk1000362.
  2. Determine which principal performed the permission/role/configuration change and whether that account and its source IP match an authorized administrator and management jump host.
  3. Review the specific resource whose permissions changed (administrator object, role, policy, or configuration object) and whether the change grants broader-than-expected access.
  4. Correlate the event with change-management records to confirm whether it was an approved change.

Containment

  1. Restrict management access to known-good administrator IPs and disable or reset any administrator account found to have been created or elevated without authorization.
  2. Apply the Check Point fix/hotfix referenced in sk1000362 and per CISA BOD 26-04 prioritization guidance, and revert any unauthorized permission/role changes.
  3. Temporarily tighten management-plane exposure (GUI/API access) to trusted networks until patching is confirmed.

Evidence Collection

  1. Export the relevant Check Point management audit logs, including administrator, role, and configuration-change records, for the affected time window.
  2. Capture the current administrator and role/permission configuration from the management server for comparison against a known-good baseline.

Escalation Criteria

  • ! Escalate to incident response if an administrator account or role was created or elevated by an unauthorized or unknown principal.
  • ! Escalate if evidence shows access to or modification of critical management resources from an untrusted source IP, consistent with exploitation of the authorization weakness.

Investigation Guide

Forensic Artifacts

  • > Check Point management audit logs (administrator logins, role/permission changes, policy installations)
  • > Administrator and role/permission object configuration on the management server

Tuning Guidance

Build an allowlist of authorized administrator accounts, their source management IPs/jump hosts, and known automation/service accounts. Suppress routine change-window policy installations and object edits, and alert on permission/role/administrator operations from principals or source IPs outside the baseline.


Hunting Queries

Baselines which principals and source IPs perform Check Point permission/role operations to spot anomalies.

Hunting — KQL
kql
// df00tech DF00-da7ea78acd · https://df00tech.com/detections/CVE-2026-123039 · licence: https://df00tech.com/detections/licence
CommonSecurityLog | where DeviceVendor has "Check Point" | where Activity has_any ("Permission", "Role", "Administrator") | summarize by SourceUserName, SourceIP, Activity, bin(TimeGenerated, 1d)
Hunting — SPL
spl
``` df00tech DF00-da7ea78acd · https://df00tech.com/detections/CVE-2026-123039 · licence: https://df00tech.com/detections/licence ```
index=checkpoint (action="*permission*" OR operation="*role*" OR operation="*administrator*") | stats count by administrator, src_ip, operation

Atomic Red Team Tests

Test 1 Simulate Check Point administrator role change log event
linux

Generate a synthetic Check Point-style syslog/CEF event representing an administrator role/permission change for detection validation in a lab.

Command

bash
logger -n 127.0.0.1 -P 514 -d "CEF:0|Check Point|VPN-1 & FireWall-1|R81|Role Modified|Administrator Role Modified|7|administrator=labadmin operation=Role Modified src=10.9.9.9"

Cleanup

bash
echo 'No cleanup required; synthetic log event only'

Expected Telemetry

A Check Point CEF event with operation 'Role Modified' ingested into the SIEM.

Expected Detection

The KQL/SPL/CEF-based rules match on the role/permission operation.

Test 2 Simulate unexpected administrator account creation event
linux

Emit a synthetic Check Point administrator-creation event from an untrusted source IP for testing.

Command

bash
logger -n 127.0.0.1 -P 514 -d "CEF:0|Check Point|Management|R81|Administrator Created|New Administrator Created|8|administrator=rogueadmin operation=Administrator Created src=203.0.113.50"

Cleanup

bash
echo 'No cleanup required; synthetic log event only'

Expected Telemetry

A Check Point CEF event with operation 'Administrator Created' from an unexpected source IP.

Expected Detection

Rules flag the administrator operation from a source IP outside the management baseline.

Test 3 Simulate permission/authorization keyword event
linux

Generate a synthetic event containing permission/authorization keywords to validate keyword-based matching across dialects.

Command

bash
logger -n 127.0.0.1 -P 514 -d "CEF:0|Check Point|Management|R81|Permission Change|Permission Assignment Changed|7|operation=Permission Modified msg=authorization privilege changed src=198.51.100.10"

Cleanup

bash
echo 'No cleanup required; synthetic log event only'

Expected Telemetry

A Check Point CEF event containing 'permission'/'authorization'/'privilege' text.

Expected Detection

Keyword-based conditions in the Elastic/Chronicle/Sumo rules match the event.

Related Detections

Blog posts about this detection

Browse by tactic

Full ATT&CK matrix Search all detections