KEV Lag Tracker → CVE-2026-16232. Data verified against the official CISA KEV catalog and the National Vulnerability Database.

CISA added CVE-2026-16232 (Check Point SmartConsole) to the Known Exploited Vulnerabilities catalog on July 22, 2026. CISA listed it as actively exploited 0 days before its NVD publication date — exploitation was confirmed at or before public disclosure. A KEV listing is CISA’s official confirmation that a vulnerability is being exploited in the wild.

The Record

CVECVE-2026-16232
Vendor / productCheck Point SmartConsole
VulnerabilityCheck Point SmartConsole Improper Authentication Vulnerability
CVSS base score9.1
NVD publication dateJuly 22, 2026
Added to CISA KEVJuly 22, 2026
Lag (public → KEV listing)0 days
Federal patch deadlineJuly 25, 2026
Known ransomware useNo

Measured against the 1674 entries in our tracker with verified publication dates, CVE-2026-16232 was flagged faster than 87% of them.

What CISA Reported

CISA describes the flaw as follows: “Check Point SmartConsole contains an improper authentication vulnerability which could allow an unauthenticated remote attacker to obtain an application login token and use it to authenticate with full administrative privileges.”

Federal Patch Deadline

Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-16232 by July 25, 2026 — a 3-day remediation window from the KEV listing date. Private organizations are not bound by that deadline; CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

What EPSS Forecast Before the Confirmation

EPSS had no score for CVE-2026-16232 on the day before CISA confirmed exploitation. That normally means the CVE had not yet been published when it was already being exploited — a case no forecast could have flagged. Its current EPSS probability is 89.12%. See the EPSS accuracy analysis for how often this happens.

How This Compares

We do not yet track enough Check Point entries to publish a vendor median (the threshold is five with verified publication dates), so the reference here is the catalog as a whole:

Across all tracked KEV entriesValue
Entries with verified publication dates1674
Median lag (disclosure → KEV listing)266 days
Exploited within 7 days of disclosure24%
Tied to known ransomware campaigns20%

Other Recent Check Point KEV Additions

CVEProductAdded to KEVLag (days)Ransomware
CVE-2026-50751Security GatewayJune 8, 20260⚠️ Yes
CVE-2024-24919Quantum Security GatewaysMay 30, 20242⚠️ Yes

Defense guide: How to Detect Zero-day Vulnerability: Attack Chain & Defense — detection signals, attack chain and response steps for this class of attack.

Frequently Asked Questions

What is CVE-2026-16232?

CVE-2026-16232 is a vulnerability in Check Point SmartConsole (Check Point SmartConsole Improper Authentication Vulnerability) that CISA added to its Known Exploited Vulnerabilities catalog on July 22, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild.

How long was CVE-2026-16232 public before CISA confirmed exploitation?

0 days before its NVD publication date — CISA listed it as exploited at or before the vulnerability was formally published, which is the signature of a zero-day.

What is the federal patch deadline for CVE-2026-16232?

U.S. federal agencies must remediate CVE-2026-16232 by July 25, 2026, a 3-day window from the KEV listing date. Private organizations are not bound by that deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

Is CVE-2026-16232 used in ransomware campaigns?

CISA has not flagged CVE-2026-16232 as known to be used in ransomware campaigns. That field reflects confirmed campaign use, not the absence of risk.

Is a 0-day lag typical?

The median across all 1674 KEV entries we track with verified publication dates is 266 days, so CVE-2026-16232 is below the catalog median.

Related Coverage

Primary Sources

How We Track This

This page is generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No date or figure on this page is estimated or taken from a third-party source — they come directly from CISA and NVD records. Free to cite with attribution to CVEDaily (CC BY 4.0).