dbcve.org
QtsOperating system · Qnap

CVE-2025-62848

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. The remote attackers can then exploit the vulnerability to launch a denial-of-service (DoS) attack. 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 · high confidence

This is a NULL pointer dereference vulnerability in QNAP QTS and QuTS hero operating systems. Remote attackers can exploit this flaw by triggering the NULL pointer dereference through crafted network requests, causing the affected service to crash and resulting in a denial-of-service condition.

MitigationApply the vendor-supplied patches by upgrading to QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024 or later.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 product type
    Log into the QNAP admin interface and check the operating system name displayed, or run 'uname -a' via SSH to determine if the system is running QTS or QuTS hero
    Affected if The system is running QTS or QuTS hero (this vulnerability only affects these products)
  2. Check the installed QTS version
    In QTS admin interface, go to Control Panel > System > Firmware Update > Firmware Information, or run 'getcfg system version' via SSH to retrieve the 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 the installed QuTS hero version
    In QuTS hero admin interface, go to Control Panel > System > Firmware Update > Firmware Information, or run 'getcfg system version' via SSH to retrieve the 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 network services are exposed
    Check if the QNAP administrative interfaces (HTTP/HTTPS on ports 80/443, or other management ports) are accessible from network segments outside your trusted internal network
    Affected if The QNAP admin interface is accessible from untrusted networks and the installed version is in the affected list

A system is affected if it runs QTS or QuTS hero with a version matching any of the specific build numbers listed and has accessible network management interfaces.

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 vendor-supplied patches by upgrading to QTS 5.2.7.3297 build 20251024, QuTS hero h5.2.7.3297 build 20251024, or QuTS hero h5.3.1.3292 build 20251024 or later.

Recommended fix High confidence

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

  1. 1. Log into the QNAP admin interface (QTS or QuTS hero)
  2. 2. Navigate to Control Panel > System > Firmware Update
  3. 3. Check for available updates or manually verify your current build version
  4. 4. If not already on a fixed build, initiate firmware update to QTS 5.2.7.3297 build 20251024 or later (for QTS systems)
  5. 5. For QuTS hero systems, update to either h5.2.7.3297 build 20251024 or h5.3.1.3292 build 20251024 or later
  6. 6. Allow the update to complete and system to reboot
  7. 7. After reboot, verify the system is running the patched build version

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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