Koffei

CVE-2025-70795

🟠 Medium

Safetica Application suite — the STProcessMonitor.sys driver. Keep separate from CVE-2026-0828 / CERT/CC VU#818729, which covers a different driver filename (ProcessMonitorDriver.sys) in the same family · STProcessMonitor 11.11.4.0 — from the record's prose only, since its structured vendor, product and version fields are all n/a placeholders. Privilege level is disputed and unresolved: the MITRE prose says an admin-privileged user, CISA-ADP scores PR:L, and the driver-tracking submission says legacy builds from 11.11.4.0 allow low-privilege abuse while builds from 11.26.18.0 require LocalSystem — which reconciles all three

CVSS (Koffei note)
5.5
CVSS (v3.1, CVE List)
5.5
EPSS (2026-11-18)
0.265%
18.62th percentile

Exploitation

No — no in-the-wild exploitation and no named actor found, and essentially no press coverage beyond aggregators. SSVC 17/04/2026 reads exploitation poc, automatable no, technical impact partial ; no kev block. The record's seven references are all untagged, so there was no exploit-tagged link to verify

Timeline

  1. 17/04/2026CVE record published (CVE List)
  2. 30/10/2026ThreatsDay roundup — additional exploited CVEs

Relationships

SafeticaSafeticaThe GentlemenThe GentlemenCVE-2025-70795CVE-2025-70795

exploits suspected named in the same story vendor · Select a box to open its page · All relationships

Risk

5.5 Medium (v3.1, CISA-ADP only — the MITRE CNA supplies no score and NVD is still Awaiting Analysis with no independent score) — AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, EPSS 0.261% (CWE-269 from CISA-ADP ; MITRE assigns none at all). The 5.5 understates what this is: an unauthorised process loads the driver and sends IOCTL 0xB822200C, the handler does not validate its caller, and protected processes are terminated in kernel space. It is rated availability-only, but operationally it is an EDR and antivirus killer and a BYOVD primitive, and the low EPSS reflects the absence of mass internet exploitation rather than low risk

Fix

No vendor fix found. No Safetica advisory exists, and the only remediation signal is that build 11.26.18.0 raises the bar to LocalSystem, which is hardening reported by a driver-tracking project rather than a documented vendor fix. The actionable control is driver blocklisting, not patching — block via WDAC or AppLocker and monitor for abnormal IOCTL activity. Hashes for blocklisting: 11.11.4.0 70bcec00c215fe52779700f74e9bd669ff836f594df92381cbfb7ee0568e7a8b, 11.26.18.0 5b4f59236a9b950bcd5191b35d19125f60cfb9e1a1e1aa2e4f914b6745dde9df. For context on the vendor's posture, the CERT/CC note on the sibling driver records vendor status "Unknown" with no supported fix and no vendor statement

Official description

STProcessMonitor 11.11.4.0, part of the Safetica Application suite, allows an admin-privileged user to send crafted IOCTL requests to terminate processes that are protected through a third-party implementation. This is caused by insufficient caller validation in the driver's IOCTL handler, enabling unauthorized processes to perform those actions in kernel space. Successful exploitation can lead to denial of service by disrupting critical third-party services or applications. Unauthorized processes load the driver and send a crafted IOCTL request (0xB822200C) to terminate processes protected by a third-party implementation. This action exploits insufficient caller validation in the driver's IOCTL handler, allowing unauthorized processes to perform termination operations in kernel space. Successful exploitation can lead to denial of service by disrupting critical third-party services or applications.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H