CVE-2025-66276: QNAP QTS Critical Remote Code Execution Vulnerability
A critical remote vulnerability affects QNAP QTS systems, allowing unauthenticated attackers on the network to compromise affected devices completely. The issue enables attackers to read sensitive data, modify system files and configurations, and disrupt service availability—all without requiring user interaction or special system access. QNAP has already released a patch, and organizations running older QTS versions should prioritize immediate patching.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 9.8 CRITICAL · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- —
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-10 / 2026-06-17
NVD description (verbatim)
QuTS hero is not affected. We have already fixed the vulnerability in the following version: QTS 5.2.7.3256 build 20250913 and later
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-66276 is a network-accessible vulnerability in QNAP QTS with a CVSS 3.1 score of 9.8 (CRITICAL). The attack vector is network-based with no authentication, low complexity, and no user interaction required, resulting in high impact across confidentiality, integrity, and availability. The vulnerability affects QTS systems broadly, though QuTS hero variants are not impacted. The vendor has issued a fix in QTS 5.2.7.3256 build 20250913 and later versions.
Business impact
This vulnerability poses an immediate threat to organizational infrastructure relying on QNAP NAS devices. Unpatched systems can be remotely compromised to exfiltrate files, alter backup data, encrypt systems for ransom, or disrupt business operations without any warning signs requiring user action. Given the critical severity and ease of exploitation, any organization using affected QTS versions faces potential data breach, compliance violations, and operational downtime. Threat actors typically prioritize such vulnerabilities for mass exploitation.
Affected systems
QNAP QTS systems are affected by this vulnerability. Specifically, any QTS installation prior to version 5.2.7.3256 build 20250913 is vulnerable. QuTS hero is confirmed not affected. Organizations should verify their current QTS version immediately—the build number and date are critical identifiers for determining exposure. Systems running legacy QTS versions face particular risk.
Exploitability
This vulnerability is highly exploitable. It requires no authentication, can be triggered over the network, involves low technical complexity, and requires no user interaction. An attacker with basic network access to a vulnerable QTS system can launch exploitation without specialized tools. The lack of any authentication barrier and the straightforward network accessibility make this a prime target for automated scanning and mass exploitation campaigns.
Remediation
Apply QTS version 5.2.7.3256 build 20250913 or any later build immediately. Organizations unable to patch immediately should implement network segmentation to restrict access to affected QTS systems from untrusted networks, disable remote access if not required, and strengthen monitoring for suspicious access patterns. Do not delay patching—the combination of critical severity and ease of exploitation makes this urgent.
Patch guidance
Verify your current QTS version and build number in the system information or administration panel. If you are running any version prior to 5.2.7.3256 build 20250913, download and install the latest QTS release from QNAP's official support portal. Test patching in a non-production environment first if possible, but do not delay—the risk of continued operation on unpatched systems outweighs typical testing timelines. After patching, confirm the new build number to ensure successful installation. Consult QNAP's official advisory for platform-specific patching procedures.
Detection guidance
Monitor QTS systems for unexpected network connections, successful authentication from unusual IP addresses, or spike in system resource usage that might indicate active exploitation. Log analysis should focus on failed and successful authentication attempts to the QTS management interface, particularly from external networks. Network intrusion detection systems should flag connections to QTS management ports from unexpected sources. Additionally, monitor for changes to critical system files or unexpected user account creation, which may indicate post-exploitation activity.
Why prioritize this
This vulnerability merits the highest priority for three reasons: (1) CRITICAL CVSS score of 9.8 reflecting complete system compromise without authentication barriers, (2) zero user interaction requirement and straightforward network exploitation enabling rapid weaponization and mass attacks, and (3) the prevalence of QNAP NAS devices in both enterprise and small-to-medium business environments as critical backup and storage infrastructure. Threat actors will prioritize exploiting this vulnerability broadly.
Risk score, explained
The CVSS 3.1 score of 9.8 reflects a network vector with no authentication, low attack complexity, and high impact across all three security dimensions. This represents near-maximal severity—only prevented from a perfect 10.0 by the fact that scope is unchanged (impact limited to the vulnerable component itself). The practical threat is severe: any unpatched QTS system on a network reachable by an attacker is immediately compromisable. The lack of any mitigating factors (authentication, user interaction, complexity) elevates this to critical urgency.
Frequently asked questions
Is my QNAP NAS affected if I run QuTS hero?
No. QNAP has explicitly confirmed that QuTS hero is not affected by CVE-2025-66276. If your system runs QuTS hero, you are not vulnerable to this particular issue. However, verify your exact product and OS variant in the system information panel, as some QNAP models can run either QTS or QuTS.
What if I cannot patch immediately?
Implement emergency network controls: isolate the affected QTS system from untrusted networks, disable remote access features (such as UPnP or cloud access) if not essential, and require VPN access for any necessary administrative connections. Enable all available audit logging. However, these are temporary measures only—patching should occur within days, not weeks.
Will the patch break my current configurations or applications?
QNAP typically maintains backward compatibility within major version families. However, test the patch on a non-production system first if you have critical, heavily customized configurations. Given the severity of this vulnerability, even a small risk of temporary misconfiguration is outweighed by the certainty of compromise if you remain unpatched. Consult QNAP's release notes and your configuration backup.
How can I tell if my system has already been compromised?
Check QTS system logs for authentication attempts from unknown sources, unexpected configuration changes, or failed login attempts prior to patching. Look for unfamiliar user accounts, unexpected scheduled tasks, or changes to backup jobs. However, sophisticated attackers may cover tracks; assume any system that was unpatched and internet-accessible for an extended period may have been compromised. After patching, strongly consider a full system audit and password reset for all administrative accounts.
This analysis is provided for informational purposes to help security teams assess and remediate vulnerability risk. The information presented is based on vendor advisories and public disclosures current as of the analysis date. Verify all technical details, including patch version numbers and affected product variants, against QNAP's official security advisory before taking action. Patch versions, build numbers, and availability may change; consult the vendor directly for the most current remediation guidance. This analysis does not constitute legal, compliance, or formal risk assessment advice. Organizations should conduct their own asset discovery, impact analysis, and testing within their specific environments. SEC.co assumes no liability for decisions made based on this analysis. Source: NVD (public-domain), retrieved 2026-07-19. Analysis generated by SEC.co (claude-haiku-4-5).
Affected vendors
Related vulnerabilities
- CVE-2025-62850HIGHQNAP QuTS hero NULL Pointer Dereference DoS Vulnerability
- CVE-2025-62851MEDIUMQNAP License Center Path Traversal Vulnerability – CVSS 4.4
- CVE-2025-62858MEDIUMQNAP Buffer Overflow (QTS / QuTS hero) – Patch Now
- CVE-2025-66273HIGHQNAP Command Injection in QTS and QuTS hero
- CVE-2025-66279HIGHQNAP NAS Command Injection – Admin Authentication Required, HIGH Severity
- CVE-2025-66280HIGHQNAP Integer Overflow Vulnerability: Patch & Risk Assessment
- CVE-2025-66281HIGHQNAP NULL Pointer Dereference DoS Vulnerability (HIGH)
- CVE-2026-22893HIGHQNAP NAS Command Injection Vulnerability (QTS, QuTS hero) – Patch Guidance
Preview — this page is review (quality 0.88). high-value: hold for review.