dbcve.org
QtsOperating system · Qnap

CVE-2026-22893

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.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 · high confidence

This is a command injection vulnerability in QNAP QTS and QuTS hero operating systems. It requires an attacker to first compromise and obtain administrator-level credentials, then leverages the elevated access to inject and execute arbitrary operating system commands through vulnerable input handling. The vulnerability carries a CVSS score of 7.2 due to the prerequisite of admin access, but once exploited allows complete system compromise.

MitigationOrganizations should ensure administrator accounts use strong, unique passwords and enable multi-factor authentication. Update affected QNAP devices to the fixed versions (QTS 5.2.9.3410 build 20260214, QuTS hero h5.2.9.3410 build 20260214, h5.3.4.3500 build 20260520, or h6.0.0.3459 build 20260409 or later) as the primary remediation.

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.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 NAS operating system
    Log into the QNAP admin web interface and navigate to Control Panel > System > About, or run `getconf` from the QTS/QuTS command line to determine if the system is running QTS or QuTS hero
    Affected if The system is identified as either QTS or QuTS hero
  2. Determine the installed QTS version
    In the web interface, go to Control Panel > System > About and note the Build number and Version number displayed. From command line, run `getconf` to retrieve the version details
    Affected if The version is 5.2.0.2737 or later but earlier than 5.2.9.3410 (build 20260214)
  3. Determine the installed QuTS hero version
    In the web interface, go to Control Panel > System > About and note the Build number and Version number displayed. From command line, run `getconf` to retrieve version details
    Affected if The version is h5.2.0.2737 or later but earlier than h5.2.9.3410; OR h5.3.0.3115 or later but earlier than h5.3.4.3500; OR h6.0.0.3324 or later but earlier than h6.0.0.3459
  4. Verify administrator account exposure
    Review who has administrator-level credentials for the NAS and check if these accounts are accessible from untrusted networks or if default/weak credentials are in use
    Affected if Administrator credentials are exposed to untrusted networks or use weak/default passwords, combined with a vulnerable version

A system is affected if it runs QTS version 5.2.0.2737 through 5.2.9.3409, or QuTS hero version h5.2.0.2737 through h5.2.9.3409, h5.3.0.3115 through h5.3.4.3499, or h6.0.0.3324 through h6.0.0.3458, AND an 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.3410 or later
Fixed in 5.2.9.3410
Interim mitigation

Organizations should ensure administrator accounts use strong, unique passwords and enable multi-factor authentication. Update affected QNAP devices to the fixed versions (QTS 5.2.9.3410 build 20260214, QuTS hero h5.2.9.3410 build 20260214, h5.3.4.3500 build 20260520, or h6.0.0.3459 build 20260409 or later) as the primary remediation.

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.3459 (build 20260409+)

  1. 1. Identify the current QNAP firmware version by logging into the QTS or QuTS hero admin interface
  2. 2. Determine which product line and version branch is currently running (QTS, QuTS hero h5.2.x, h5.3.x, or h6.0.x)
  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.0.x users: Upgrade to QuTS hero h6.0.0.3459 build 20260409 or later
  7. 7. Download the firmware from the official QNAP download center and apply via the Administration > Firmware Update section
  8. 8. Verify the build number after upgrade matches or exceeds the required build for the respective version
Caveat Standard QNAP firmware upgrade risks apply - ensure backups of critical data and review release notes 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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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