CVE-2026-16232 Vulnerability Analysis & Exploit Details

CVE-2026-16232
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-16232 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-16232 Details

Status: Analyzed

Last updated: 🕢 10 Aug 2026, 19:59 UTC
Originally published on: 🕑 22 Jul 2026, 14:17 UTC

Time between publication and last update: 19 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2026-16232 Vulnerability Summary

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.

Assessing the Risk of CVE-2026-16232

Access Complexity Graph

The exploitability of CVE-2026-16232 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-16232

With low attack complexity and no required privileges, CVE-2026-16232 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-16232, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-16232, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-16232 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-16232 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-16232 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-16232 References

External References

CWE Common Weakness Enumeration

CWE-287

CAPEC Common Attack Pattern Enumeration and Classification

  • Authentication Abuse CAPEC-114 An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
  • Authentication Bypass CAPEC-115 An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
  • Identity Spoofing CAPEC-151 Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
  • Fake the Source of Data CAPEC-194 An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
  • Exploiting Trust in Client CAPEC-22 An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-57 This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
  • Session Hijacking CAPEC-593 This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
  • Token Impersonation CAPEC-633 An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
  • Upload a Web Shell to a Web Server CAPEC-650 By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
  • Adversary in the Middle (AiTM) CAPEC-94 An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.

Vulnerable Configurations

  • cpe:2.3:a:checkpoint:multi-domain_security_management:r77.30:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r77.30:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r80.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r80.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r80.20:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r80.20:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r80.30:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r80.30:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r80.40:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r80.40:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_10:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_10:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_101:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_101:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_103:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_103:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_105:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_105:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_111:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_111:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_113:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_113:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_115:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_115:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_118:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_118:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_119:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_119:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_120:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_120:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_122:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_122:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_126:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_126:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_127:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_127:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_14:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_14:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_141:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_141:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_146:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_146:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_24:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_24:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_26:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_26:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_38:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_38:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_41:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_41:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_43:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_43:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_45:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_45:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_53:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_53:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_54:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_54:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_65:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_65:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_70:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_70:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_76:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_76:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_79:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_79:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_8:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_8:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_84:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_84:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_89:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_89:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_90:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_90:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_92:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_92:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_96:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_96:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_98:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_98:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_99:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r81.20:take_99:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_10:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_10:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_103:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_103:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_107:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_107:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_12:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_12:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_14:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_14:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_18:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_18:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_19:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_19:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_25:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_25:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_33:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_33:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_34:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_34:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_36:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_36:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_39:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_39:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_41:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_41:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_43:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_43:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_44:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_44:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_60:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_60:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_73:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_73:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_91:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82:take_91:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_19:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_19:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_24:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_24:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_6:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_6:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r77.30:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r77.30:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r80.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r80.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r80.20:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r80.20:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r80.30:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r80.30:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r80.40:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r80.40:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_10:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_10:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_101:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_101:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_103:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_103:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_105:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_105:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_111:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_111:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_113:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_113:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_115:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_115:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_118:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_118:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_119:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_119:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_120:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_120:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_122:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_122:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_126:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_126:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_127:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_127:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_14:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_14:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_141:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_141:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_146:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_146:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_24:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_24:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_26:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_26:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_38:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_38:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_41:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_41:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_43:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_43:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_45:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_45:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_53:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_53:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_54:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_54:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_65:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_65:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_70:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_70:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_76:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_76:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_79:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_79:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_8:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_8:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_84:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_84:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_89:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_89:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_90:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_90:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_92:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_92:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_96:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_96:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_98:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_98:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_99:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r81.20:take_99:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_10:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_10:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_103:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_103:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_107:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_107:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_12:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_12:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_14:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_14:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_18:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_18:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_19:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_19:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_25:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_25:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_33:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_33:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_34:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_34:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_36:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_36:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_39:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_39:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_41:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_41:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_43:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_43:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_44:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_44:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_60:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_60:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_73:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_73:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82:take_91:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82:take_91:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82.10:-:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82.10:-:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_19:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_19:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_24:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_24:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_6:*:*:*:*:*:*
    cpe:2.3:a:checkpoint:quantum_security_management:r82.10:take_6:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-16232: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97219 – The MStore API WordPress plugin before 4.22.1 does not restrict which fields of an order a customer may update, allowing any authenticated user wit...
  • CVE-2026-93698 – Insufficient validation allows arbitrary commands to be executed via the Multilang adminbin.
  • CVE-2026-93697 – There is a stored XSS vulnerability allowing arbitrary code execution in the WHM Mass Modify Accounts interface.
  • CVE-2026-93029 – There is a stored XSS vulnerability allowing arbitrary code execution in the WHM Manage SSL Hosts interface.
  • CVE-2026-92924 – The Unlimited Elements for Elementor WordPress plugin before 2.0.21 does not check that a request to render widget output comes from a user allowed...