HIGH 7.5

CVE-2026-0828: Safetica ProcessMonitorDriver IOCTL Privilege Escalation & Process Termination

Safetica's endpoint protection client contains a flaw in its kernel-level driver that allows unprivileged users to forcibly terminate system processes that should be protected. An attacker without elevated privileges can exploit this through direct driver communication (IOCTL calls) to shut down critical Windows processes, potentially disabling security features or system functionality. This vulnerability affects specific versions of Safetica's x64 endpoint client.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
Affected products
0 configuration(s)
Published / Modified
2026-06-26 / 2026-06-26

NVD description (verbatim)

Kernel driver ProcessMonitorDriver.sys in Safetica's endpoint client x64 , versions 10.5.75.0 and 11.11.4.0, allows unprivileged user to abuse IOCTL path and terminate protected system processes.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-0828 is a privilege escalation and denial-of-service vulnerability in ProcessMonitorDriver.sys, a kernel-mode driver bundled with Safetica endpoint client versions 10.5.75.0 and 11.11.4.0 on 64-bit Windows systems. The driver fails to properly validate or authorize IOCTL requests, permitting unprivileged users to invoke protected process termination functionality. This breaks the process isolation guarantees that the driver is intended to enforce, allowing arbitrary process kills without administrator rights.

Business impact

An attacker exploiting this vulnerability could disable endpoint protection, terminate antivirus monitors, kill logging agents, or halt critical business applications. The ability to terminate protected processes without authentication creates both immediate availability risk and potential compliance violations if security monitoring is disrupted during an incident. Organizations relying on Safetica for endpoint protection face degraded security posture if users or malware on their systems leverage this flaw to cripple defenses.

Affected systems

Safetica endpoint client x64 versions 10.5.75.0 and 11.11.4.0 are affected. Organizations should verify their installed Safetica version against these specific release numbers. The vulnerability is kernel-level and affects Windows systems using the vulnerable versions; 32-bit versions and other Safetica product lines have not been reported as affected based on available information.

Exploitability

The vulnerability can be exploited by any unprivileged user on an affected system without requiring special tools or interaction. IOCTL exploitation is straightforward from user-mode applications, making this practically exploitable. No authentication, elevated privilege, or user interaction is needed, though the attacker must have local code execution ability. The low barrier to exploitation combined with direct access to critical system functionality elevates the practical risk.

Remediation

Update Safetica endpoint client to a patched version beyond 11.11.4.0 or verify against the vendor advisory for the specific fixed release. Organizations should prioritize this update across all endpoints running the vulnerable versions. If immediate patching is not possible, restrict driver loading or disable Safetica's process protection features as a temporary mitigation, though this reduces security posture. Consult Safetica's official security advisory for definitive patch guidance and timelines.

Patch guidance

Contact Safetica support or check their security advisory portal for the latest patched versions. Version 11.11.4.0 is confirmed vulnerable; organizations should upgrade to the next stable release confirmed by Safetica as containing the IOCTL validation fix. Test patches in a non-production environment before enterprise deployment. Safetica typically bundles updates with their management console; coordinate with your Safetica administrator or vendor account team for staged rollout if managing many endpoints.

Detection guidance

Monitor for unexpected IOCTL calls to ProcessMonitorDriver.sys from user-mode processes, particularly those not typically associated with Safetica management. Endpoint Detection and Response (EDR) tools should flag repeated IOCTL 0x**** sequences targeting process termination. Log kernel driver load events and monitor for unusual process termination patterns, especially of system services or security software. A sudden cluster of protected process kills from non-administrative contexts is a strong indicator of exploitation.

Why prioritize this

This vulnerability combines high ease of exploitation (unprivileged user, no authentication) with direct impact to process integrity and endpoint security. The ability to terminate protected processes without privilege escalation is a critical failure of a security driver's core function. While not yet listed on CISA's KEV catalog, the straightforward exploitation path and security control bypass warrant immediate prioritization, particularly in environments where endpoint protection is a primary security control.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects high network and local attack complexity, no privilege requirement, and high impact to system integrity through process termination. However, the score assumes high confidentiality impact which may not align with denial-of-service exploitation; the practical impact is significant availability damage through process kills and potential information disclosure if protected security tools are silenced during an attack.

Frequently asked questions

Does this affect our Safetica deployment if we're on version 10.5.75.0?

Yes, version 10.5.75.0 is explicitly listed as vulnerable. You should update immediately to a patched release. Contact your Safetica support team or account manager for guidance on the patched version and migration path.

Can this vulnerability be exploited remotely?

No. This is a local privilege escalation and process termination vulnerability that requires code execution on the target system. An attacker must first gain local access (via malware, phishing, or legitimate credentials) before leveraging this IOCTL flaw. However, once inside, no additional privilege is needed to trigger the vulnerability.

How does this affect our security posture if an attacker exploits it?

An attacker could disable Safetica's process protection, terminate your antivirus or EDR agent, kill security event logging, or shut down other protected system services. This creates a window where further intrusions or lateral movement may proceed undetected or unopposed. The severity depends on what other security controls you have in place beyond Safetica.

Is there a workaround if we cannot patch immediately?

Temporary mitigations include disabling Safetica's process protection module if alternate protection exists, restricting user-mode application execution via AppLocker or similar controls, or air-gapping high-value systems until patched. However, these reduce security effectiveness. Patching should be prioritized; contact Safetica for patch availability and timelines.

This analysis is based on the CVE record and published vendor information current as of the analysis date. Patch version numbers, timelines, and specific mitigation steps should be verified against official Safetica security advisories and vendor communications. CVSS scores reflect the official vector but may not capture all organizational risk contexts. This information is provided for security planning purposes and does not constitute legal advice or guaranteed remediation guidance. Organizations should conduct independent testing and validation in their own environments before deploying patches or mitigations. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).