cve.bz

CVE-2026-16232 Check Point SmartConsole Improper Authentication Vulnerability

9.3 criticalKEVExploitEPSS 3.5%Fix available

Critical (9.3) in Check Point SmartConsole. In CISA KEV since 2026-07-22. EPSS 3.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
3.5% (unchanged from 3.5% a week ago; 78% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-07-22, due 2026-07-25
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-07-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-16232 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-16232?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-16232?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-16232 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
checkpoint:multi-domain_security_managementfrom r77.30 before r81.20
checkpoint:multi-domain_security_managementr81.20
checkpoint:multi-domain_security_managementr81.20:take_10
checkpoint:multi-domain_security_managementr81.20:take_101
checkpoint:multi-domain_security_managementr81.20:take_103
checkpoint:multi-domain_security_managementr81.20:take_105
checkpoint:multi-domain_security_managementr81.20:take_111
checkpoint:multi-domain_security_managementr81.20:take_113
checkpoint:multi-domain_security_managementr81.20:take_115
checkpoint:multi-domain_security_managementr81.20:take_118
checkpoint:multi-domain_security_managementr81.20:take_119
checkpoint:multi-domain_security_managementr81.20:take_120
checkpoint:multi-domain_security_managementr81.20:take_122
checkpoint:multi-domain_security_managementr81.20:take_126
checkpoint:multi-domain_security_managementr81.20:take_127
checkpoint:multi-domain_security_managementr81.20:take_14
checkpoint:multi-domain_security_managementr81.20:take_141
checkpoint:multi-domain_security_managementr81.20:take_146
checkpoint:multi-domain_security_managementr81.20:take_24
checkpoint:multi-domain_security_managementr81.20:take_26
checkpoint:multi-domain_security_managementr81.20:take_38
checkpoint:multi-domain_security_managementr81.20:take_41
checkpoint:multi-domain_security_managementr81.20:take_43
checkpoint:multi-domain_security_managementr81.20:take_45
checkpoint:multi-domain_security_managementr81.20:take_53
checkpoint:multi-domain_security_managementr81.20:take_54
checkpoint:multi-domain_security_managementr81.20:take_65
checkpoint:multi-domain_security_managementr81.20:take_70
checkpoint:multi-domain_security_managementr81.20:take_76
checkpoint:multi-domain_security_managementr81.20:take_79
checkpoint:multi-domain_security_managementr81.20:take_8
checkpoint:multi-domain_security_managementr81.20:take_84
checkpoint:multi-domain_security_managementr81.20:take_89
checkpoint:multi-domain_security_managementr81.20:take_90
checkpoint:multi-domain_security_managementr81.20:take_92
checkpoint:multi-domain_security_managementr81.20:take_96
checkpoint:multi-domain_security_managementr81.20:take_98
checkpoint:multi-domain_security_managementr81.20:take_99
checkpoint:multi-domain_security_managementr82
checkpoint:multi-domain_security_managementr82:take_10
checkpoint:multi-domain_security_managementr82:take_103
checkpoint:multi-domain_security_managementr82:take_107
checkpoint:multi-domain_security_managementr82:take_12
checkpoint:multi-domain_security_managementr82:take_14
checkpoint:multi-domain_security_managementr82:take_18
checkpoint:multi-domain_security_managementr82:take_19
checkpoint:multi-domain_security_managementr82:take_25
checkpoint:multi-domain_security_managementr82:take_33
checkpoint:multi-domain_security_managementr82:take_34
checkpoint:multi-domain_security_managementr82:take_36
checkpoint:multi-domain_security_managementr82:take_39
checkpoint:multi-domain_security_managementr82:take_41
checkpoint:multi-domain_security_managementr82:take_43
checkpoint:multi-domain_security_managementr82:take_44
checkpoint:multi-domain_security_managementr82:take_60
checkpoint:multi-domain_security_managementr82:take_73
checkpoint:multi-domain_security_managementr82:take_91
checkpoint:multi-domain_security_managementr82.10
checkpoint:multi-domain_security_managementr82.10:take_19
checkpoint:multi-domain_security_managementr82.10:take_24
checkpoint:multi-domain_security_managementr82.10:take_6
checkpoint:quantum_security_managementfrom r77.30 before r81.20
checkpoint:quantum_security_managementr81.20
checkpoint:quantum_security_managementr81.20:take_10
checkpoint:quantum_security_managementr81.20:take_101
checkpoint:quantum_security_managementr81.20:take_103
checkpoint:quantum_security_managementr81.20:take_105
checkpoint:quantum_security_managementr81.20:take_111
checkpoint:quantum_security_managementr81.20:take_113
checkpoint:quantum_security_managementr81.20:take_115
checkpoint:quantum_security_managementr81.20:take_118
checkpoint:quantum_security_managementr81.20:take_119
checkpoint:quantum_security_managementr81.20:take_120
checkpoint:quantum_security_managementr81.20:take_122
checkpoint:quantum_security_managementr81.20:take_126
checkpoint:quantum_security_managementr81.20:take_127
checkpoint:quantum_security_managementr81.20:take_14
checkpoint:quantum_security_managementr81.20:take_141
checkpoint:quantum_security_managementr81.20:take_146
checkpoint:quantum_security_managementr81.20:take_24
checkpoint:quantum_security_managementr81.20:take_26
checkpoint:quantum_security_managementr81.20:take_38
checkpoint:quantum_security_managementr81.20:take_41
checkpoint:quantum_security_managementr81.20:take_43
checkpoint:quantum_security_managementr81.20:take_45
checkpoint:quantum_security_managementr81.20:take_53
checkpoint:quantum_security_managementr81.20:take_54
checkpoint:quantum_security_managementr81.20:take_65
checkpoint:quantum_security_managementr81.20:take_70
checkpoint:quantum_security_managementr81.20:take_76
checkpoint:quantum_security_managementr81.20:take_79
checkpoint:quantum_security_managementr81.20:take_8
checkpoint:quantum_security_managementr81.20:take_84
checkpoint:quantum_security_managementr81.20:take_89
checkpoint:quantum_security_managementr81.20:take_90
checkpoint:quantum_security_managementr81.20:take_92
checkpoint:quantum_security_managementr81.20:take_96
checkpoint:quantum_security_managementr81.20:take_98
checkpoint:quantum_security_managementr81.20:take_99
checkpoint:quantum_security_managementr82
checkpoint:quantum_security_managementr82:take_10
checkpoint:quantum_security_managementr82:take_103
checkpoint:quantum_security_managementr82:take_107
checkpoint:quantum_security_managementr82:take_12
checkpoint:quantum_security_managementr82:take_14
checkpoint:quantum_security_managementr82:take_18
checkpoint:quantum_security_managementr82:take_19
checkpoint:quantum_security_managementr82:take_25
checkpoint:quantum_security_managementr82:take_33
checkpoint:quantum_security_managementr82:take_34
checkpoint:quantum_security_managementr82:take_36
checkpoint:quantum_security_managementr82:take_39
checkpoint:quantum_security_managementr82:take_41
checkpoint:quantum_security_managementr82:take_43
checkpoint:quantum_security_managementr82:take_44
checkpoint:quantum_security_managementr82:take_60
checkpoint:quantum_security_managementr82:take_73
checkpoint:quantum_security_managementr82:take_91
checkpoint:quantum_security_managementr82.10
checkpoint:quantum_security_managementr82.10:take_19
checkpoint:quantum_security_managementr82.10:take_24
checkpoint:quantum_security_managementr82.10:take_6

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • sfewer-r7/CVE-2026-16232 Harbor Check: matches CVE 12 stars, Python, created
    A proof-of-concept script to exploit CVE-2026-16232, an authentication bypass via the SmartConsole login process using an application token.
  • HackSpeak/CVE-2026-16232 Harbor Check: matches CVE 3 stars, Python, created
    CVE-2026-16232 (Check Point SmartConsole authentication bypass) PoC - unauth to admin; for authorized security testing

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON