dbcve.org
QtsOperating system · Qnap

CVE-2026-24719

HIGH · 7.2 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 5.2.9.3492 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.3492 build 20260507 and later QuTS hero h5.2.9.3499 build 20260514 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 · moderate confidence

A command injection vulnerability in QNAP QTS and QuTS hero operating systems allows authenticated administrators to execute arbitrary commands on the underlying system. The attacker must first obtain valid administrator credentials before exploiting this flaw.

MitigationUpdate QNAP firmware to QTS 5.2.9.3492 (build 20260507) or QuTS hero h5.2.9.3499 (build 20260514) or later. Additionally, enforce strong administrator password policies and limit admin access to trusted networks to reduce the attack surface.

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.3492
Quts HeroOperating system
Affected:>= h5.0.0, < h5.2.9.3499

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 version via web console
    Log into the QTS admin interface and navigate to Control Panel > System > Firmware Update > Firmware Information, or use the `getcfg` command line utility to retrieve the system firmware version
    Affected if The displayed version is >= 5.2.0.2737 and < 5.2.9.3492
  2. Check QuTS hero version via web console
    Log into the QuTS hero admin interface and navigate to Control Panel > System > Firmware Update > Firmware Information, or use the `getcfg` command line utility to retrieve the system firmware version
    Affected if The displayed version is >= h5.0.0 and < h5.2.9.3499
  3. Check QTS version via command line
    Access the NAS via SSH and run `cat /etc/config/uLinux.conf` or `firmware version` to retrieve the installed QTS build number
    Affected if The build number is >= 2737 and < 3492 (corresponding to versions 5.2.0.2737 through 5.2.9.3491)
  4. Check QuTS hero version via command line
    Access the NAS via SSH and run `cat /etc/config/uLinux.conf` or `firmware version` to retrieve the installed QuTS hero build number
    Affected if The build number starts with h5.0.0 or higher and is less than h5.2.9.3499
  5. Verify administrative access exposure
    Review the network configuration in Control Panel > System > Network > Service Binding and check if the admin web console (port 8080/443) is bound to WAN or untrusted networks
    Affected if The admin interface is accessible from networks beyond the local trusted network, increasing the attack surface for credential theft

A system is affected if it runs QTS version 5.2.0.2737 through 5.2.9.3491 or QuTS hero version h5.0.0 through h5.2.9.3498, regardless of administrative exposure, since the flaw can be exploited once an attacker obtains administrator credentials.

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.3492 or later
Fixed in 5.2.9.3492
Interim mitigation

Update QNAP firmware to QTS 5.2.9.3492 (build 20260507) or QuTS hero h5.2.9.3499 (build 20260514) or later. Additionally, enforce strong administrator password policies and limit admin access to trusted networks to reduce the attack surface.

Recommended fix High confidence

QTS 5.2.9.3492 (build 20260507) or later / QuTS hero h5.2.9.3499 (build 20260514) or later

  1. 1. Identify the current QTS or QuTS hero version by navigating to Control Panel > System > Firmware Update
  2. 2. For QTS systems: Upgrade to version 5.2.9.3492 (build 20260507) or later
  3. 3. For QuTS hero systems: Upgrade to version h5.2.9.3499 (build 20260514) or later
  4. 4. Before upgrading, ensure the device has stable power and backup critical data
  5. 5. After upgrade, verify the new version matches or exceeds the fixed builds listed above
  6. 6. As a security best practice, review and ensure no unauthorized administrator accounts exist
Caveat Standard firmware upgrade risks apply - ensure stable power during update and backup critical data before proceeding

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24719 — 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-2026-24719 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