dbcve.org
QtsOperating system · Qnap

CVE-2026-24716

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 NULL pointer dereference 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 launch a denial-of-service (DoS) attack. 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 QuTS hero h5.3.4.3500 build 20260520 and later QuTS hero h6.0.0.3459 build 20260409 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

This is a NULL pointer dereference vulnerability in QNAP QTS and QuTS hero operating systems. An attacker who first gains administrative credentials can exploit this flaw to cause a denial-of-service condition on the affected device.

MitigationUpgrade QNAP devices to the specified fixed firmware versions (QTS 5.2.9.3492+, QuTS hero h5.2.9.3499+, h5.3.4.3500+, or h6.0.0.3459+) and review administrative accounts for any signs of compromise.

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>= h5.3.0.3115, < h5.3.4.3500>= h6.0.0.3324, < h6.0.0.3459

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. Identify the QNAP operating system variant
    Determine whether the device runs QTS or QuTS hero - this can be done via the system information page in the QNAP admin console or by checking the system firmware details
    Affected if The device runs either QTS or QuTS hero operating system
  2. Determine the installed QTS version
    Locate the firmware version in the QNAP admin interface under System > Firmware or System Information. The version number will be in the format x.x.x.x (e.g., 5.2.0.2737)
    Affected if The QTS version is >= 5.2.0.2737 AND < 5.2.9.3492
  3. Determine the installed QuTS hero version
    Locate the firmware version in the QNAP admin interface under System > Firmware or System Information. The version number will be in the format hX.X.X.X (e.g., h5.0.0)
    Affected if The QuTS hero version falls into any of these ranges: >= h5.0.0 AND < h5.2.9.3499; OR >= h5.3.0.3115 AND < h5.3.4.3500; OR >= h6.0.0.3324 AND < h6.0.0.3459
  4. Verify administrator access controls
    Review whether strong passwords, multi-factor authentication, and network access controls are in place for administrator accounts
    Affected if Administrator credentials could be compromised, as the attacker requires valid administrator credentials to trigger the NULL pointer dereference

The environment is affected if the device runs QTS or QuTS hero with a version number that falls within any of the affected version ranges AND the attacker could obtain 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

Upgrade QNAP devices to the specified fixed firmware versions (QTS 5.2.9.3492+, QuTS hero h5.2.9.3499+, h5.3.4.3500+, or h6.0.0.3459+) and review administrative accounts for any signs of compromise.

Recommended fix High confidence

QTS 5.2.9.3492 (build 20260507); QuTS hero h5.2.9.3499 (build 20260514); QuTS hero h5.3.4.3500 (build 20260520); QuTS hero h6.0.0.3459 (build 20260409)

  1. 1. Identify the current QNAP product (QTS or QuTS hero) and version by logging into the QNAP admin interface.
  2. 2. For QTS: If running version >= 5.2.0.2737 and < 5.2.9.3492, upgrade to QTS 5.2.9.3492 (build 20260507) or later.
  3. 3. For QuTS hero h5.x: If running version >= h5.0.0 and < h5.2.9.3499, upgrade to h5.2.9.3499 (build 20260514) or later; if running version >= h5.3.0.3115 and < h5.3.4.3500, upgrade to h5.3.4.3500 (build 20260520) or later.
  4. 4. For QuTS hero h6.x: If running version >= h6.0.0.3324 and < h6.0.0.3459, upgrade to h6.0.0.3459 (build 20260409) or later.
  5. 5. Download the firmware update from the QNAP Support Download Center and apply via Control Panel > Firmware Update, or use the auto-update feature.
  6. 6. After upgrade, verify the new version matches or exceeds the fixed build numbers above.

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-24716 — 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-24716 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