CVE-2025-3886
CVE-2025-3886 is a high-severity vulnerability in Catonetworks Cato Client with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: High (CVSS 3.x base score 8.1)
- CVSS v4: 5.7
- EPSS exploit prediction: 0% (9th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-12448
- Weakness: CWE-362
- Affected product: Catonetworks Cato Client
- Published:
- Last modified:
Description
An issue in CatoNetworks CatoClient before v.5.8.0 allows attackers to escalate privileges and achieve a race condition (TOCTOU) via the PrivilegedHelperTool component.
Frequently asked questions
- What is CVE-2025-3886?
- An issue in CatoNetworks CatoClient before v.5.8.0 allows attackers to escalate privileges and achieve a race condition (TOCTOU) via the PrivilegedHelperTool component.
- How severe is CVE-2025-3886?
- CVE-2025-3886 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2025-3886 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-3886?
- CVE-2025-3886 affects Catonetworks Cato Client. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-3886?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- Does CVE-2025-3886 have an EU (EUVD) identifier?
- Yes. CVE-2025-3886 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-12448.
- When was CVE-2025-3886 published?
- CVE-2025-3886 was published on 2025-04-27 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:catonetworks:cato_client:*:*:*:*:*:macos:*:*
More vulnerabilities in Catonetworks Cato Client
- CVE-2024-6975 — High (CVSS 8.8): Cato Networks Windows SDP Client Local Privilege Escalation via openssl configuration file. This issue affects SDP…
- CVE-2024-6974 — High (CVSS 8.8): Cato Networks Windows SDP Client Local Privilege Escalation via self-upgradeThis issue affects SDP Client: before…
- CVE-2023-43976 — High (CVSS 8.1): An issue in CatoNetworks CatoClient before v.5.4.0 allows attackers to escalate privileges and winning the race…
- CVE-2024-6973 — High (CVSS 7.5): Remote Code Execution in Cato Windows SDP client via crafted URLs. This issue affects Windows SDP Client before 5.10.34.
- CVE-2024-6977 — Medium (CVSS 6.5): A vulnerability in Cato Networks SDP Client on Windows allows the insertion of sensitive information into the log file,…
- CVE-2024-6978 — Medium (CVSS 5.6): Cato Networks Windows SDP Client Local root certificates can be installed by low-privileged users.This issue affects…
All CVEs affecting Catonetworks Cato Client →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…