CVE-2026-15515

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory published 2026-07-13. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A 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.

CVSS v3
7.0
EG Score
7.0(high)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GitHub - subsubsub1231/qmukiller · GitHub

https://github.com/subsubsub1231/qmukiller

Vendor Advisories for CVE-2026-15515(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-28 00:29 UTCGHSA enrichment
  2. 2026-07-27 11:56 UTCGHSA enrichment
  3. 2026-07-26 23:58 UTCGHSA enrichment
  4. 2026-07-26 12:00 UTCEG score recompute
  5. 2026-07-26 11:59 UTCGHSA enrichment
  6. 2026-07-25 14:17 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:05 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:24 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 00:10 UTCGHSA enrichment
  16. 2026-07-16 17:02 UTCEPSS rescore
  17. 2026-07-16 12:13 UTCGHSA enrichment
  18. 2026-07-16 00:14 UTCGHSA enrichment
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:23 UTCNVD updateCVSS v4 → 6.4
  21. 2026-07-15 15:54 UTCMITRE cvelistV5CVSS v4 → 7.3
  22. 2026-07-15 12:16 UTCGHSA enrichment
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-15 00:17 UTCGHSA enrichment
  25. 2026-07-14 12:19 UTCGHSA enrichment
Show 6 more
  1. 2026-07-14 00:22 UTCGHSA enrichment
  2. 2026-07-13 22:30 UTCEPSS rescore
  3. 2026-07-13 12:25 UTCGHSA enrichment
  4. 2026-07-13 02:07 UTCNVD updateCVSS v4 → 6.4
  5. 2026-07-13 00:28 UTCEG score recompute
  6. 2026-07-13 00:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15515?
CVE-2026-15515 is a high vulnerability published on July 13, 2026. A 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…
When was CVE-2026-15515 disclosed?
CVE-2026-15515 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15515 actively exploited?
CVE-2026-15515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-15515?
CVE-2026-15515 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-15515?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15515, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15515

Explore →

Is Your Infrastructure Affected by CVE-2026-15515?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs