Exploitation / management planeMediumTLP:CLEAR

Check Point management path traversal

Check Point Management CVE-2026-93616: Pre-Authentication Path Traversal (Hunt Only)

Published
22 September 2026
Added
16 November 2026, 13:44 UK
Last updated
16 November 2026

Nothing to block1 to hunt5 behaviours to hunt

Hunt3 platforms

Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.

  • Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
  • SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
  • Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral

These queries can return false positives. Know your environment and confirm a hit before acting.

Summary

Pre-authentication path traversal on Check Point management and log servers lets an attacker run a script and load a Java class. An unauthenticated attacker can execute a script from an arbitrary path and load an arbitrary Java class.

Do now

  1. Run the hunt.
  2. Install the R82.20 Security Hotfix now.
  3. Check for check_upgrade_tools.sh.

Indicators 1

ValueTypeActionCopy
CVE-2026-93616Othermonitor

Sources Check Point · Check Point (2) · NIST · NCSC New Zealand

More detail
Note No public attacker infrastructure has been published. A match on the vendor log patterns is a lead and, as Check Point notes, does not by itself confirm compromise. Check Point management servers usually do not run Defender for Endpoint, so run the sk1000171 commands on the appliance and use firewall or NetFlow logs for TCP/19009. This is not the gateway VPN flaw CVE-2026-85102, and it is not the PHP2Shell or Gaia DynamicCLI issue already on the feed as CVE-2026-123039.

What to do

  1. Install the R82.20 Security Hotfix, or Jumbo Hotfix Accumulator R82.20 Take 10, R82.10 Take 45, R82 Take 127, R81.20 Take 170 or R81.10 Take 192; Check Point LivePatch Take 28/29 does not fix this.
  2. Restrict TCP/19009 on every Security Management, Multi-Domain, Log and SmartEvent server to trusted IP addresses, using a gateway in front of the server and the Trusted Clients list in SmartConsole.
  3. On each of those servers, run the indicator commands in Check Point sk1000171 against current and rotated cpm.elg logs, and investigate oversized login usernames, traversal or upload path lines, JAR path breakouts, and fwm or mds core dumps written at the same time.
  4. If any indicator matches, treat the management server as possibly compromised: collect diagnostics, review unexpected files and scheduled tasks, and rebuild from a fixed release if in doubt.

Behaviours to hunt 5

Behaviours are leads, not confirmed indicators, and can match legitimate activity. Compare any hit against your own baseline and environment before acting.

  1. alert Oversized login username in cpm.elg, especially with an fwm or mds core dump

    Look forA cpm.elg login request whose username is 1,001 characters or longer, especially when an fwm or mds core dump is written under /var/log/dump/usermode/ at the same time

    Why it mattersCheck Point indicator 1. An oversized username in LoginSvcImpl may indicate the authentication bypass that issues a session without valid credentials. If an fwm or mds core dump appears at the same time, Check Point says that is a potential exploit attempt. Tuning: run the sk1000171 grep on every affected server, including rotated logs. Expected false positives: none stated by the vendor; a match still needs investigation and does not by itself confirm compromise. Check Point

    Log sourceCheck Point Management, Multi-Domain, Log or SmartEvent cpm.elg and rotated cpm.elg.* under $MDS_FWDIR/log, plus /var/log/dump/usermode/; collect the log lines into Splunk or Google SecOps if you want the hunts below. The vendor command is run from Expert mode.

    QueriesSPL · YARA-L

  2. alert cpm.elg Invoking method line with a suspicious version path

    Look forcpm.elg lines of the form 'Invoking method ... in version:' that contain path separators, percent-encoded path characters or CPupgrade-tools-..

    Why it mattersCheck Point indicator 2.a, after an attacker has a session (via indicator 1, stolen credentials or another method). Unexpected path separators, encodings such as %2f or %2e, or CPupgrade-tools-.. may indicate arbitrary file operations. Check Point's example grep also matches a literal dot, which appears in ordinary version strings; this hunt keeps the path-separator, encoding and CPupgrade-tools-.. cases the advisory tells you to review. A match needs review of the path. Check Point

    Log sourcecpm.elg and rotated cpm.elg.* on the same management, log and SmartEvent servers, from Expert mode or forwarded application logs

    QueriesSPL · YARA-L

  3. alert cpm.elg upload path traversal toward upgrade tools

    Look forcpm.elg 'Uploading file' lines whose path contains directory traversal or encoded separators and targets CPupgrade-tools- or scripts/check_upgrade_tools.sh

    Why it mattersCheck Point indicator 2.b. A manipulated upload path with ../, %2e%2e%2f or %2f aimed at upgrade-tools locations may indicate an attempt to write or execute a file outside the expected directory. Review the matching path and file name. Check Point

    Log sourcecpm.elg and rotated cpm.elg.* on the same servers, from Expert mode or forwarded application logs

    QueriesSPL · YARA-L

  4. alert cpm.elg JAR path breakout under CPupgrade-tools-

    Look forcpm.elg 'The path to the jars:' lines that resolve CPupgrade-tools- with ../, /./, //, /temp/ or /opt/CPsuite-

    Why it mattersCheck Point indicator 2.c. Suspicious JAR path resolution that breaks out of the expected CPupgrade-tools directory may indicate an attempt to load an arbitrary Java class or otherwise manipulate files, which can lead to privilege escalation. Review the resulting path. Check Point

    Log sourcecpm.elg and rotated cpm.elg.* on the same servers, from Expert mode or forwarded application logs

    QueriesSPL · YARA-L

  5. alert TCP/19009 from an address that is not a trusted client

    Look forConnections to TCP 19009 on a Check Point Management, Log or SmartEvent server from an address that is not a trusted client

    Why it mattersCheck Point's primary mitigation is to allow the management web service on TCP/19009 only from trusted IP addresses. That service is the pre-authentication attack path. Tuning: replace the documentation placeholders 192[.]0[.]2[.]10 and 192[.]0[.]2[.]11 with your Trusted Clients. Management servers usually do not run Defender for Endpoint, so prefer perimeter logs; in Defender XDR a managed workstation connecting out to 19009 is only interesting if it is not an authorised administrator device. Expected false positives: a newly authorised admin workstation before the allowlist is updated, and vendor support access. Check Point

    Log sourceFirewall, NetFlow or load-balancer logs in front of the management server (Splunk Network_Traffic, Google SecOps NETWORK_CONNECTION); Defender XDR DeviceNetworkEvents for managed devices that connect out to TCP/19009

    QueriesKQL · SPL · YARA-L

Affected countries and sectors

Targets
Global
Sectors
Not stated

Background

Check Point disclosed CVE-2026-93616 (CVSS 9.8) on 22 September 2026: a pre-authentication path traversal and file-upload flaw in the management web service on Security Management, Multi-Domain Security Management, Log Server, Multi-Domain Log Server and SmartEvent. An unauthenticated attacker can execute a script from an arbitrary path and load an arbitrary Java class. Check Point Research observed a handful of pinpointed attacks on 23 July 2026, before a fix was available. CISA added the CVE to its Known Exploited Vulnerabilities catalog on 22 September 2026. Affected versions are R82.20 with no Security Hotfix or before Jumbo Take 10, R82.10 Jumbo Hotfix Take 44 or lower, R82 Take 126 or lower, R81.20 Take 166 or lower, R81.10 Take 190 or lower, and all R80 to R81 releases (end of support). Check Point LivePatch Take 28/29 does not fix it. The fix is the R82.20 Security Hotfix, or Jumbo Hotfix Accumulator R82.20 Take 10, R82.10 Take 45, R82 Take 127, R81.20 Take 170 or R81.10 Take 192. Smart-1 Cloud is already patched; firewall appliances and Spark are not affected. No public attacker IP addresses or file hashes have been published, so this entry is hunt and alert only. Its hunts follow Check Point sk1000171: an oversized login username in cpm.elg (indicator 1), often with a contemporaneous fwm or mds core dump, then traversal, upload and JAR-path breakout lines in the same logs (indicators 2.a to 2.c), plus inbound TCP/19009 from addresses that are not trusted clients.

Downloads

View folder in repository

MITRE ATT&CK4

Open in the live dashboard Get the blocklist