Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network MITM position
-
DeliveryIntercept Cato Client tunnel handshake
-
ExploitPresent forged PoP certificate (CWE-295 bypass)
-
ExecutionImpersonate Cato PoP server
-
ImpactIntercept or modify tunnel traffic
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Exploitation requires the attacker to hold a man-in-the-middle position on the same adjacent/local network segment as the victim endpoint (AV:A) and to intercept the Cato Client's tunnel handshake at connection time, when it establishes the tunnel to a Cato PoP server (the AT:P attack requirement reflects this positioning prerequisite). The flaw is the client's improper validation of the PoP server certificate (CWE-295), so no credentials (PR:N) and no user interaction (UI:N) are needed once the MITM position exists. LIMITING FACTORS: the attack is NOT internet-remote - it cannot be launched from an arbitrary location; the attacker must already control or occupy the local network path (e.g., rogue access point, ARP spoofing, malicious hotspot), which substantially narrows realistic exploitation to untrusted-network scenarios rather than default corporate deployments. |
| Impact | This is a moderate-severity integrity/confidentiality issue, not a high-priority emergency. The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:N, score 6.0) tells a consistent story: exploitation requires an ADJACENT network position AND a specific attack requirement (AT:P) - namely that the attacker already occupy a man-in-the-middle vantage point between the Cato Client and the PoP. That precondition is the single biggest risk limiter; it is not remotely exploitable across the internet (AV:A, not AV:N). Impact is weighted toward integrity (VI:H - traffic can be modified) with only limited confidentiality exposure (VC:L) and no availability impact (VA:N). No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The input tag 'Information Disclosure' only partially captures the issue - the CVSS and description emphasize traffic MODIFICATION (integrity) at least as much as interception. Net: a real but conditional flaw whose practical risk hinges entirely on an attacker achieving a MITM position on the local/adjacent network; prioritize patching for high-mobility endpoints (public Wi-Fi, untrusted networks) over fixed corporate LANs. |
| Exploit ScenarioDerived | An attacker on the same adjacent network as a victim (e.g., a shared or rogue Wi-Fi network) positions themselves between the Cato Client and a legitimate Cato PoP. Because the client fails to properly validate the PoP's certificate during the tunnel handshake, the attacker presents a fraudulent certificate, impersonates the PoP, and transparently intercepts or alters tunnel traffic. No public exploit code was identified in the provided data, and success requires the attacker to already hold a man-in-the-middle position. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Improper validation of the Cato Point of Presence (PoP) server certificate during the Cato Client tunnel handshake (CWE-295) lets an attacker who already sits on the same network segment impersonate a PoP and read or rewrite tunneled traffic. The flaw is unauthenticated (CVSS vector PR:N) and needs no user interaction, but exploitation requires a man-in-the-middle position on the adjacent/local network (AV:A with attack requirement AT:P per the vendor vector, assessed as AC:H), so it is not internet-remote - rogue access points, ARP spoofing, or hostile hotspots are the realistic vectors, not default corporate deployments. Vendor and independent scoring put this at moderate severity (vendor CVSS 6.0; independent assessment CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N, integrity impact highest), and no public exploit code was identified at time of analysis; it is a data-interception and traffic-tampering risk rather than a high-priority emergency.
RemediationAI
The primary fix is to upgrade the Cato Client to the fixed release named in the vendor advisory at https://knowledge.catonetworks.com/docs/security-vulnerability-cve-2026-19377-that-impacts-cato-client-versions; no exact patched version is provided in the intelligence data supplied here, so retrieve the version number from that advisory and do not assume one. Because the attack requires a local man-in-the-middle position, useful compensating controls until upgrade include: disabling or restricting Cato Client auto-connect on untrusted wireless networks (trade-off: added friction and manual connect steps for roaming users), requiring users to join corporate SSIDs with 802.1X/WPA3-Enterprise rather than open or shared-key hotspots where rogue APs and ARP spoofing are feasible (trade-off: no connectivity on guest/BYOD networks), and enabling Dynamic ARP Inspection, DHCP snooping, and port security on the corporate LAN to raise the cost of poisoning attacks (trade-off: configuration effort and possible breakage of unmanaged devices). Network detections for anomalous PoP endpoints and rogue AP monitoring add defense-in-depth but do not correct the validation flaw itself, and user-level workarounds such as certificate pinning are not exposed as configurable options in the client. Confirm the installed client build against the advisory before and after remediation, and treat this as a moderate-severity integrity/confidentiality issue rather than an emergency, consistent with the independent assessment.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Cato Client is the endpoint component of Cato Networks' SASE/SSE platform; it establishes an encrypted tunnel to a Cato PoP for all corporate traffic. CWE-295 (Improper Certificate Validation) means the client does not correctly verify the identity of the PoP server it is talking to during the tunnel handshake, so a forged or substituted certificate is accepted. In practical terms, an attacker positioned on the local network path (rogue AP, ARP/DNS poisoning, malicious hotspot) can present itself as the PoP, terminate the tunnel, and then read or manipulate the traffic passing through it. The vendor CVSS 4.0 vector (AV:A, AT:P, PR:N, UI:N, VC:L, VI:H) and the independent CVSS 3.1 assessment (AV:A, AC:H, PR:N, UI:N, C:L, I:H, A:N) agree on the key characteristics: adjacent-network attack vector, no credentials, no user interaction, high integrity impact and limited confidentiality impact, with no scope change. No CPE identifiers were supplied for this record, so exact platform coverage is defined only by the vendor advisory.
Know when the next one hits your stack
- 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
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Adjacent vector (AV:A) and MITM positioning requirement maps to AC:H; no auth (PR:N); traffic modification drives I:H with limited interception C:L and no availability impact.
Primary rating from Vendor (2505284f-8ffb-486c-bf60-e19c1097a90b).
CVSS VectorVendor: 2505284f-8ffb-486c-bf60-e19c1097a90b
Lifecycle Timeline
1DescriptionCVE.org
Improper certificate validation in the tunnel handshake in Cato Client allows a man-in-the-middle attacker to impersonate a Cato Point of Presence (PoP) server and intercept or modify tunnel traffic.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-101881
GHSA-v76q-8hm2-wrx6
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB