CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 3 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing3d
- Last KEV listing3d
- Last sighting26d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 22, 2026
- EUVDENISA, European Unionlisted Jul 22, 2026
- VulnCheck KEVcommercial researchlisted Jul 19, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 22, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationblackpointcyber.com/blog/cve-analysis-july-2026/
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationblackpointcyber.com/blog/blackpoint-soc-threat-pulse-week-of
- reported exploitationwww.rapid7.com/blog/post/etr-cve-2026-16232-critical-check-p
- reported exploitationblog.checkpoint.com/security/security-advisory-action-requir
- reported exploitationprevidian.com/CVE-2026-16232
8 public reports collected from VulnCheck and CIRCL, first on Jul 19, 2026. Each links to its original source. We have not verified them.
Description
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.
Required action (CISA)
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.
