dbcve.org
File StationApplication · Qnap

CVE-2026-24720

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 5.5.6.5243 or later.
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
An allocation of resources without limits or throttling vulnerability has been reported to affect File Station 6. If a remote attacker gains a user account, they can then exploit the vulnerability to prevent other systems, applications, or processes from accessing the same type of resource. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5243 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

This is a resource exhaustion vulnerability in QNAP File Station 6 where the application fails to implement proper limits or throttling on resource allocation. A remote attacker who has obtained valid user credentials can exploit this to consume excessive resources, thereby denying access to those same resources for other legitimate systems, applications, or processes.

MitigationApply the vendor patch by updating File Station to version 5.5.6.5243 or later. Additionally, enforce strict access controls on user accounts to reduce the attack surface, as the vulnerability requires a valid user account to exploit.

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
File StationApplication
Affected:>= 5.5.6.4691, < 5.5.6.5243

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. Confirm File Station is installed on the QNAP device
    Log into QTS and navigate to App Center, or run the command 'qpkg --status' via SSH to list installed QNAP packages and look for FileStation.
    Affected if File Station does not appear in the installed packages list.
  2. Identify the installed File Station version
    In QTS App Center, click on File Station and view the version information displayed, or check the version file at /share/CACHEDEV1_DATA/.qpkg/FileStation/package-version if accessible via SSH.
    Affected if The installed version is 5.5.6.4691 or any version from 5.5.6.4691 through 5.5.6.5242 (versions below 5.5.6.5243 are affected).
  3. Verify if remote access to File Station is enabled
    In QTS, go to Control Panel > Network & File Services > Win/Mac/NFS and check if SMB/FTP/WebDAV services that allow remote file access are enabled, or check if the myQNAPcloud service is configured.
    Affected if Remote access services (FTP, SMB with external access, WebDAV, or myQNAPcloud) are enabled and exposed to network attackers.
  4. Review user account configuration for File Station access
    In QTS, go to Control Panel > Privilege > Users and examine which local or domain users have permissions to access File Station and file shares.
    Affected if There are user accounts beyond the administrator that have File Station or file share access permissions.

You are affected if File Station is installed with a version between 5.5.6.4691 and 5.5.6.5242, remote access is enabled, and there are user accounts that could be compromised to exploit the resource exhaustion flaw.

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.5.6.5243 or later
Fixed in 5.5.6.5243
Interim mitigation

Apply the vendor patch by updating File Station to version 5.5.6.5243 or later. Additionally, enforce strict access controls on user accounts to reduce the attack surface, as the vulnerability requires a valid user account to exploit.

Recommended fix High confidence

File Station 5.5.6.5243 or later

  1. Log in to the QNAP NAS admin interface
  2. Navigate to App Center or the File Station settings
  3. Check current File Station version to confirm it's in the affected range (>= 5.5.6.4691, < 5.5.6.5243)
  4. Update File Station through the QNAP update mechanism or App Center
  5. Verify the installed version is 5.5.6.5243 or later

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

Fix this in File Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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