dbcve.org
QtsOperating system · Qnap

CVE-2024-13086

HIGH · 7.5 CVSS v3.1 Published 2025-03-07
Fix available
A fix is available. Upgrade to 5.2.0.2851 or later.
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
An exposure of sensitive information vulnerability has been reported to affect product. If exploited, the vulnerability could allow remote attackers to compromise the security of the system. We have already fixed the vulnerability in the following version: QTS 5.2.0.2851 build 20240808 and later QuTS hero h5.2.0.2851 build 20240808 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 · low confidence

This is a sensitive information exposure vulnerability affecting QNAP QTS and QuTS hero NAS firmware. The vulnerability allows remote attackers to potentially compromise system security through exposure of sensitive data. The issue is addressed in QTS 5.2.0.2851 build 20240808 and QuTS hero h5.2.0.2851 build 20240808 and later.

MitigationUpgrade QNAP NAS devices running QTS or QuTS hero to version 5.2.0.2851 build 20240808 or later to remediate this vulnerability.

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.0.0, < 5.2.0.2851
Quts HeroOperating system
Affected:>= h5.0.0, < h5.2.0.2851

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 firmware type and version via CLI
    Access the NAS via SSH and run `cat /etc/version` to display the firmware version and build number, or use `getsysinfo sysfirmware`
    Affected if The displayed version is QTS 5.0.0 or later but earlier than 5.2.0.2851 build 20240808, or QuTS hero h5.0.0 or later but earlier than h5.2.0.2851 build 20240808
  2. Check firmware version via admin web interface
    Log into the QNAP admin console, go to Control Panel > System > Firmware, and note the displayed version and build number
    Affected if The version shown is within the affected ranges: QTS >= 5.0.0 and < 5.2.0.2851, or QuTS hero >= h5.0.0 and < h5.2.0.2851
  3. Verify build date of the firmware
    In the admin interface under Control Panel > System > Firmware, or via CLI with `cat /etc/version/builddate` to confirm the build date
    Affected if The build date is earlier than 20240808 for QTS or QuTS hero versions in the affected range

A user is affected if their QNAP NAS runs QTS or QuTS hero firmware version 5.0.0 to 5.2.0.2851 (or h5.0.0 to h5.2.0.2851 for QuTS hero) with build date before 20240808.

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
Upgrade available Upgrade to 5.2.0.2851 or later
Fixed in 5.2.0.2851
Interim mitigation

Upgrade QNAP NAS devices running QTS or QuTS hero to version 5.2.0.2851 build 20240808 or later to remediate this vulnerability.

Recommended fix High confidence

QTS 5.2.0.2851 build 20240808 (or later) / QuTS hero h5.2.0.2851 build 20240808 (or later)

  1. 1. Identify the current QNAP QTS or QuTS hero version by logging into the NAS admin interface and checking System Information > Firmware Version
  2. 2. Ensure the current version is within the affected range: QTS < 5.2.0.2851 or QuTS hero < h5.2.0.2851
  3. 3. Back up all critical data on the NAS before proceeding with any firmware update
  4. 4. Download the firmware update QTS 5.2.0.2851 (build 20240808) or QuTS hero h5.2.0.2851 (build 20240808) from the official QNAP download center
  5. 5. Apply the firmware update through the QNAP admin interface (Control Panel > System > Firmware Update) or QNAP Utility
  6. 6. Verify the update was successful by confirming the new firmware version matches 5.2.0.2851 build 20240808 or later
Caveat Review QNAP's release notes for 5.2.0.2851 to check for any compatibility or configuration changes before upgrading

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

Fix this in Qts Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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