dbcve.org
QtsOperating system · Qnap

CVE-2025-30274

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-29
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
A NULL pointer dereference vulnerability has been reported to affect several QNAP operating system versions. If 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.5.3145 build 20250526 and later QuTS hero h5.2.5.3138 build 20250519 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. An unauthenticated attacker can exploit this flaw to crash the affected system, resulting in a denial-of-service condition. The vulnerability has been addressed in QTS 5.2.5.3145 build 20250526 and QuTS hero h5.2.5.3138 build 20250519.

MitigationOrganizations should identify all affected QNAP devices in their environment and update firmware to the fixed versions (QTS 5.2.5.3145 build 20250526 or later / QuTS hero h5.2.5.3138 build 20250519 or later). Schedule maintenance windows to apply patches and verify system availability after updates.

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
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 or run `getsysinfo` via SSH to determine if the system is running QTS or QuTS hero
    Affected if System is either QTS or QuTS hero but the specific product type cannot be determined for version matching
  2. Check the installed QTS firmware version
    Access the admin web interface (System Administration > Firmware) or run `getcfg` system version command via SSH
    Affected if 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 firmware version
    Access the admin web interface (System Administration > Firmware) or run `getcfg` system version command via SSH
    Affected if 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 the build number if version appears close to boundary
    Check the full build number displayed in System Administration > Firmware or via `getsysinfo` command
    Affected if For QTS, build is earlier than 20250526; for QuTS hero, build is earlier than 20250519

The system is affected if it runs QTS or QuTS hero and the installed version matches any of the specific versions listed in the affected products list, regardless of configuration, since the vulnerability is exploitable by any unauthenticated network attacker.

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

Organizations should identify all affected QNAP devices in their environment and update firmware to the fixed versions (QTS 5.2.5.3145 build 20250526 or later / QuTS hero h5.2.5.3138 build 20250519 or later). Schedule maintenance windows to apply patches and verify system availability after updates.

Recommended fix High confidence

QTS 5.2.5.3145 (build 20250526 or later) for QTS systems; QuTS hero h5.2.5.3138 (build 20250519 or later) for QuTS hero systems

  1. 1. Identify the current QTS or QuTS hero version running on the NAS device
  2. 2. If the 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), plan to upgrade
  3. 3. Back up critical data before performing the firmware upgrade
  4. 4. For QTS systems: upgrade to QTS 5.2.5.3145 build 20250526 or later
  5. 5. For QuTS hero systems: upgrade to QuTS hero h5.2.5.3138 build 20250519 or later
  6. 6. After upgrade, verify the new version is running and the vulnerability is resolved
Caveat Firmware upgrades carry inherent risk; ensure data backup before proceeding and review QNAP release notes for any known issues

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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