dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-12781

HIGH · 7.8 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
A vulnerability was identified in EaseUS Partition Master up to 14.5. The affected element is an unknown function in the library epmntdrv.sys of the component Kernel Driver. The manipulation leads to improper access controls. The attack needs to be performed locally. The exploit is publicly available and might be used. You should upgrade the affected component. The vendor explains: "We have confirmed that this issue was present only in older versions of the product. Our product has since been updated, and the issue has been resolved in the latest version, so it no longer exists."

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 confidence

EaseUS Partition Master contains a kernel driver (epmntdrv.sys) with improper access control, allowing a local unprivileged attacker to potentially escalate privileges to kernel/system level via the driver's ioctl interfaces. A publicly available exploit exists for this vulnerability.

MitigationUpgrade EaseUS Partition Master to the latest version. The vendor has confirmed the issue is resolved in current releases.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if EaseUS Partition Master is installed
    Look for the software in Add/Remove Programs or check for the installation directory typically at C:\Program Files\EaseUS\Partition Master or C:\Program Files (x86)\EaseUS\Partition Master
    Affected if EaseUS Partition Master is installed on the system
  2. Identify the installed version
    Check the version information in the program's main executable (often PartitionMaster.exe) by right-clicking the file, selecting Properties, and viewing the Details tab. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductID} or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ for an EaseUS entry
    Affected if The installed version is older than the current patched version (the vendor states the issue is resolved in current releases)
  3. Locate the epmntdrv.sys driver file
    Search for epmntdrv.sys on the system using File Explorer search or the command: dir /s C:\epmntdrv.sys
    Affected if The file epmntdrv.sys exists on the system, indicating the vulnerable driver component is present
  4. Check if the driver is currently loaded
    Open Command Prompt as Administrator and run: sc query epmntdrv or check Device Manager for hidden devices or drivers related to EaseUS. Also check the services list: sc queryex type= service state= all | findstr -i epmntdrv
    Affected if The driver service exists and is in a running or stopped state, meaning the vulnerable ioctl interface is available on the system

A user is affected if EaseUS Partition Master is installed with the epmntdrv.sys driver present and the installed version predates the vendor's patched release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EaseUS Partition Master to the latest version. The vendor has confirmed the issue is resolved in current releases.

Recommended fix Moderate confidence

Latest version of EaseUS Partition Master (vendor states issue resolved in current release)

  1. Open EaseUS Partition Master and navigate to Help > About to identify the currently installed version.
  2. Visit the official EaseUS website (easeus.com) and navigate to the Partition Master product page to determine the latest available version.
  3. If the current version is 14.5 or earlier, download the latest version from the official EaseUS website.
  4. Close any running instances of EaseUS Partition Master before proceeding with installation.
  5. Run the downloaded installer and follow the on-screen instructions to update to the latest version.
  6. After installation, verify the updated version number via Help > About to confirm the remediation.
Caveat Review release notes for any significant changes between older versions and the latest release; backup important data before updating partition management software

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12781 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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