9.3Kritisch KEV

CVE-2026-16232Authentication Bypass in the SmartConsole Login Process Using an Application Token

checkpoint Quantum Security Management; checkpoint Multi-Domain Security Management Veröffentlicht: (vor 3 Monaten)

Bekannt ausgenutzt — Check Point SmartConsole Improper Authentication Vulnerability

CISA hat am 22.07.2026 bestätigt, dass diese Schwachstelle in echten Angriffen genutzt wird. Frist für US-Bundesbehörden: 25.07.2026.

Erforderliche Maßnahme: 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. https://support.checkpoint.com/results/sk/sk185169/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-16232

Beschreibung

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.

Schwachstellentyp (CWE): CWE-287

Daten: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Wiedergegeben wie in der Quelle, auf Englisch.

Betroffene Produkte und Versionen

HerstellerProduktVersionen
checkpoint Multi-Domain Security Management R82.10 with Jumbo Hotfix Take 36 or below, R82 with Jumbo Hotfix Take 118 or below, R81.20 with Jumbo Hotfix Take 158 or below, R81.10, R81, R80.30, R80.20, R80.10, R80, and R77.30
checkpoint Quantum Security Management R82.10 with Jumbo Hotfix Take 36 or below, R82 with Jumbo Hotfix Take 118 or below, R81.20 with Jumbo Hotfix Take 158 or below, R81.10, R81, R80.30, R80.20, R80.10, R80, and R77.30

Referenzen und Patches

CPE-Treffer (NVD) (60)

  • cpe:2.3:a:checkpoint:multi-domain_security_management:*:*:*:*:*:*:*:* ≥ r77.30 < 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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_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_99:*:*:*:*:*:*
  • 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_103:*:*:*:*:*:*
  • 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_14:*:*:*:*:*:*
  • 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_25:*:*:*:*:*:*
  • 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_36:*:*:*:*:*:*
  • 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_43:*:*:*:*:*:*
  • 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_73:*:*:*:*:*:*
  • 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:take_19:*:*:*:*:*:*
  • cpe:2.3:a:checkpoint:multi-domain_security_management:r82.10:take_24:*:*:*:*:*:*