dbcve.org
File StationApplication · Qnap

CVE-2025-29890

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-29
Fix available
A fix is available. Upgrade to 5.5.6.4907 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 5. 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.4907 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 resource exhaustion vulnerability in QNAP File Station 5 where the application fails to impose limits or throttling on resource allocation. A remote attacker who obtains valid user credentials can exploit this to consume excessive system resources, effectively denying access to File Station services for other legitimate users or processes.

MitigationUpdate File Station 5 to version 5.5.6.4907 or later. Ensure user account security is maintained and consider implementing network-level access controls 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
File StationApplication
Affected:>= 5.5.6.4691, < 5.5.6.4907

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. Locate File Station version in QNAP admin console
    Log into the QNAP NAS admin interface, navigate to App Center or Control Panel, find File Station 5 in the installed applications list, and note the version number displayed.
    Affected if The displayed version is 5.5.6.4691 or higher but lower than 5.5.6.4907
  2. Verify File Station 5 is the installed package
    Confirm through QNAP App Center that the installed package is specifically File Station version 5 (not File Station 6 or another file management tool). The vulnerability affects only File Station 5.x.
    Affected if File Station version 5.x is installed and the version falls within the affected range
  3. Check version via command line if available
    Access the QNAP NAS via SSH and run: `qpkg -i | grep -i 'file station'` or check `/share/CACHEDEV1_DATA/.qpkg/FileStation5/` for version metadata. The version info may also be in `/etc/config/qpkg.conf`.
    Affected if The retrieved version matches 5.5.6.4691 through 5.5.6.4906, indicating the unpatched vulnerable versions

A user is affected if QNAP File Station 5 is installed with a version between 5.5.6.4691 and 5.5.6.4906 inclusive, as these versions lack resource throttling protections against exhaustion attacks.

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.4907 or later
Fixed in 5.5.6.4907
Interim mitigation

Update File Station 5 to version 5.5.6.4907 or later. Ensure user account security is maintained and consider implementing network-level access controls to reduce the attack surface.

Recommended fix High confidence

File Station 5.5.6.4907

  1. Log in to the QNAP NAS as an administrator
  2. Open the App Center or navigate to File Station settings
  3. Check for available updates for File Station 5
  4. Update File Station to version 5.5.6.4907 or later
  5. Verify the update was successful by checking the File Station version in the application settings

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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