dbcve.org
QtsOperating system · Qnap

CVE-2025-48725

HIGH · 8.1 CVSS v3.1 Published 2026-02-11
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 version: QuTS hero h5.3.2.3354 build 20251225 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

Buffer overflow vulnerability in QNAP NAS operating systems that requires an authenticated user account before exploitation. A remote attacker who has obtained valid credentials can trigger the overflow to modify memory contents or cause denial of service by crashing processes.

MitigationUpdate affected QNAP devices to QuTS hero h5.3.2.3354 build 20251225 or later. Additionally, enforce strong credential policies and monitor for unauthorized account creation to prevent the prerequisite access needed for exploitation.

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
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 QTS version
    Access the QNAP admin console and navigate to Control Panel > System > Firmware, or run `cat /proc/version` via SSH to retrieve the installed QTS build number
    Affected if The build number matches any of these: 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
  2. Identify QuTS Hero version
    Access the QNAP admin console and navigate to Control Panel > System > Firmware, or run `cat /proc/version` via SSH to retrieve the installed QuTS Hero build number
    Affected if The build number matches any of these: 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
  3. Verify remote access configuration
    Check if the QNAP device has remote management ports (HTTP/HTTPS for admin console) exposed to the network or internet via router port forwarding or firewall rules
    Affected if Remote admin access is enabled and reachable from untrusted networks, allowing a remote attacker to attempt authentication
  4. Audit user accounts
    Review the list of local users in Control Panel > Privilege > Users, or run `getent passwd` via SSH to enumerate all accounts
    Affected if There are any user accounts present, since the attacker needs valid credentials for at least one account to exploit the buffer overflow

A device is affected if it runs any of the listed QTS or QuTS Hero versions AND has network accessibility that allows an attacker to authenticate with valid 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

Update affected QNAP devices to QuTS hero h5.3.2.3354 build 20251225 or later. Additionally, enforce strong credential policies and monitor for unauthorized account creation to prevent the prerequisite access needed for exploitation.

Recommended fix Moderate confidence

QuTS hero h5.3.2.3354 build 20251225 or later

  1. Identify your current QNAP operating system version (QTS or QuTS hero) via the Control Panel > System > Firmware version
  2. For QuTS hero systems: Upgrade to version h5.3.2.3354 build 20251225 or later to remediate the buffer overflow vulnerability
  3. For QTS systems: Monitor QNAP security advisories for corresponding fix releases as the official fix reference only lists QuTS hero h5.3.2.3354
  4. After upgrading, verify the new firmware version matches or exceeds the fixed release
  5. Ensure user account security best practices are followed - limit the number of user accounts and enforce strong passwords, as the vulnerability requires a valid user account to exploit
Caveat Firmware upgrades carry inherent risks; backup critical data before proceeding and ensure the device has stable power during the update 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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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