Check Point Security Management / Multi-Domain Security Management, unauthenticated bypass of management authentication to arbitrary command execution; fixed in Jumbo HFA R81.20 Take 161 / R82 Take 122 / R82.10 Take 40, no fix for the R80.x / R81 / R81.10 end-of-support trains

CVE-2026-18574, Check Point Security Management: unauthenticated bypass of management authentication to arbitrary command execution, with no fix for seven end-of-support trains

Check Point disclosed CVE-2026-18574 in support article sk185222, created 2026-08-01 and last modified 2026-08-03: an unauthenticated attacker may be able to bypass management authentication and execute arbitrary commands on the Security Management Server, with successful exploitation resulting in full compromise of the management system (Check Point, 2026-08-03). CERT-FR issued CERTFR-2026-AVI-0965 on 2026-08-04, describing the effect as remote arbitrary code execution together with a security-policy bypass (CERT-FR, 2026-08-04), and BSI CERT-Bund published WID-SEC-2026-2628 the same day (BSI CERT-Bund, 2026-08-04). No party has published a CVSS score; Check Point rates the advisory High.

The affected product is the estate's policy authority, not an edge device. A Security Management or Multi-Domain Management Server holds the policy database, the object database, administrator accounts and the SIC trust material for every gateway it manages, so command execution there is a whole-perimeter problem rather than a single-host one. The single stated precondition is reachability: Check Point's advisory records that successful exploitation requires network access to the Security Management Server, and that environments which do not restrict Trusted Clients, or which expose management services to untrusted networks, may have increased exposure (Check Point, 2026-08-03).

The end-of-support gap is the sharpest fact here. Check Point's fix list covers three trains (Jumbo Hotfix Accumulator Take 161 on R81.20, Take 122 on R82, Take 40 on R82.10) while its affected-versions list additionally names R80, R80.10, R80.20, R80.30, R80.40, R81 and R81.10, all marked end-of-support (Check Point, 2026-08-03). For an estate still running any of those, there is no patch to apply and no vendor fix coming; the answer is an upgrade programme or network containment, and containment is the only one available this week. Smart-1 Cloud customers are stated to be already protected.

Check Point states the issue was discovered internally and that it has no indication of active exploits (Check Point, 2026-08-03). That is the vendor's assessment as of 2026-08-03 and is worth weighing against this product surface's recent record rather than reading as a grace period: CVE-2026-16232, an authentication bypass in the SmartConsole login path on the same management servers, went from disclosure to confirmed in-the-wild exploitation and a CISA KEV listing within days in July, and its root cause turned out to be a caller-supplied identity value the server trusted, on a configuration that was the default in testing. Two further CVEs in the same bundle followed a week later, an unauthenticated command-execution flaw and a Gaia Portal privilege escalation. Counting those, this is the fourth CVE on this management surface in roughly two weeks and the second authentication bypass among them.

Detection concepts, telemetry class first. Management-plane authentication logs are the primary surface: successful administrative sessions on the management server that are not preceded by a matching client authentication, sessions whose source address sits outside the Trusted Clients definition, and policy-install, object-modification or administrator-creation events that do not correlate with a preceding interactive administrator login. Because this flaw reaches command execution, host process-creation telemetry on the management server itself is the second anchor; shells or interpreters spawned by the management daemons are not part of normal operation.

Triage: legitimate automation produces administrative API activity without an interactive login too, CI-driven policy pushes, configuration-management integrations and scheduled management jobs all look like that. The discriminators are the source address measured against the Trusted Clients definition, which API identity is in use, and whether the activity falls inside a known scheduled window; all three should be a small fixed set on a healthy management network.

Builds on: Check Point patches an actively-exploited SmartConsole authentication bypass granting full…