dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-12779

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 found in AOMEI Dynamic Disk Manager up to 10.10.1. This issue affects some unknown processing in the library ddmdrv.sys of the component Kernel Driver. Performing a manipulation results in improper access controls. The attack must be initiated from a local position. The exploit has been made public and could be used. 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

A vulnerability in the kernel driver (ddmdrv.sys) of AOMEI Dynamic Disk Manager allows local attackers to perform improper access controls due to unknown processing issues in the driver component. The exploit has been publicly disclosed and can be exploited from a local attack position.

MitigationSince the vendor did not respond to early disclosure and no patch is available, organizations should remove or disable AOMEI Dynamic Disk Manager until a fix is released, or implement compensating controls such as restricting local access to systems running the affected software.

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. Verify AOMEI Dynamic Disk Manager installation
    Check for the presence of AOMEI Dynamic Disk Manager in installed programs via registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or by looking in C:\Program Files\AOMEI or C:\Program Files (x86)\AOMEI
    Affected if AOMEI Dynamic Disk Manager is installed on the system
  2. Locate the ddmdrv.sys driver file
    Search for ddmdrv.sys file on the system using file search or checking typical driver locations such as C:\Windows\System32\drivers\ and the application's install directory
    Affected if The file ddmdrv.sys exists on the system
  3. Check if ddmdrv.sys driver is loaded
    Run 'sc query ddmdrv' or 'driverquery /v | findstr ddmdrv' in Command Prompt to query driver status, or check in Device Manager under System devices
    Affected if The ddmdrv driver is present and running (status shows RUNNING)
  4. Identify installed AOMEI Dynamic Disk Manager version
    Check the installed version via Programs and Features in Control Panel, the application's uninstall entry in registry, or by locating the main executable (usually in the install directory) and checking its file properties
    Affected if A version of AOMEI Dynamic Disk Manager is installed (without a vendor patch, any version with the vulnerable driver is affected)
  5. Check for running AOMEI processes
    Open Task Manager or run 'tasklist /v | findstr AOMEI' to see if any AOMEI Dynamic Disk Manager processes are actively running
    Affected if Any AOMEI Dynamic Disk Manager process is running (indicating the software is actively loaded)
  6. Review driver signing status
    Run 'sigcheck -k ddmdrv.sys' or check driver properties in Device Manager to verify if the driver is digitally signed (vulnerable drivers may be unsigned or have suspicious signatures)
    Affected if The driver is present without proper Microsoft WHQL signing or displays unknown publisher information

A system is affected if AOMEI Dynamic Disk Manager is installed with the ddmdrv.sys kernel driver present, regardless of version, since no patched version is available from the vendor.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond to early disclosure and no patch is available, organizations should remove or disable AOMEI Dynamic Disk Manager until a fix is released, or implement compensating controls such as restricting local access to systems running the affected software.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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