dbcve.org
QtsOperating system · Qnap

CVE-2025-30273

HIGH · 8.1 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 →
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
An out-of-bounds write 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 or corrupt memory. 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 · moderate confidence

Out-of-bounds write vulnerability in QNAP QTS and QuTS hero operating systems allows a remote attacker with valid user credentials to write beyond allocated memory boundaries, corrupting memory and potentially achieving code execution.

MitigationUpdate affected QNAP devices to QTS 5.2.5.3145 build 20250526 or QuTS hero h5.2.5.3138 build 20250519 or later. Until patched, minimize network exposure and enforce strong account credentials 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
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 QNAP operating system type
    Log into QTS or QuTS hero admin panel and check System Settings > System Information > Firmware Version to determine if the device runs QTS or QuTS hero
    Affected if Device runs either QTS or QuTS hero operating system
  2. Check QTS firmware version
    In admin panel, go to Control Panel > System > Firmware Information and note the exact version number displayed (format: x.x.x.xxxx)
    Affected if Version matches 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 QuTS hero firmware version
    In admin panel, go to Control Panel > System > Firmware Information and note the exact version number displayed (format: h5.x.x.xxxx)
    Affected if Version matches 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

The device is affected if it runs QTS version 5.2.0.2737 through 5.2.4.3079 or QuTS hero version h5.2.0.2737 through h5.2.4.3070, and the attacker has valid user credentials to authenticate.

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 QTS 5.2.5.3145 build 20250526 or QuTS hero h5.2.5.3138 build 20250519 or later. Until patched, minimize network exposure and enforce strong account credentials to reduce the attack surface.

Recommended fix High confidence

QTS 5.2.5.3145 build 20250526 or later; QuTS hero h5.2.5.3138 build 20250519 or later

  1. 1. Identify which QNAP operating system is running on the device (QTS or QuTS hero).
  2. 2. Check the current version by navigating to Control Panel > System > Firmware Management > Firmware Information.
  3. 3. For QTS systems: If running version 5.2.0.2737, 5.2.0.2744, 5.2.0.2782, or 5.2.0.2802, upgrade to QTS 5.2.5.3145 (build 20250526) or later.
  4. 4. For QuTS hero systems: If running version h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, or h5.2.0.2802, upgrade to QuTS hero h5.2.5.3138 (build 20250519) or later.
  5. 5. Before upgrading, ensure the device has sufficient storage space and stable power. Back up critical data as a precaution.
  6. 6. Perform the firmware upgrade through Control Panel > System > Firmware Management > Check for Update, or manually download the firmware from the QNAP download center.
Caveat Ensure backup of critical data before upgrading; verify application compatibility with new QTS/QuTS hero versions

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

Fix this in Qts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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