# CVE-2026-16232: Check Point SmartConsole Improper Authentication

> Unauthenticated attackers can bypass SmartConsole login to gain administrative privileges and modify security policies if Trusted Clients are not restricted.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 22 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-m2xx-23gx-734v

## What is CVE-2026-16232?

CVE-2026-16232 is a critical authentication bypass vulnerability in checkpoint Multi-Domain Security Management, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-16232?

It affects 2 products.


Products: Checkpoint Multi-Domain Security Management, Checkpoint Quantum Security Management.

## How do I fix CVE-2026-16232?

No fix has been published for CVE-2026-16232 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Jul 2026.

## Is CVE-2026-16232 being exploited?

Yes. Attackers have exploited CVE-2026-16232 in the wild since at least 22 Jul 2026.

Public exploit code:

- A proof-of-concept script to exploit CVE-2026-16232, an authentication bypass via the SmartConsole login process using an application token. (github_poc): https://github.com/sfewer-r7/CVE-2026-16232
- CVE-2026-16232 (Check Point SmartConsole authentication bypass) PoC - unauth to admin; for authorized security testing (github_poc): https://github.com/HackSpeak/CVE-2026-16232
- Check Point SmartConsole Authentication Bypass Run Script RCE (metasploit)
- Local web app for conducting a Check Point Trusted Access Review. This scanner is built specifically to look for configuration issues around CVE-2026-16232, CVE-2026-62144 , and CVE-2026-62145. This tool is not created or supported by Check Point and should be used at your own risk. (github_poc): https://github.com/WadesWeaponShed/Check-Point-Trusted-Access-Review
- Check Point Security Management Server - SmartConsole Authentication Bypass (nuclei)

## Other vulnerabilities in checkpoint Multi-Domain Security Management

- [CVE-2026-93616](https://insights.sbomify.com/CVE-2026-93616/): Check Point Multiple Products Path Traversal (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16232 and fix it if it is affected.

What it is: CVE-2026-16232 is a critical authentication bypass vulnerability in checkpoint Multi-Domain Security Management, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-16232 in the wild since at least 22 Jul 2026.

Affected product: checkpoint Multi-Domain Security Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16232/ (Markdown: https://insights.sbomify.com/CVE-2026-16232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16232
- OSV: https://osv.dev/vulnerability/CVE-2026-16232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16232/
Summaries are generated and may contain mistakes; the official description above is the record.