CVE-2026-16232 kev in the critical feed json
Authentication Bypass in the SmartConsole Login Process Using an Application Token
published 2026-07-22 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-47700
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Exploited
- added 2026-07-22
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
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.
Patch / fix
cisa 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.
- checkpoint multi-domain_security_management r81.20
- checkpoint quantum_security_management r81.20
Timeline
- First public exploit (Metasploit exploit/linux/misc/checkpoint_smartconsole_cve_2026_16232_rce)
- Added to CISA KEV
- Published
- CISA SSVC: exploitation active
- CISA patch deadline
Known exploited
- Added
- 3 mo ago
- Patch by
- 2026-07-25 (3 mo ago)
- Ransomware
- Not known
- 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.
- Vendor, product
- Check Point, SmartConsole
- CISA name
- Check Point SmartConsole Improper Authentication Vulnerability
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
3.52% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/linux/misc/checkpoint_smartconsole_cve_2026_16232_rce Check Point SmartConsole Authentication Bypass Run Script RCE metasploit exploit, excellent rank, 2026-07-22
- Nuclei template Check Point Security Management Server - SmartConsole Authentication Bypass nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- checkpoint Quantum Security Management
- checkpoint Multi-Domain Security Management
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
support.checkpoint.com
/results/sk/sk185169
mitigation, patch, vendor-advisory
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-16232
government-resource, us-government-resource
Sources
- CVE List CVE-2026-16232
- NVD CVE-2026-16232
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.