CVE-2026-123039: Check Point Multiple Products flaw exploited in the wild, what we know
CVE-2026-123039 affects Check Point Multiple Products; exploited in the wild. What happened, who is affected, how far exploitation has gone and where the patch stands.
CVE-2026-123039 at a glance
CVE-2026-123039 is a high-severity Insecure Permissions vulnerability in Check Point Multiple Products, with a CVSS 3.1 base score of 7.8. NVD published it on 2026-11-12 and classifies the weakness as CWE-732 and CWE-862. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-13; the federal remediation due date is 2026-11-16. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 2.19% (percentile 82.7, scored 2026-11-14). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Privilege Escalation, inferred from the CWE and the description. Its CVERadar threat level is 55/100.
Full CVE-2026-123039 record: exploitation evidence, ATT&CK chain and every source.
What it is
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.
Who's affected
Anyone running Check Point Multiple Products. Internet-facing instances are the priority.
NVD has not published affected version ranges for this CVE yet. Use the vendor advisory in the sources below to confirm which builds are affected.
Exploitation status
- Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-13; federal remediation due date 2026-11-16.
What this means for a small business
CISA added CVE-2026-123039 to its Known Exploited Vulnerabilities catalog on 2026-11-13. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.
If your business runs Check Point Multiple Products, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-16 to deal with it, and that is a sensible deadline for a small business too.
- Patch. Install the latest update from Check Point. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
- If you cannot patch yet. Follow 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.
- Check your exposure. Find out whether Check Point Multiple Products can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
- When to call IT support. Call your IT support provider now if you run Check Point Multiple Products and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.
Risk
- EPSS (probability of exploitation activity in the next 30 days): 1.27%, higher than 70% of all scored CVEs (as of 2026-11-13).
- CVERadar threat level: 54/100 (see methodology).
- Likely ATT&CK techniques: T1068 Exploitation for Privilege Escalation (inferred).
Remediation steps
- Find every instance. List where Check Point Multiple Products runs, including test, DR and forgotten internet-facing systems, and record the installed version.
- Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.
- If you can't patch today, follow 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.
- Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
- Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
- Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.
Detection hints
- T1068 Exploitation for Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and review who holds admin rights.
Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.
Sources
- NVD: CVE-2026-123039 nvd.nist.gov/vuln/detail/CVE-2026-123039
- CVE.org record www.cve.org/CVERecord?id=CVE-2026-123039
- Vendor link from CISA KEV support.checkpoint.com/results/sk/sk1000362
- CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
- FIRST EPSS (2026-11-13) api.first.org/data/v1/epss?cve=CVE-2026-123039
Track every exploited CVE
Full record for CVE-2026-123039, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.