| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in QNAP QTS and QuTS hero. The affected element is an unknown function. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2025-52426. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in QNAP QTS and QuTS hero (affected version unknown). It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains an administrator account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following versions: QTS 5.2.7.3256 build 20250913 and later QuTS hero h5.2.7.3256 build 20250913 and later QuTS hero h5.3.1.3250 build 20250912 and later
The weakness was shared by coral as qsa-25-50. The advisory is shared at qnap.com. The identification of this vulnerability is CVE-2025-52426 since 06/16/2025. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-0691) and CERT Bund (WID-SEC-2026-0011). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- QNAP NAS
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.qnap.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.9
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
06/16/2025 CVE reserved01/02/2026 Advisory disclosed
01/02/2026 VulDB entry created
01/06/2026 VulDB entry last update
Sources
Vendor: qnap.comAdvisory: qsa-25-50
Researcher: coral
Status: Confirmed
CVE: CVE-2025-52426 (🔒)
GCVE (CVE): GCVE-0-2025-52426
GCVE (VulDB): GCVE-100-339389
EUVD: 🔒
CERT Bund: WID-SEC-2026-0011 - QNAP NAS: Mehrere Schwachstellen
Entry
Created: 01/02/2026 16:37Updated: 01/06/2026 10:08
Changes: 01/02/2026 16:37 (68), 01/03/2026 04:20 (1), 01/05/2026 22:57 (11), 01/06/2026 00:11 (7), 01/06/2026 10:08 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.