CVE-2026-12780
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 · uneditedA vulnerability was determined in AOMEI Backupper up to 8.3.0. Impacted is an unknown function in the library amwrtdrv.sys of the component Kernel Driver. Executing a manipulation can lead to improper access controls. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. 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 confidenceAOMEI Backupper up to version 8.3.0 contains a kernel driver (amwrtdrv.sys) with improper access controls, allowing a local attacker to potentially escalate privileges or perform unauthorized operations via the vulnerable driver.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify AOMEI Backupper installationCheck for AOMEI Backupper in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the program folder in C:\Program Files or C:\Program Files (x86)Affected if AOMEI Backupper is found installed on the system
-
Determine installed versionOpen the Windows registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AOMEI Backupper GUID} or right-click the application executable and view Properties > Details to find the versionAffected if The reported version is 8.3.0 or any earlier version (e.g., 8.2.0, 8.1.0, etc.)
-
Locate the kernel driver fileSearch for the file amwrtdrv.sys in the AOMEI Backupper installation directory (typically C:\Program Files\AOMEI Backupper or C:\Program Files (x86)\AOMEI Backupper)Affected if The driver file amwrtdrv.sys exists in the application directory
-
Check driver service statusOpen Command Prompt and run 'sc query amwrtdrv' or view Services in Task Manager to see if the AOMEI Backupper driver service is present and runningAffected if The amwrtdrv service exists and is in a running or stopped state (the vulnerability applies regardless of running state if the driver is installed)
If AOMEI Backupper version 8.3.0 or earlier is installed with the amwrtdrv.sys driver present, the system is affected by this vulnerability.
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 dataSince the vendor did not respond to disclosure, no patch is available. Implement compensating controls such as restricting local user privileges, deploying endpoint detection and response solutions, or removing/disabling AOMEI Backupper if not required.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12780 — 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-12780 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