CVE-2025-70795: Protected Process Termination in Safetica ProcessMonitorDriver
CVE-2025-70795 is an insufficient caller-validation vulnerability in the IOCTL handler of Safetica STProcessMonitor 11.11.4.0. An attacker with administrative privileges can load the vulnerable driver and submit crafted requests that invoke kernel-mode process termination, bypassing third-party process protections. The vulnerability enables denial of service and security-tool disruption through bring-your-own-vulnerable-driver attacks. Related process-termination exposure is also documented in ProcessMonitorDriver 11.26.18, although its required control code and input structure differ from those of the initially described interface.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can terminate protected third-party applications and critical services, causing denial of service. Terminating endpoint security processes can impair detection and prevention, facilitating subsequent malicious activity. Driver-assisted security-process termination associated with this vulnerability has been observed in The Gentlemen ransomware incidents; ransomware encryption and other downstream actions are separate capabilities, not direct effects of the vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Restrict administrative privileges and unauthorized kernel-driver installation. Apply Microsoft's vulnerable-driver blocklist and App Control or WDAC policies to prevent vulnerable driver loading; enable the Defender ASR rule for abuse of vulnerable signed drivers and Memory Integrity where compatible. Monitor unexpected kernel-service creation, driver loading, and correlated termination of security processes. Validate controls against legitimate Safetica deployments before enforcement.
Remediation
Patch, then assume compromise.
Upgrade Safetica to a vendor-supported release that removes the vulnerable driver exposure, and remove obsolete vulnerable driver copies and service registrations where operationally safe. The exact fixed release is not available in the supplied information. Updating the installed application alone does not prevent an administrator-level attacker from introducing an older vulnerable driver; enforce driver-loading controls to address residual BYOVD exposure.
Exploits
2 exploits validated by Mallory's analysis.
References
Frequently asked questions
- Is CVE-2025-70795 exploited in the wild?
- Yes. As of Oct 29, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-70795?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-70795, the earliest disclosed Apr 20, 2024.
- Is there a patch for CVE-2025-70795?
- Upgrade Safetica to a vendor-supported release that removes the vulnerable driver exposure, and remove obsolete vulnerable driver copies and service registrations where operationally safe. The exact fixed release is not available in the supplied information.
- How severe is CVE-2025-70795?
- CVE-2025-70795 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.27% (19th percentile) as of Oct 29, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.