CVE-2026-0828
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKernel 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKernel driver ProcessMonitorDriver.sys in Safetica endpoint client x64 versions 10.5.75.0 and 11.11.4.0 contains an improper access control vulnerability in its IOCTL handler, allowing unprivileged users to send specially crafted IOCTL requests to terminate protected system processes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Safetica endpoint client is installedOpen Programs and Features (appwiz.cpl) or check for Safetica in the installed programs list. Alternatively, check for the presence of ProcessMonitorDriver.sys in system driver directories (C:\Windows\System32\drivers\)Affected if Safetica endpoint client is present on the system with the driver file ProcessMonitorDriver.sys existing
-
Identify installed Safetica versionIn Programs and Features, locate Safetica and note the version column. If not displayed, check the application's About or Help section, or examine version info of the main Safetica executable (typically in C:\Program Files\Safetica\)Affected if The installed version is either 10.5.75.0 or 11.11.4.0
-
Confirm kernel driver is loadedOpen Command Prompt as Administrator and run 'sc query ProcessMonitorDriver' or check Device Manager under 'Non-Plug and Play Drivers' for ProcessMonitorDriverAffected if The ProcessMonitorDriver.sys service exists and is in a running or stopped state (driver presence alone indicates exposure)
-
Verify vulnerable version matchCompare the identified installed version against the affected versions 10.5.75.0 and 11.11.4.0. If the exact version matches either of these two, the environment is vulnerable to the improper access control flawAffected if Installed version exactly equals 10.5.75.0 or exactly equals 11.11.4.0
A system is affected if Safetica endpoint client version 10.5.75.0 or 11.11.4.0 is installed with the ProcessMonitorDriver.sys kernel driver present, allowing unprivileged users to terminate protected processes via IOCTL.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches from Safetica for versions 10.5.75.0 and 11.11.4.0; if patches are unavailable, consider disabling or removing the affected endpoint client software until a fix is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0828 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0828 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data