This page was not yet optimized for use on mobile devices.
QNAP QuTS Hero H5.2.5.3138 Build 20250519
Configuration details
| CPE title | QNAP QuTS Hero H5.2.5.3138 Build 20250519 |
|---|---|
| URI | cpe:2.3:o:qnap:quts_hero:h5.2.5.3138:build_20250519:*:*:*:*:*:* |
Linked CVEs
70 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2025-44013 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-47205 | MEDIUM | 4.9 | 11.02.2026 | |
| CVE-2025-47208 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-47211 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-47212 | HIGH | 7.2 | 03.10.2025 | |
| CVE-2025-47213 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-47214 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-48721 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-48725 | HIGH | 8.1 | 11.02.2026 | |
| CVE-2025-48726 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-48727 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-48728 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-48729 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-48730 | MEDIUM | 6.5 | 03.10.2025 | |
| CVE-2025-52424 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52426 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-52427 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52428 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52429 | MEDIUM | 6.5 | 03.10.2025 | |
| CVE-2025-52430 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-52431 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-52432 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52433 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52853 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52854 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52855 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52857 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52858 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52859 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52860 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52862 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52863 | HIGH | 8.1 | 02.01.2026 | |
| CVE-2025-52864 | HIGH | 8.1 | 02.01.2026 | |
| CVE-2025-52866 | MEDIUM | 4.9 | 03.10.2025 | |
| CVE-2025-52872 | HIGH | 8.1 | 02.01.2026 | |
| CVE-2025-53405 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-53406 | MEDIUM | 6.5 | 03.10.2025 | |
| CVE-2025-53407 | MEDIUM | 6.5 | 03.10.2025 | |
| CVE-2025-53414 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-53589 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-53590 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-53591 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-53592 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-53593 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-53596 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-54164 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-54165 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-54166 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-57705 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-58466 | MEDIUM | 4.9 | 11.02.2026 | |
| CVE-2025-59380 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-59381 | MEDIUM | 4.9 | 02.01.2026 | |
| CVE-2025-59385 | CRITICAL | 9.8 | 16.12.2025 | |
| CVE-2025-62847 | HIGH | 7.5 | 16.12.2025 | |
| CVE-2025-62848 | HIGH | 7.5 | 16.12.2025 | |
| CVE-2025-62849 | CRITICAL | 9.8 | 16.12.2025 | |
| CVE-2025-62850 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2025-62852 | MEDIUM | 6.5 | 02.01.2026 | |
| CVE-2025-62858 | MEDIUM | 6.5 | 09.06.2026 | |
| CVE-2025-66273 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2025-66277 | CRITICAL | 9.8 | 11.02.2026 | |
| CVE-2025-66279 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2025-66280 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2025-66281 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2025-9110 | HIGH | 7.5 | 02.01.2026 | |
| CVE-2026-22893 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2026-24716 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2026-24717 | MEDIUM | 6.5 | 10.06.2026 | |
| CVE-2026-24719 | HIGH | 7.2 | 10.06.2026 | |
| CVE-2026-41539 | MEDIUM | 6.1 | 09.06.2026 |
Showing 5 out of 70.
Matched certificates
This CPE has no matched certificates.