dbcve.org
QtsOperating system · Qnap

CVE-2025-30268

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 a remote attacker gains a user account, they 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

A NULL pointer dereference vulnerability in QNAP QTS and QuTS hero operating systems allows an authenticated remote attacker to cause a denial-of-service condition. The attacker must first obtain valid user credentials to exploit this flaw, which triggers a crash via the dereferenced null pointer.

MitigationApply the vendor-released patches: update QTS to version 5.2.5.3145 build 20250526 or later, or QuTS hero to h5.2.5.3138 build 20250519 or later. Additionally, enforce strong authentication controls and minimize the number of user accounts 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
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 QNAP OS type and version
    Access the QNAP admin console and navigate to Control Panel > System > System Status, or run the command `cat /etc/config/def` to retrieve the firmware version details.
    Affected if The displayed version matches any of the listed affected versions: QTS 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 OR QuTS hero h5.2.0.2737, h5.2.0.2782, h5.2.0.2789, h5.2.0.2802, h5.2.0.2823, h5.2.0.2
  2. Confirm remote access is enabled
    In the QNAP admin console, go to Control Panel > System > General Settings > Security and verify if Allow remote connection or Web access from external networks is enabled. Alternatively, check the file `/etc/config/ssheb/ssheb.conf` for network exposure settings.
    Affected if Remote access or web-based administration interfaces are accessible from external networks.
  3. Review user account configuration
    Navigate to Control Panel > Privilege > Users or run `cat /etc/shadow` to enumerate local user accounts. Identify whether multiple user accounts exist with valid login credentials.
    Affected if More than one user account with valid credentials exists on the system, providing potential attack vectors for credential theft.
  4. Check access control settings
    Go to Control Panel > Security and review the Access Control settings to determine if IP restrictions or two-factor authentication are enforced for administrative logins.
    Affected if IP access restrictions are not enabled or two-factor authentication is not enforced, making credential-based attacks more feasible.

The environment is affected if the QNAP device runs QTS or QuTS hero at any of the specific versions listed AND remote authentication is accessible to potential attackers.

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-released patches: update QTS to version 5.2.5.3145 build 20250526 or later, or QuTS hero to h5.2.5.3138 build 20250519 or later. Additionally, enforce strong authentication controls and minimize the number of user accounts 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. Identify the currently installed QNAP OS version (QTS or QuTS hero) using the QNAP admin console or System Information
  2. If running QTS 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
  3. If running QuTS hero 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
  4. Perform the upgrade through QNAP's App Center or firmware update mechanism
  5. After upgrade, verify the new version is installed correctly

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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