dbcve.org
QtsOperating system · Qnap

CVE-2025-66273

HIGH · 7.2 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 5.2.9.3410 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A command injection 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 execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.2.9.3410 build 20260214 and later QuTS hero h5.2.9.3410 build 20260214 and later QuTS hero h5.3.4.3500 build 20260520 and later QuTS hero h6.0.0.3397 build 20260206 and later

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated remote attackers with administrator privileges to execute arbitrary commands on the underlying system. The vulnerability is exploitable only after an attacker has first compromised an administrator account.

MitigationApply the available firmware updates (QTS 5.2.9.3410 build 20260214, QuTS hero h5.2.9.3410 build 20260214, QuTS hero h5.3.4.3500 build 20260520, or QuTS hero h6.0.0.3397 build 20260206 or later) to vulnerable QNAP devices. Additionally, secure administrator accounts through strong passwords, multi-factor authentication, and network access controls to prevent the initial account compromise required to exploit this flaw.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QtsOperating system
Affected:>= 5.2.0.2737, < 5.2.9.3410
Quts HeroOperating system
Affected:>= h5.2.0.2737, < h5.2.9.3410>= h5.3.0.3115, < h5.3.4.3500>= h6.0.0.3324, < h6.0.0.3397

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check QTS firmware version
    Log into the QNAP admin console, navigate to Control Panel > System > Firmware Update, or run 'qm` | grep -i version' via SSH if available. The version is typically displayed as a build number like 5.2.x.x.
    Affected if The installed QTS version is greater than or equal to 5.2.0.2737 AND less than 5.2.9.3410.
  2. Check QuTS hero firmware version
    Log into the QuTS hero admin console, navigate to Control Panel > System > Firmware Update, or check the version via SSH. The version format includes an 'h' prefix (e.g., h5.3.0.x).
    Affected if The installed QuTS hero version is in any of these ranges: >= h5.2.0.2737 and < h5.2.9.3410, OR >= h5.3.0.3115 and < h5.3.4.3500, OR >= h6.0.0.3324 and < h6.0.0.3397.
  3. Confirm device model
    Identify whether the device runs QTS or QuTS hero by checking the login page banner, the admin dashboard, or the System Information page. QuTS hero typically displays 'QuTS hero' in the interface header.
    Affected if The device is any QNAP NAS model running the affected QTS or QuTS hero firmware versions listed above.

If the device runs QTS version 5.2.0.2737 through 5.2.9.3409, or QuTS hero in any of the specified vulnerable version ranges, the environment is affected by CVE-2025-66273.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.9.3410 or later
Fixed in 5.2.9.3410
Interim mitigation

Apply the available firmware updates (QTS 5.2.9.3410 build 20260214, QuTS hero h5.2.9.3410 build 20260214, QuTS hero h5.3.4.3500 build 20260520, or QuTS hero h6.0.0.3397 build 20260206 or later) to vulnerable QNAP devices. Additionally, secure administrator accounts through strong passwords, multi-factor authentication, and network access controls to prevent the initial account compromise required to exploit this flaw.

Recommended fix High confidence

QTS 5.2.9.3410 (build 20260214) | QuTS hero h5.2.9.3410 (build 20260214) | QuTS hero h5.3.4.3500 (build 20260520) | QuTS hero h6.0.0.3397 (build 20260206)

  1. 1. Identify which QNAP operating system you are running (QTS, QuTS hero h5.2.x, QuTS hero h5.3.x, or QuTS hero h6.x)
  2. 2. Check your current firmware version in Control Panel > System > Firmware Update
  3. 3. For QTS users: Upgrade to QTS 5.2.9.3410 build 20260214 or later
  4. 4. For QuTS hero h5.2.x users: Upgrade to QuTS hero h5.2.9.3410 build 20260214 or later
  5. 5. For QuTS hero h5.3.x users: Upgrade to QuTS hero h5.3.4.3500 build 20260520 or later
  6. 6. For QuTS hero h6.x users: Upgrade to QuTS hero h6.0.0.3397 build 20260206 or later
  7. 7. After upgrade, verify the new build number matches or exceeds the required version
  8. 8. As a security best practice, change administrator passwords and review admin accounts for any unauthorized changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66273 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data