QTS vulnerabilities: known CVEs & security history
QNAP · Actively exploited · 83 tracked CVEs · 3 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all QTS release lines — 83 in total, with 3 actively exploited in the wild. A CVE here doesn't mean your version is affected — check QTS's current status and the safe version to run.
Known QTS CVEs
Actively-exploited and most-severe first. Showing the top 80 of 83. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2018-19949⚡ exploited | critical | 9.8 | 28% | 2020 |
| CVE-2018-19943⚡ exploited | high | 8 | 18% | 2020 |
| CVE-2018-19953⚡ exploited | medium | 6.1 | 29% | 2020 |
| CVE-2025-66276 | critical | 9.8 | 0% | 2026 |
| CVE-2025-62849 | critical | 9.8 | 1% | 2025 |
| CVE-2025-59385 | critical | 9.8 | 1% | 2025 |
| CVE-2025-30264 | high | 8.8 | 1% | 2025 |
| CVE-2024-53691 | high | 8.8 | 24% | 2024 |
| CVE-2025-52872 | high | 8.1 | 0% | 2026 |
| CVE-2025-52864 | high | 8.1 | 0% | 2026 |
| CVE-2025-52863 | high | 8.1 | 0% | 2026 |
| CVE-2025-30273 | high | 8.1 | 0% | 2025 |
| CVE-2025-9110 | high | 7.5 | 0% | 2026 |
| CVE-2025-62848 | high | 7.5 | 1% | 2025 |
| CVE-2025-62847 | high | 7.5 | 1% | 2025 |
| CVE-2026-24719 | high | 7.2 | 1% | 2026 |
| CVE-2026-24716 | high | 7.2 | 0% | 2026 |
| CVE-2026-22893 | high | 7.2 | 1% | 2026 |
| CVE-2025-66281 | high | 7.2 | 0% | 2026 |
| CVE-2025-66280 | high | 7.2 | 0% | 2026 |
| CVE-2025-66279 | high | 7.2 | 1% | 2026 |
| CVE-2025-66273 | high | 7.2 | 1% | 2026 |
| CVE-2025-47212 | high | 7.2 | 1% | 2025 |
| CVE-2026-24717 | medium | 6.5 | 0% | 2026 |
| CVE-2025-62858 | medium | 6.5 | 0% | 2026 |
| CVE-2025-62852 | medium | 6.5 | 0% | 2026 |
| CVE-2025-48721 | medium | 6.5 | 0% | 2026 |
| CVE-2025-53593 | medium | 6.5 | 0% | 2026 |
| CVE-2025-53592 | medium | 6.5 | 0% | 2026 |
| CVE-2025-53591 | medium | 6.5 | 0% | 2026 |
| CVE-2025-47208 | medium | 6.5 | 0% | 2026 |
| CVE-2025-44013 | medium | 6.5 | 0% | 2026 |
| CVE-2025-53407 | medium | 6.5 | 0% | 2025 |
| CVE-2025-53406 | medium | 6.5 | 0% | 2025 |
| CVE-2025-52429 | medium | 6.5 | 0% | 2025 |
| CVE-2025-48730 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30274 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30272 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30271 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30270 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30268 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30267 | medium | 6.5 | 0% | 2025 |
| CVE-2025-30265 | medium | 6.5 | 0% | 2025 |
| CVE-2025-29882 | medium | 6.5 | 0% | 2025 |
| CVE-2026-41539 | medium | 6.1 | 0% | 2026 |
| CVE-2025-58465 | medium | 5.4 | 0% | 2025 |
| CVE-2025-59381 | medium | 4.9 | 0% | 2026 |
| CVE-2025-59380 | medium | 4.9 | 1% | 2026 |
| CVE-2025-57705 | medium | 4.9 | 0% | 2026 |
| CVE-2025-54166 | medium | 4.9 | 0% | 2026 |
| CVE-2025-54165 | medium | 4.9 | 0% | 2026 |
| CVE-2025-54164 | medium | 4.9 | 0% | 2026 |
| CVE-2025-53596 | medium | 4.9 | 0% | 2026 |
| CVE-2025-53590 | medium | 4.9 | 0% | 2026 |
| CVE-2025-53589 | medium | 4.9 | 0% | 2026 |
| CVE-2025-53414 | medium | 4.9 | 0% | 2026 |
| CVE-2025-53405 | medium | 4.9 | 0% | 2026 |
| CVE-2025-52431 | medium | 4.9 | 0% | 2026 |
| CVE-2025-52430 | medium | 4.9 | 0% | 2026 |
| CVE-2025-52426 | medium | 4.9 | 0% | 2026 |
| CVE-2025-58463 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52866 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52862 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52860 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52859 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52858 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52857 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52855 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52854 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52853 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52433 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52432 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52428 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52427 | medium | 4.9 | 0% | 2025 |
| CVE-2025-52424 | medium | 4.9 | 0% | 2025 |
| CVE-2025-48729 | medium | 4.9 | 0% | 2025 |
| CVE-2025-48728 | medium | 4.9 | 0% | 2025 |
| CVE-2025-48727 | medium | 4.9 | 0% | 2025 |
| CVE-2025-48726 | medium | 4.9 | 0% | 2025 |
| CVE-2025-47214 | medium | 4.9 | 0% | 2025 |
3 older / lower-severity CVEs not shown — see QTS's full record.
Is my QTS version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your QTS version → · Monitor QTS for new CVEs →
QTS vulnerabilities — frequently asked
How many known vulnerabilities does QTS have?
IsItPatched tracks 83 CVEs for QTS, 3 of which are actively exploited (CISA KEV). 4 are critical-severity and 18 high-severity. These span every release line — what matters is whether the version you run is affected.
Does QTS have any actively-exploited vulnerabilities?
Yes — 3 QTS CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (3 linked to ransomware). Patch these as a priority.
What is the most severe QTS vulnerability?
Among tracked issues, CVE-2018-19949 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Improper input validation weakness.
Is QTS safe to use?
It depends on the version. The latest supported QTS release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: QTS security status · QTS end-of-life · actively-exploited CVEs. Always verify against QNAP's advisories — see our disclaimer.