What is CVE-2026-62144?

CVE-2026-62144 is Management Authentication Bypass and Privilege Escalation. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-287 Improper Authentication.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-62144 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-62144 using CVSS 9.1, EPSS 21%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalAuth Bypasspublic exploit

CVE-2026-62144

CVE-2026-62144 — Management Authentication Bypass and Privilege Escalation

An authentication bypass vulnerability in Check Point Security Management and Multi-Domain Security Management allows an unauthenticated remote attacker to execute administrative commands on the Management Server. Successful exploitation may also allow command execution on managed Security Gateways. Exploitation requires network access to the Management Server without firewall protection or a configuration that does not restrict Trusted Clients.

Published Jul 22, 2026Updated Jul 24, 2026Sources: NVD, checkpoint (CNA), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

21%

ahead of 97% of scored CVEs

Affects

checkpoint

8 products listed

CVSS base

9.1

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Quantum Security Management to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

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

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.1	CVSS 3.1	critical	3.9	5.2	CNA

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-287 · Improper Authentication

Read Application Data
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands

Mitigation: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.::

Weakness & attack patterns

CWE-287Improper Authentication

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-151 · Identity SpoofingCAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-194 · Fake the Source of DataCAPEC-22 · Exploiting Trust in ClientCAPEC-650 · Upload a Web Shell to a Web ServerCAPEC-593 · Session HijackingCAPEC-114 · Authentication AbuseCAPEC-94 · Man in the Middle AttackCAPEC-633 · Token ImpersonationCAPEC-115 · Authentication Bypass

T1548Abuse Elevation Control Mechanism
T1040Network Sniffing
T1185Browser Session Hijacking

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 1 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

3 more posts on this CVEShowing 5 of 8 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Quantum Security Management, Multi-Domain Security Management.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

ip139.28.37.25090
SOCRadar BlogTrace Feeds · Jul 23, 2026
ip151.241.99.20792
SOCRadar Threat Exchange Services · Jul 23, 2026
ip151.241.99.23392
SOCRadar Threat Exchange Services · Jul 23, 2026
ip158.62.198.18292
SOCRadar Threat Exchange Services · Jul 23, 2026

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.1 (AV:N)
Jul 24, 2026 · NVD
Initial · CVE published
Jul 22, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

8×SvrsJul 24, 2026 – Aug 6, 2026 · SOCRadar CTI
3×TweetsJul 23, 2026 – Aug 23, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jul 24, 2026 · SOCRadar CTI
1×Github_Repos · Github repository created, WadesWeaponShed/Check-Point-Trusted-Access-ReviewJul 22, 2026 · SOCRadar CTI

References

1 on the record

support.checkpoint.com/results/sk/sk185152
Vendor Advisory, NIST

Coverage

6 stories from the feeds we poll

1 more reports on this CVEShowing 5 of 6 · Vendor research and security press coverageUnlock free

Elsewhere on this site

checkpointevery CVE for this vendor
Auth Bypasssame class
CWE-287other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 4 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-62144 is Management Authentication Bypass and Privilege Escalation, a critical vulnerability affecting Quantum Security Management, Multi-Domain Security Management from checkpoint. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 1 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.1 describes technical severity, while EPSS 21% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.