CVE-2026-15515
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 security vulnerability has been detected in Tencent PC Manager 18.1.30242.301. This issue affects some unknown processing in the library qmudisk64.sys of the component QMUDisk Driver. The manipulation leads to uncontrolled search path. The attack must be carried out locally. The attack is considered to have high complexity. The exploitability is assessed as difficult. The exploit has been disclosed publicly and may 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 confidenceUncontrolled search path vulnerability in Tencent PC Manager's QMUDisk driver (qmudisk64.sys). The driver loads resources from locations that may be manipulated by a local attacker, potentially allowing malicious code execution with elevated privileges. This is a kernel-mode driver vulnerability making it particularly sensitive.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Check if Tencent PC Manager is installedLook for Tencent PC Manager in installed programs via Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) or check for its installation directory (typically C:\Program Files\Tencent\PCMgr or similar)Affected if Tencent PC Manager is installed on the system
-
Locate the qmudisk64.sys driver fileSearch for qmudisk64.sys in the Tencent PC Manager installation directory and system driver folders (C:\Windows\System32\drivers, C:\Windows\SysWOW64\drivers)Affected if The qmudisk64.sys driver file exists on the system
-
Check if the driver is loadedRun 'sc query qmudisk' or check the driver list via 'driverquery /v | findstr qmudisk' in an elevated command promptAffected if The qmudisk driver shows as RUNNING or LOADED in the service status
-
Verify driver file integrity and locationInspect the driver file properties to confirm it is the QMUDisk driver from Tencent, and check that it is not in a user-writable locationAffected if Driver file is present and originates from Tencent PC Manager QMUDisk component
-
Check for driver loading permissionsReview the permissions on the driver file and its loading configuration in the registry (HKLM\SYSTEM\CurrentControlSet\Services\qmudisk) to ensure no unauthorized modificationAffected if Driver is present and could be loaded by the system
A system is affected if Tencent PC Manager is installed and the qmudisk64.sys driver is present or loaded, since the uncontrolled search path vulnerability allows potential privilege escalation through driver resource loading manipulation.
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 vendor did not respond, disable or remove the QMUDisk driver if possible; implement application control policies to restrict driver loading; monitor for indicators of compromise given public exploit availability.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15515 — 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-15515 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