CVE-2025-53592VulnerabilityPublished 2 Jan 2026Updated 5 Jan 2026

CVE-2025-53592: QNAP Systems QTS · CWE-476

Affects QNAP Systems QTSSource CVE Database V5

Not known to be exploited · CVSS 1.3 Low : upgrade to 5.2.7.3256 build 20250913 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

1.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.2.7.3256 build 20250913, h5.3.1.3250 build 20250912, h5.2.7.3256 build 20250913

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade QTS to 5.2.7.3256 build 20250913; QuTS hero to h5.3.1.3250 build 20250912 or h5.2.7.3256 build 20250913.

Affected software

Product	Affected	Fixed in
QNAP Systems Inc.QTS	Affected =>=5.2.0 <5.3.0	Fixed in 5.2.7.3256 build 20250913
QNAP Systems Inc.QuTS hero	Affected ≥ h5.2.x, < h5.2.7.3256 build 20250913 ≥ h5.3.x, < h5.3.1.3250 build 20250912	Fixed in h5.3.1.3250 build 20250912 h5.2.7.3256 build 20250913

AI-suggested

1. Immediately update all QNAP NAS devices to QTS version 5.2.7.3256 or later, or the corresponding patched QuTS hero versions, to remediate the vulnerability. 2. Enforce strict user account management policies, including strong password requirements, multi-factor authentication (MFA), and regular review of user privileges to minimize the risk of unauthorized access. 3. Limit network exposure of QNAP devices by restricting access to trusted IP ranges and using VPNs for remote connections. 4. Monitor NAS device logs for unusual login attempts or service disruptions that could indicate exploitation attempts. 5. Implement network segmentation to isolate NAS devices from critical infrastructure to contain potential DoS impacts. 6. Educate users on phishing and credential hygiene to reduce the risk of account compromise. 7. Regularly backup NAS configurations and data to enable rapid recovery in case of service disruption. 8. Disable or restrict unnecessary services and ports on QNAP devices to reduce the attack surface.

Description

A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains a user 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

Impact

For European organizations, the primary impact of CVE-2025-53592 is the potential for denial-of-service attacks on QNAP NAS devices running vulnerable QTS versions. This could lead to temporary unavailability of critical file storage and backup services, disrupting business continuity, especially in SMBs and enterprises relying heavily on QNAP for data storage and sharing. While the vulnerability does not allow data theft or modification, the loss of availability can affect operational workflows, delay access to important files, and increase recovery costs. Organizations with remote or distributed workforces may experience amplified impact due to reliance on networked storage. Additionally, if attackers gain user credentials through other means (phishing, credential reuse), they could leverage this vulnerability to cause service outages. The absence of known exploits reduces immediate risk, but the presence of a fix means organizations should prioritize patching to avoid future exploitation. The impact is more pronounced in sectors with high dependence on NAS devices for data availability, such as finance, healthcare, and manufacturing.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

qnap.com/en/security-advisory/qsa-25-50 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 17:01 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats