Wavense
VulnerabilitiesVendorsMy Stack
Wavense© 2026 Wavense. All rights reserved.Privacy PolicyTerms & Conditions
Vulnerabilities/CVE-2026-16232
Vulnerability dossier

CVE-2026-16232

Check Point SmartConsole Administrative Authentication Bypass

VendorcheckpointPublishedJul 22, 2026SourceNVDWeaknessCWE-287
Act now

Actively exploited in the wild. Patch or mitigate immediately — don't wait for a maintenance window.

⚙ WeaponizedMetasploit module availableopen ↗
Severity
Critical · 9.3
CVSS base score
Exploitation
In the wild
CISA KEV · Metasploit
Predicted risk
78% model
EPSS forecast — overtaken by confirmed exploitation
Exposure
Internet-facing
Exploitable remotely, no login, no user action
01

What's the risk?

An unauthenticated attacker, remotely over the network, with no user interaction, can fully compromise the system — steal data, tamper with it and take it offline.

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.

How it's exploitedMITRE ATT&CK · inferred from weakness & vector
Initial Access
T1078Valid AccountsT1190Exploit Public-Facing Application

Inferred from the weakness type (CWE) and how the flaw is reached — the techniques an attacker would chain to exploit this. Real-world corroboration appears here as threat intel is folded in.

02

Who's exploiting it?

Corroborated threat activity referencing this CVE — with source and confidence, not inference.

Confirmed exploited in the wild. CISA KEV

Named threat actors and observed ATT&CK techniques appear here as intel feeds are folded in — the ATT&CK chain above stays inferred until then.

03

Are we affected?

50
  • Affectedcheckpoint · multi-domain_security_management≥ r77.30, < r81.20↑ fixed r81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr81.20
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • Affectedcheckpoint · multi-domain_security_managementr82
  • 04

    What to do

    Generated by Wavense from the CVE record — an immediate mitigation and the permanent fix.

    1. !

      Mitigate now

      Immediately restrict network access to the Check Point Management Server IP address, ensuring it is not directly exposed to the internet. Implement strict firewall rules and VPN requirements for administrative access. Proactively monitor Management Server logs for any suspicious administrative login attempts or unauthorized configuration changes from untrusted sources.

    2. ✓

      Permanent fix

      Apply the vendor-provided hotfix or security update for Check Point SmartConsole and the Management Server immediately. Consult the official Check Point security advisory for specific hotfix numbers, affected product versions, and detailed installation instructions to permanently resolve this critical vulnerability.

    Technical details— weakness, CVSS vector & calculator, related CVEs

    Business impact

    An unauthenticated remote attacker can exploit this flaw to obtain an application login token and gain full administrative privileges on the Check Point Management Server. This allows them to modify security policies and configurations, potentially leading to complete compromise of the network's security posture, unauthorized access, or denial of service.

    Weakness

    1
    CWE-287Common Weakness Enumeration · MITRE definition

    CVSS 4.0 details

    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
    Attack Vector
    Network
    Attack Complexity
    Low
    Privileges Required
    None
    User Interaction
    None
    Confidentiality
    High
    Integrity
    High
    Availability
    High

    Related vulnerabilities

    Other CVEs affecting multi-domain security management

    NVD
    9.8Critical
    CVE-2026-93616KEV

    A directory traversal and file upload vulnerability allows an unauthenticated attacker to upload and execute arbitrary scripts on Check Point Management Server.

    checkpointCWE-22Path TraversalNetworkLow effortNo authNo interactionCIA
    2026-09-22
    0.0
    / 10.0 base
    Critical severity
    Key facts
    CVE ID
    CVE-2026-16232
    Published
    Jul 22, 2026
    Last modified
    Aug 10, 2026
    CVSS
    9.3 (v4.0)
    EPSS
    77.97%
    In CISA KEV
    Yes
    Confidence
    80/100
    Weakness
    CWE-287
    Fixed in
    r81.20
    Timeline
    1. Jul 22, 2026Published to NVDNVD
    2. Aug 10, 2026Record last modifiedNVD
    3. Aug 22, 2026AI analysis generatedWavense
    View on NVD