dbcve.org
Quts HeroOperating system · Qnap

CVE-2025-47208

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
An allocation of resources without limits or throttling vulnerability has been reported to affect several QNAP operating system versions. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource. We have already fixed the vulnerability in the following versions: QTS 5.2.6.3195 build 20250715 and later QuTS hero h5.2.6.3195 build 20250715 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 resource exhaustion vulnerability (CWE-770) in QNAP QTS and QuTS hero operating systems where an authenticated remote attacker can allocate resources without proper limits or throttling, effectively monopolizing system resources and preventing other systems, applications, or processes from accessing the same type of resource.

MitigationUpdate to QTS 5.2.6.3195 build 20250715 or QuTS hero h5.2.6.3195 build 20250715 or later. Since the vulnerability requires a compromised user account, also ensure strong password policies and consider implementing account lockout 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
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
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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 system type
    Log into the QNAP admin interface and check System Information > Overview, or run 'getsysinfo' via SSH to determine if the system is running QTS or QuTS hero
    Affected if System is not QTS or QuTS hero (this CVE only applies to these products)
  2. Check the installed QTS or QuTS hero version
    In the admin interface go to Control Panel > System > Firmware Update > Check for Update, or run 'qts_version' (QTS) or 'quts_version' (QuTS hero) via SSH to obtain the exact build number
    Affected if The installed version matches any of these: QTS 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; or QuTS hero 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
  3. Verify remote authentication exposure
    Check if the QNAP admin interface is accessible from the network (go to Control Panel > System > General Settings > Security and review access permissions), and review user accounts in Control Panel > Privilege > Users to see which accounts have remote access privileges
    Affected if The QNAP admin interface is network-accessible and there are user accounts with remote login capabilities, allowing an authenticated attacker to trigger the resource exhaustion

You are affected if your system runs QTS or QuTS hero AND your installed version matches any of the listed affected versions AND the admin interface is network-accessible with user accounts that can authenticate remotely.

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 to QTS 5.2.6.3195 build 20250715 or QuTS hero h5.2.6.3195 build 20250715 or later. Since the vulnerability requires a compromised user account, also ensure strong password policies and consider implementing account lockout policies.

Recommended fix High confidence

QTS 5.2.6.3195 build 20250715 and later / QuTS hero h5.2.6.3195 build 20250715 and later

  1. Identify whether the system is running QTS or QuTS hero
  2. Check current firmware version using the QNAP Control Panel > System > Firmware page
  3. If running an affected version (QTS 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802 / QuTS hero h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802), plan the upgrade
  4. Backup critical data and configurations before proceeding with firmware upgrade
  5. Download the fixed firmware (QTS 5.2.6.3195 build 20250715 or later / QuTS hero h5.2.6.3195 build 20250715 or later) from the QNAP download center
  6. Install the firmware update via Control Panel > System > Firmware > Firmware Update
  7. Verify the system is now running version 5.2.6.3195 build 20250715 or later

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

Fix this in Quts Hero Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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