dbcve.org
Quts HeroOperating system · Qnap

CVE-2025-52863

HIGH · 8.1 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 →
87/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 buffer overflow 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 modify memory or crash processes. We have already fixed the vulnerability in the following versions: QTS 5.2.7.3256 build 20250913 and later QuTS hero h5.2.7.3256 build 20250913 and later QuTS hero h5.3.0.3192 build 20250716 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

A buffer overflow vulnerability in QNAP QTS and QuTS hero operating systems allows an authenticated remote attacker to modify memory or crash processes. The attacker requires valid user credentials first (post-authentication), then exploits the buffer overflow to achieve memory corruption or denial of service.

MitigationApply the available firmware updates: QTS 5.2.7.3256 build 20250913, QuTS hero h5.2.7.3256 build 20250913, or QuTS hero h5.3.0.3192 build 20250716 or later. Prior to updating, ensure strong user account security to reduce the attack surface.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 firmware type
    Log into the QNAP admin interface and check System > Overview, or use the CLI command `getsysinfo` to determine if the device runs QTS or QuTS hero
    Affected if The device runs QTS or QuTS hero (other NAS platforms are not affected)
  2. Determine the installed firmware version
    In the web interface, go to Control Panel > System > Firmware Update to view the current version, or run `fw_version` via SSH
    Affected if The displayed version matches any of the affected version numbers listed for QTS or QuTS hero

The system is affected if it is running QTS or QuTS hero and the installed firmware version exactly matches one of the versions in the affected list (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 for QTS or 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.

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: QTS 5.2.7.3256 build 20250913, QuTS hero h5.2.7.3256 build 20250913, or QuTS hero h5.3.0.3192 build 20250716 or later. Prior to updating, ensure strong user account security to reduce the attack surface.

Recommended fix High confidence

QTS: 5.2.7.3256 build 20250913+ | QuTS hero: h5.2.7.3256 build 20250913+ or h5.3.0.3192 build 20250716+

  1. 1. Identify your current QNAP firmware version by logging into the QTS/QuTS hero web interface and checking System Administration > Firmware Version
  2. 2. Confirm your current version matches one of the affected versions: 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
  3. 3. For QTS systems: Upgrade to QTS 5.2.7.3256 build 20250913 or later via Control Panel > System > Firmware Update > Check for Update
  4. 4. For QuTS hero h5.2.x systems: Upgrade to h5.2.7.3256 build 20250913 or later via the same firmware update process
  5. 5. For QuTS hero h5.3.x systems: Upgrade to h5.3.0.3192 build 20250716 or later
  6. 6. After upgrade, verify the new firmware version matches the fixed builds specified above
  7. 7. Review user account security and ensure strong passwords are in place, as this vulnerability requires prior account compromise
Caveat Standard QNAP firmware upgrade risks apply - ensure power stability during update and backup critical data before proceeding

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

Fix this in Quts Hero Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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