dbcve.org
Quts HeroOperating system · Qnap

CVE-2025-62850

HIGH · 7.2 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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: 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 · moderate confidence

A NULL pointer dereference vulnerability in QNAP QuTS hero OS that can be exploited by an attacker who already possesses administrator credentials to cause a denial-of-service condition.

MitigationApply the available firmware updates (QuTS hero h5.2.9.3410 build 20260214, h5.3.4.3500 build 20260520, or h6.0.0.3459 build 20260409 and later). Prior to patching, verify administrator account integrity and review access logs for potential 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
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. Locate QuTS hero version in admin console
    Log into the QNAP admin web interface, go to Control Panel > System > Firmware/Environment, and record the Build Number and Firmware Version displayed.
    Affected if The displayed version falls within h5.2.0.2737 to h5.2.9.3409, h5.3.0.3115 to h5.3.4.3499, or h6.0.0.3324 to h6.0.0.3458.
  2. Verify QuTS hero version via CLI
    Access the NAS via SSH using an administrator account, then run the command 'getsysinfo system' or 'cat /proc/board_version' to retrieve the firmware build number.
    Affected if The reported build number matches any of the affected version ranges listed above.
  3. Confirm remote admin access is enabled
    In the admin web interface, go to Control Panel > System > General Settings, and check whether 'Allow SSH connection' or the QNAP cloud management access is enabled.
    Affected if Remote SSH or cloud management access is enabled, making the system reachable for an authenticated remote attacker.
  4. Check for administrator account exposure
    Review the list of administrator accounts in Control Panel > Privilege > Administrators and verify that credentials are not shared, default, or compromised.
    Affected if Administrator credentials are weak, shared, or may have been compromised, enabling the attacker to exploit the vulnerability.

You are affected if your QuTS hero version is within any of the three vulnerable ranges AND remote administrator access is enabled or 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the available firmware updates (QuTS hero h5.2.9.3410 build 20260214, h5.3.4.3500 build 20260520, or h6.0.0.3459 build 20260409 and later). Prior to patching, verify administrator account integrity and review access logs for potential compromise.

Recommended fix High confidence

QuTS hero h5.2.9.3410 (build 20260214) or later / h5.3.4.3500 (build 20260520) or later / h6.0.0.3459 (build 20260409) or later depending on current branch

  1. Identify the current QuTS hero version running on the QNAP device via the admin console or command line
  2. Determine which version branch the current installation falls into (h5.2.x, h5.3.x, or h6.0.x)
  3. For systems on h5.2.x branch: upgrade to QuTS hero h5.2.9.3410 (build 20260214) or later
  4. For systems on h5.3.x branch: upgrade to QuTS hero h5.3.4.3500 (build 20260520) or later
  5. For systems on h6.0.x branch: upgrade to QuTS hero h6.0.0.3459 (build 20260409) or later
  6. Perform the upgrade via QNAP App Center or firmware update mechanism
  7. After upgrade, verify the new version is running and the vulnerability is resolved
Caveat Standard QNAP firmware upgrade risks apply - ensure backups of critical data and configuration are performed before upgrading

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

Fix this in Quts Hero Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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