What is CVE-2026-16232?
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.
Timeline
- 2026-07-22Published to the U.S. National Vulnerability Database (NVD)
- 2026-07-22Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
- 2026-07-24First covered in a defend.network daily briefing
- 2026-07-25CISA federal remediation deadline (BOD 22-01)
- 2026-08-10NVD record last updated
CISA Known Exploited Vulnerability
Check Point SmartConsole Improper Authentication Vulnerability
Affected product
Check Point SmartConsole
NVD also lists CPE entries for: Checkpoint Multi-Domain Security Management, Checkpoint Quantum Security Management
Remediation Steps
- Apply the vendor security update for Checkpoint Multi-Domain Security Management as a priority.
- Restrict network exposure of the affected service to trusted sources until patched.
- Review logs and detections for indicators of exploitation.
- Confirm fixed versions against the official vendor advisory before deploying.
References
Referenced in our briefings & reports
- Vulnerability Priority Report – Week 2 of August 2026 (August 10 – 16)
- Vulnerability Priority Report – Week 1 of August 2026 (August 3 – 9)
- Vulnerability Priority Report – Week 4 of July 2026 (July 27 – August 2)
- Vulnerability Priority Report – Week 3 of July 2026 (July 20 – 26)
- Microsoft 570 patches, Check Point KEV; BlueNoroff crypto phishing escalates (2026-07-25)
- Zimbra zero-day exploited by Laundry Bear; Langflow RCE added to KEV (2026-07-24)
Browse all tracked CVEs in the defend.network CVE database →