dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-15475

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click 5 weeks old

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 weakness has been identified in MiniTool Partition Wizard up to 13.6. The affected element is an unknown function in the library pwdrvio.sys of the component Signed Kernel Driver. This manipulation causes improper access controls. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. Upgrading to version 13.9 is sufficient to fix this issue. The affected component should be upgraded. The vendor was contacted early about this disclosure.

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 · moderate confidence

Local privilege escalation vulnerability in MiniTool Partition Wizard's signed kernel driver (pwdrvio.sys). The driver implements improper access controls that allow unprivileged local users to potentially interact with the driver in unsafe ways, possibly achieving elevated privileges or kernel-level code execution.

MitigationUpgrade MiniTool Partition Wizard from any version up to 13.6 to version 13.9 to obtain the patched driver. As this is a third-party application, remediation involves standard software deployment 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Verify MiniTool Partition Wizard installation
    Look for MiniTool Partition Wizard in the Windows installed programs list (Control Panel > Programs and Features) or check for its installation directory under Program Files or Program Files (x86).
    Affected if The application is present on the system.
  2. Identify installed version
    Right-click the MiniTool Partition Wizard executable (typically named PartitionWizard.exe or similar) in the installation folder, select Properties, and check the File Version on the Details tab. Alternatively, view the version in Programs and Features.
    Affected if The installed version is 13.6 or earlier (any version up to 13.6 is affected).
  3. Locate the pwdrvio.sys driver file
    Search for the file pwdrvio.sys on the system. Common locations include the application installation directory or C:\Windows\System32\drivers\. Use Windows Search or run: dir /s pwdrvio.sys in Command Prompt.
    Affected if The driver file pwdrvio.sys exists on the system.
  4. Check driver file version
    If pwdrvio.sys is found, right-click the file, select Properties, and check the File Version on the Details tab to identify the driver version.
    Affected if The driver version corresponds to MiniTool Partition Wizard version 13.6 or earlier.

A user is affected if MiniTool Partition Wizard version 13.6 or earlier is installed and the pwdrvio.sys driver file is present on the system.

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 MiniTool Partition Wizard from any version up to 13.6 to version 13.9 to obtain the patched driver. As this is a third-party application, remediation involves standard software deployment processes.

Recommended fix High confidence

MiniTool Partition Wizard 13.9

  1. Download MiniTool Partition Wizard version 13.9 from the official MiniTool website (www.minitool.com)
  2. Uninstall the current version of MiniTool Partition Wizard (version 13.6 or earlier) from your system
  3. Install the downloaded version 13.9
  4. Restart your computer if prompted by the installer
  5. Verify the installed version by opening MiniTool Partition Wizard and checking the version number

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15475 — 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-15475 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