Exploited CVEs / CVE-2026-16232

CVE-2026-16232

Check Point SmartConsole Improper Authentication Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-07-25 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

CriticalCISA KEV
9.8
CVSS base
73%
EPSS exploit probability
Critical
Severity
2026-07-22
Added to KEV
2026-07-25 (past due)
CISA due date

Actively exploited Check Point SmartConsole vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-07-22.

Senserva AI read on CVE-2026-16232CISA required actionOfficial fix for CVE-2026-16232Admin questions

Senserva AI Opinion for CVE-2026-16232

This flaw lets an unauthenticated remote attacker grab an application login token from Check Point SmartConsole and use it to log in with full administrative privileges, effectively taking over your firewall management. It is confirmed exploited in the wild (CISA KEV, added 2026-07-22) and rated Critical at CVSS 9.1, so any exposed SmartConsole management interface is a direct path to controlling your security policy. Because it bypasses authentication rather than exploiting a logged-in session, network exposure of the management endpoint is the deciding risk factor.

Do this: Apply the Check Point SmartConsole fix now, then restrict management interface access to trusted admin networks and audit for unexpected admin logins or new sessions.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-16232

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-07-25; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 15, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-16232

Published
2026-07-22
Last revised
2026-07-22
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is CVE-2026-16232's addition to the CISA KEV catalog on 2026-07-22, confirming active exploitation. EPSS then climbed steeply from 1.1% on 2026-07-23 to 73.3% by 2026-08-11, while Severity rose from 0.0 to 9.8. Every indicator points the same direction: patch this today.

0%25%50%75%100%CISA KEVCISA KEV on 2026-07-222026-07-23: EPSS 1.1%2026-07-23: EPSS 1.1%2026-07-24: EPSS 13%2026-07-24: EPSS 13%2026-07-29: EPSS 70%2026-07-29: EPSS 70%2026-07-30: EPSS 70%2026-08-02: EPSS 71%2026-08-02: EPSS 71%2026-08-10: EPSS 71%2026-08-11: EPSS 73%EPSS 73%2026-07-222026-08-11

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-07-22 added to the CISA KEV catalog by CISA
  • 2026-07-23 CVSS 0.0 to 9.1; EPSS first scored at 1.1%
  • 2026-07-24 EPSS 1.1% to 12.7%
  • 2026-07-29 EPSS 12.7% to 70.0%
  • 2026-08-02 EPSS 70.0% to 71.4%
  • 2026-08-10 CVSS 9.1 to 9.8
  • 2026-08-11 EPSS 71.4% to 73.3%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-07-25 (past due).

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.

Official fix for CVE-2026-16232

Check the vendor's security advisory channel for the patched SmartConsole versions and workarounds.

Common questions about CVE-2026-16232

Is CVE-2026-16232 actively exploited?

Yes. CVE-2026-16232 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-07-22, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 73%.

What is the CISA deadline and required action for CVE-2026-16232?

CISA set the federal (BOD 22-01) remediation due date at 2026-07-25, which has passed; treat any unremediated system as overdue. The verbatim required action: 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.

What fixes CVE-2026-16232?

Check the vendor's security advisory for the patched SmartConsole versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-16232?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-16232's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Check Point CVEs
Authoritative references

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.