dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-12784

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 weakness has been identified in IM-Magic Partition Resizer up to 7.9.0. This affects an unknown function in the library MDA_NTDRV.sys of the component Kernel Driver. This manipulation causes improper access controls. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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

Improper access controls in the MDA_NTDRV.sys kernel driver of IM-Magic Partition Resizer up to version 7.9.0 allow local attackers to potentially escalate privileges. The vulnerability exists in the kernel driver's access control mechanisms, which can be exploited with local system access.

MitigationSince the vendor did not respond and no patch is available, uninstall IM-Magic Partition Resizer and replace with an alternative partition management tool, or implement strict access controls limiting system access to trusted administrators only.

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 IM-Magic Partition Resizer is installed
    Open Programs and Features (appwiz.cpl) or check the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'IM-Magic Partition Resizer'
    Affected if The software is listed as an installed program
  2. Determine the installed version of IM-Magic Partition Resizer
    Locate the installation directory (typically C:\Program Files\IM-Magic Partition Resizer or C:\Program Files (x86)\IM-Magic Partition Resizer) and check the version property of the main executable, or check the Uninstall registry key for the DisplayVersion value
    Affected if The version is 7.9.0 or any earlier version (e.g., 7.8.0, 7.7.0, etc.)
  3. Locate the MDA_NTDRV.sys kernel driver on the system
    Search for the file MDA_NTDRV.sys in the C:\Windows\System32\drivers folder or perform a system-wide file search
    Affected if The file MDA_NTDRV.sys exists on the system
  4. Check if the MDA_NTDRV kernel driver service is registered or loaded
    Open Command Prompt and run 'sc query MDANTDRV' or check the Windows services list (services.msc) for a service related to MDA_NTDRV, or use 'driverquery /v' to list loaded drivers
    Affected if The driver is registered as a Windows service or appears in the loaded driver list

If IM-Magic Partition Resizer version 7.9.0 or earlier is installed AND the MDA_NTDRV.sys driver file is present on the system, the environment is affected by this vulnerability.

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

Since the vendor did not respond and no patch is available, uninstall IM-Magic Partition Resizer and replace with an alternative partition management tool, or implement strict access controls limiting system access to trusted administrators only.

Recommended fix High confidence
  1. This vulnerability is in a kernel driver (MDA_NTDRV.sys) which requires the vendor to release a patched driver. No vendor response or patch was received at time of disclosure.
  2. Contact IM-Magic vendor directly to request a security patch for the MDA_NTDRV.sys kernel driver.
  3. If using IM-Magic Partition Resizer in an enterprise environment, consider using application allowlisting to prevent execution of untrusted kernel drivers.
  4. Ensure only trusted administrators have local access to systems running this software.
  5. Monitor for any public proofs-of-concept targeting this vulnerability and apply compensating controls if discovered.
  6. Consider alternative partition management tools that have active security maintenance.
Caveat No fixed version available from vendor; this is a zero-day vulnerability with no vendor patch

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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