CVE-2026-16232 remediation guide

checkpoint Quantum Security Management, Multi-Domain Security Management, multi-domain security management

An authentication bypass vulnerability in the Check Point SmartConsole login process allows an unauthenticated remote attacker to obtain an application login token and use it to authenticate with full administrative privileges. Successful exploitation allows the attacker to modify security policies and security configurations. Remote exploitation requires internet access to the Management Server IP address and a configuration that does not restrict Trusted Clients. Check Point is aware that this vulnerability is being exploited and has affected a very small number of customers.

Open CVE record

Productcheckpoint Quantum Security Management, Multi-Domain Security Management, multi-domain security management

Affected versions>= R82.10 with Jumbo Hotfix Take 36 or below, >= R82 with Jumbo Hotfix Take 118 or below, >= R81.20 with Jumbo Hotfix Take 158 or below, >= R81.10, R81, R80.30, R80.20, R80.10, R80, and R77.30, >= r77.30 < r81.20, r81.20, r82, r82.10

Fixed versionsr81.20

Priority basisImmediate · CVSS 9.3 · EPSS 71.4%

Identify the affected asset

Confirm whether checkpoint Quantum Security Management, Multi-Domain Security Management, multi-domain security management is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= R82.10 with Jumbo Hotfix Take 36 or below, >= R82 with Jumbo Hotfix Take 118 or below, >= R81.20 with Jumbo Hotfix Take 158 or below, >= R81.10, R81, R80.30, R80.20, R80.10, R80, and R77.30, >= r77.30 < r81.20, r81.20, r82, r82.10. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

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 result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.