CVE-2025-66277
Qnap Qts 5.2.0.2737 … 5.2.8.3332
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-66277 is a critical-severity Link Following (CWE-59) vulnerability in Qnap Qts. Its CVSS base score is 9.2 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-66277 is a link following vulnerability (CWE-59: Improper Link Resolution Before File Access) affecting multiple versions of QNAP operating systems, including QTS and QuTS hero. It enables remote attackers to traverse the file system to unintended locations, potentially exposing sensitive data or enabling unauthorized modifications. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical), reflecting its network accessibility, low complexity, lack of prerequisites, and high impact on confidentiality, integrity, and availability. It was published on 2026-02-11.
Remote, unauthenticated attackers can exploit this vulnerability over the network with low effort, as it requires no privileges or user interaction. Successful exploitation allows arbitrary file system traversal, granting read, write, or delete access to files outside intended directories, which could lead to full system compromise, data exfiltration, or persistent access on affected QNAP NAS devices.
QNAP has addressed the issue in patched releases: QTS 5.2.8.3350 build 20251216 and later, QuTS hero h5.3.2.3354 build 20251225 and later, and QuTS hero h5.2.8.3350 build 20251216 and later. Security practitioners should verify systems are updated to these or newer versions and review the official advisory at https://www.qnap.com/en/security-advisory/qsa-26-05 for full details on affected models and upgrade instructions.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207017
Vulnerability Data
A link following vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to traverse the file system to unintended locations. We have already fixed the vulnerability in the following versions:…
more
QTS 5.2.8.3350 build 20251216 and later QuTS hero h5.3.2.3354 build 20251225 and later QuTS hero h5.2.8.3350 build 20251216 and later
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2
Mitigating Controls (NIST 800-53 r5) AI
Proper enforcement of access authorizations on the resolved target resource stops a link from reaching an unintended object.
Least-privilege limits the damage an attacker can cause after following an unintended link.
Validating file-name inputs can reject or canonicalize names that resolve to links before access occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require code to validate paths and avoid unsafe link following.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect link-following flaws before release.
Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.
Application security requirements can explicitly require safe handling of symbolic links and path traversal.
Secure architecture principles include input validation and safe file-access design patterns.
Secure coding standards directly address canonicalization and symlink attacks during implementation.
Access-control rules can limit which files are reachable, reducing exposure to malicious links.