Skip to main content

Cato SDP Client CVE-2026-10739

| EUVDEUVD-2026-89779 HIGH
Relative Path Traversal (CWE-23)
2026-09-30 Cato GHSA-cp25-qw94-53fj
8.5
CVSS 4.0 · Vendor: Cato
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local low-privileged access
  2. Delivery
    Connect to client IPC named pipe
  3. Exploit
    Supply forged client SID
  4. Execution
    Bypass SID validation
  5. Persist
    SYSTEM service deletes arbitrary file
  6. Impact
    Corruption/DoS or privilege escalation

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Relative path traversal prevention
Exploitation Conditions

Requires the Cato Networks SDP Client for Windows (version before 6.12.6) installed and running its privileged service, plus an authenticated local user (PR:L) able to reach the client's local IPC named pipe. Exploitation is purely local (AV:L) - there is no remote or network-facing path and no user interaction is needed. The limiting factors are: attacker must already have code execution or interactive access on the endpoint at low privilege, and the target host must run the affected Cato client, which confines exposure to Cato SASE customers' managed Windows fleets.

Impact

This is a genuine but bounded-scope local privilege escalation primitive rather than a remotely-exploitable emergency. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) confirms exploitation requires an already-authenticated local user with low privileges on a Windows endpoint running the Cato SDP client - there is no network attack surface. The high 8.5 score is driven by the SYSTEM-level integrity/availability impact: a low-privileged user can coerce a SYSTEM service into deleting arbitrary files, a well-understood building block for local privilege escalation and denial of service. Signals are consistent with a moderate-priority, defense-in-depth fix: no CISA KEV listing, no EPSS score provided, and no public POC identified in the single vendor reference. There is no active-exploitation evidence, so this is a patch-in-normal-cycle item, not a fire-drill. Note a data conflict: the vendor rates confidentiality as VC:H, but arbitrary file DELETION does not directly disclose data - the realistic impact is integrity/availability (and escalation to SYSTEM), so the confidentiality rating appears inflated. Also note the 'Information Disclosure' tag contradicts the described file-deletion behavior.

Exploit ScenarioDerived

A local low-privileged user (or malware running in that user's context) on a Windows host with the Cato SDP client connects to the client's local IPC named pipe and supplies a forged/attacker-controlled SID that the service fails to validate. The service, running as SYSTEM, is then tricked into deleting an attacker-specified arbitrary file, which can be leveraged to corrupt or remove protected files and pivot toward full SYSTEM privilege escalation. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 public PoC Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Improper validation of a client-supplied SID over a local IPC named pipe in the Cato Networks SDP Client for Windows (versions before 6.12.6) lets a local, low-privileged user coerce the client's SYSTEM-level service into deleting arbitrary files with SYSTEM privileges, resulting in high integrity and availability impact on the affected endpoint. Exploitation is purely local - it requires an authenticated local user (PR:L per the CVSS vectors) with the ability to reach the client's local IPC named pipe, no user interaction, and the affected client installed and running on the target Windows host; there is no remote or network-facing attack path. This is confirmed neither as actively exploited (no CISA KEV listing) nor as having public exploit code: no public exploit identified at time of analysis, and the bounded local scope makes it a genuine but non-emergency privilege-escalation and file-tampering primitive rather than a remotely exploitable critical issue.

RemediationAI

Upgrade the Cato Networks SDP Client for Windows to version 6.12.6 or later, which is the vendor-released fix documented in the advisory at https://knowledge.catonetworks.com/docs/cve-2026-10726-cve-2026-10739-impacts-windows-client-versions-lower-than-6126 (the same advisory also covers CVE-2026-10726, so a single client upgrade addresses both). Because this is a local privilege-escalation primitive, compensating controls focus on denying the precondition: restrict local interactive logon and RDP access so that only trusted administrators can obtain a session on hosts running the SDP Client, accepting the operational trade-off that help-desk and standard user workflows on those endpoints must be redesigned or brokered through a jump host; tighten named-pipe ACLs or use Windows Defender Application Control/AppLocker to prevent untrusted binaries from connecting to the client's IPC pipe, with the trade-off that overly broad pipe restrictions can break legitimate client-to-service communication and require careful staged testing; and deploy EDR detections for SYSTEM-context file deletions initiated by the SDP Client process, especially deletions outside Cato's install and program-data directories, noting that such monitoring is detective rather than preventive and generates tuning overhead. Applying full disk or file-level backups and object-level auditing on critical SYSTEM-owned paths can reduce recovery time if an attacker triggers destructive deletions, though it does not stop the primitive itself. No public exploit code was identified at time of analysis, so prioritization should be driven by the presence of the affected client version on hosts exposed to multi-user or low-privileged local access rather than by evidence of active exploitation.

Affected VersionsENISA

SDP Client 0 <6.12.6

Affected Packages

euvd sdp_client fix: 6.12.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Cato Networks SDP (Secure Digital Perimeter) Client for Windows installs a privileged service that runs as SYSTEM and communicates with lower-privileged client components over a local IPC named pipe. Because the service trusts a client-supplied SID from those pipe messages without adequate validation, an attacker who can write to the pipe can influence a file path that the SYSTEM service subsequently acts upon. The root cause class is CWE-23 (Relative Path Traversal): traversal sequences or otherwise unvalidated path components supplied by the caller escape the intended directory, so the trusted service deletes a file outside the expected scope while operating with SYSTEM rights. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and the independent CVSS 3.1 assessment (AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H) agree that the attack is local, requires low privileges, needs no user interaction, and yields high integrity and availability impact on the vulnerable component; they differ only in whether the scope is treated as changed or in how confidentiality impact is counted, so the practical impact ceiling is arbitrary file deletion/integrity loss on the endpoint, not remote code execution and not credential disclosure. The affected component is identified by CPE cpe:2.3:a:cato_networks:sdp_client, a version-agnostic wildcard matching the Windows client line prior to the fixed release.

Know when Sdp Client gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Cato) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.4 HIGH

Local IPC named pipe (AV:L) reachable by a low-priv user (PR:L); the SYSTEM service acting on attacker input crosses a privilege boundary (S:C); deletion yields I:H/A:H but no direct disclosure (C:N).

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Cato).

CVSS VectorVendor: Cato

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 30, 2026 - 12:16 EUVD
CVE Published
Sep 30, 2026 - 11:37 cve.org
HIGH 8.5

DescriptionCVE.org

Cato Networks SDP Client for Windows before 6.12.6 allows a local user to delete arbitrary files with SYSTEM privileges via improper validation of a client-supplied SID over a local IPC named pipe.

Technical POC Analysis

Evidence caveat, read first: the only supplied evidence is a Packet Storm Bluesky post announcing "Cato VPN Client: Split-Tunnel and Privilege Escalation (CVE-2026-10739)" plus the CVE metadata you p…

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 public PoC link from packetstorm

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

Cato Networks SDP Client for Windows (versions before 6.12.6) contains a high-severity local privilege escalation vulnerability that allows an authenticated local user to force the client's SYSTEM service to delete arbitrary files, causing data loss and service disruption on affected endpoints. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis. Leadership should prioritize identifying and mitigating affected endpoints, as this flaw can be leveraged by malicious insiders or attackers with existing local access to elevate privileges and impair critical systems.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting local interactive logon to trusted users, monitoring named pipe access and file deletion events via EDR, enforcing least privilege for local accounts, maintaining offline backups of critical files, and disabling the Cato SDP Client on non-essential endpoints until a patch is available.

Threat Model

5 threats: Elevation of Privilege, Tampering, Denial of Service and 1 more

4-step attack chain with trust boundaries and controls

Full threat model - attack chain, trust boundaries, controls per stage and evidence - is part of the Pro and Business plans.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
vendor-specific SASE endpoint client, deployed only on Cato customer Windows hosts
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

62
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy