dbcve.org
QtsOperating system · Qnap

CVE-2024-14026

HIGH · 7.8 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 an attacker gains local network access who have also gained a user account, they can then exploit the vulnerability to execute arbitrary commands. We have already fixed the vulnerability in the following versions: QTS 5.1.9.2954 build 20241120 and later QTS 5.2.3.3006 build 20250108 and later QuTS hero h5.1.9.2954 build 20241120 and later QuTS hero h5.2.3.3006 build 20250108 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

Authenticated command injection vulnerability in QNAP QTS and QuTS hero operating systems. An attacker with local network access and valid user credentials can execute arbitrary commands on the underlying system, potentially leading to full system compromise.

MitigationUpdate affected QNAP devices to QTS 5.1.9.2954 (build 20241120), QTS 5.2.3.3006 (build 20250108), QuTS hero h5.1.9.2954 (build 20241120), or QuTS hero h5.2.3.3006 (build 20250108) or later. Additionally, restrict network exposure and enforce strong credential policies.

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.1.0.2348= 5.1.0.2399= 5.1.0.2418= 5.1.0.2444= 5.1.0.2466= 5.1.1.2491= 5.1.2.2533= 5.1.3.2578= 5.1.4.2596= 5.1.5.2645= 5.1.5.2679= 5.1.6.2722
Quts HeroOperating system
Affected:= h5.1.0.2409= h5.1.0.2424= h5.1.0.2453= h5.1.0.2466= h5.1.1.2488= h5.1.2.2534= h5.1.3.2578= h5.1.4.2596= h5.1.5.2647= h5.1.5.2680= h5.1.6.2734= h5.1.7.2770

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 type
    Log into the QNAP device and navigate to Control Panel > System > General Settings, or run the command 'getcfg system.version' via QCLI to determine if the system is running QTS or QuTS hero
    Affected if The device is running either QTS or QuTS hero operating system
  2. Determine the installed QTS version and build number
    Navigate to Control Panel > System > Firmware Update, or run the command 'cat /proc/version' or 'firmware-version' to retrieve the exact version and build number (for example, 5.1.6.2722)
    Affected if The version matches any of these: 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444, 5.1.0.2466, 5.1.1.2491, 5.1.2.2533, 5.1.3.2578, 5.1.4.2596, 5.1.5.2645, 5.1.5.2679, or 5.1.6.2722
  3. Determine the installed QuTS hero version and build number
    Navigate to Control Panel > System > Firmware Update, or run 'cat /proc/version' to retrieve the exact version (for example, h5.1.6.2734)
    Affected if The version matches any of these: h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466, h5.1.1.2488, h5.1.2.2534, h5.1.3.2578, h5.1.4.2596, h5.1.5.2647, h5.1.5.2680, h5.1.6.2734, or h5.1.7.2770
  4. Assess network exposure
    Check the network configuration in Control Panel > Network & Virtual Switch > Physical Network Interface to determine if the device management interface is exposed to untrusted networks
    Affected if The device is accessible from the internet or untrusted local networks without proper access controls

The environment is affected if the device runs QTS versions 5.1.0.2348 through 5.1.6.2722 or QuTS hero versions h5.1.0.2409 through h5.1.7.2770 and has network accessibility with user authentication enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected QNAP devices to QTS 5.1.9.2954 (build 20241120), QTS 5.2.3.3006 (build 20250108), QuTS hero h5.1.9.2954 (build 20241120), or QuTS hero h5.2.3.3006 (build 20250108) or later. Additionally, restrict network exposure and enforce strong credential policies.

Recommended fix High confidence

QTS 5.1.9.2954 (build 20241120) or QTS 5.2.3.3006 (build 20250108); QuTS hero h5.1.9.2954 (build 20241120) or QuTS hero h5.2.3.3006 (build 20250108)

  1. 1. Identify your current QTS or QuTS hero firmware version by accessing the QNAP admin interface and navigating to Control Panel > System > Firmware Update
  2. 2. Determine whether your current version matches the affected versions: QTS 5.1.0.2348, 5.1.0.2399, 5.1.0.2418, 5.1.0.2444 or QuTS hero h5.1.0.2409, h5.1.0.2424, h5.1.0.2453, h5.1.0.2466
  3. 3. Download the appropriate fixed firmware version from QNAP's official support website: QTS 5.1.9.2954 (build 20241120) or later, or QTS 5.2.3.3006 (build 20250108) or later for QTS systems; QuTS hero h5.1.9.2954 (build 20241120) or later, or QuTS hero h5.2.3.3006 (build 20250108) or later for QuTS hero systems
  4. 4. In the QNAP admin interface, go to Control Panel > System > Firmware Update and select the option to update manually with the downloaded firmware file
  5. 5. Wait for the firmware update to complete and the system to reboot; do not power off the device during the update process
Caveat Firmware updates may cause downtime and can occasionally affect installed applications or configurations; ensure backups are made before upgrading

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 help mitigating

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-2024-14026 — 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-2024-14026 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