dbcve.org
QtsOperating system · Qnap

CVE-2025-59385

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An authentication bypass by spoofing vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to access resources which are not otherwise accessible without proper authentication. We have already fixed the vulnerability in the following versions: QTS 5.2.7.3297 build 20251024 and later QuTS hero h5.2.7.3297 build 20251024 and later QuTS hero h5.3.1.3292 build 20251024 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 an authentication bypass vulnerability in QNAP operating systems where remote attackers can spoof authentication to gain unauthorized access to resources that would normally require proper authentication. The vulnerability is rated critical due to the ease of exploitation and complete compromise possible once authenticated.

MitigationUpdate affected QNAP devices to the fixed versions (QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024) as soon as possible to remediate the vulnerability.

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.0.2744= 5.2.0.2782= 5.2.0.2802= 5.2.0.2823= 5.2.0.2851= 5.2.0.2860= 5.2.1.2930= 5.2.2.2950= 5.2.3.3006= 5.2.4.3070= 5.2.4.3079
Quts HeroOperating system
Affected:= h5.2.0.2737= h5.2.0.2782= h5.2.0.2789= h5.2.0.2802= h5.2.0.2823= h5.2.0.2851= h5.2.0.2860= h5.2.1.2929= h5.2.1.2940= h5.2.2.2952= h5.2.3.3006= h5.2.4.3070

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

CVSS:3.1/AV:N/AC:L/PR:N/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 QNAP product type
    Log into the QNAP device and navigate to Control Panel > System > System Status, or run the command 'getsysinfo' via QCLI to determine if the device runs QTS or QuTS hero
    Affected if The device runs QTS or QuTS hero operating system
  2. Check QTS version
    Navigate to Control Panel > System > System Status > Firmware Version, or use the command 'getcfg System.Version' via QCLI to retrieve the exact firmware build number
    Affected if The version matches any of: 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, 5.2.0.2802, 5.2.0.2823, 5.2.0.2851, 5.2.0.2860, 5.2.1.2930, 5.2.2.2950, 5.2.3.3006, 5.2.4.3070, or 5.2.4.3079
  3. Check QuTS hero version
    Navigate to Control Panel > System > System Status > Firmware Version, or use the command 'getcfg System.Version' via QCLI to retrieve the exact firmware build number
    Affected if The version matches any of: h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802, h5.2.0.2823, h5.2.0.2851, h5.2.0.2860, h5.2.1.2929, h5.2.1.2940, h5.2.2.2952, h5.2.3.3006, or h5.2.4.3070
  4. Verify remote access is enabled
    Check Control Panel > Security > Security Level and verify if the QNAP device is accessible from external networks, or inspect the firewall rules in Control Panel > System > Firewall
    Affected if The device allows remote administrative access from untrusted networks

A device is affected if it runs any of the listed QTS or QuTS hero versions AND is accessible from network locations where attackers could exploit the authentication bypass.

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 the fixed versions (QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024) as soon as possible to remediate the vulnerability.

Recommended fix High confidence

QTS 5.2.7.3297 build 20251024 or later; QuTS hero h5.2.7.3297 build 20251024 or later; or QuTS hero h5.3.1.3292 build 20251024 or later

  1. 1. Identify your current QTS or QuTS hero version from the System Administration > Firmware page
  2. 2. If running an affected version (QTS 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, 5.2.0.2802 or QuTS hero h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802), initiate a firmware update
  3. 3. Download and install QTS 5.2.7.3297 (build 20251024) or later for QTS systems
  4. 4. For QuTS hero systems, download and install either h5.2.7.3297 (build 20251024) or later, OR h5.3.1.3292 (build 20251024) or later
  5. 5. After upgrade, verify the new firmware version is installed and the device is functioning normally
  6. 6. Consider reviewing authentication settings and enabling additional security controls such as IP access filtering
Caveat Standard firmware update risks apply - ensure backups are current and plan for brief downtime during the upgrade process

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-2025-59385 — 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-59385 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