dbcve.org
File StationApplication · Qnap

CVE-2025-29900

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 · moderate confidence

This is a resource exhaustion vulnerability in QNAP File Station 5 where authenticated users can allocate resources without proper limits or throttling. A remote attacker with a valid user account can exploit this to consume excessive resources, preventing other systems, applications, or processes from accessing the same type of resource (file operations). This effectively creates a denial-of-service condition through uncontrolled resource allocation.

MitigationUpdate File Station 5 to version 5.5.6.4907 or later to apply the vendor patch. Additionally, enforce the principle of least privilege for user accounts and monitor for anomalous resource consumption patterns.

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. Verify File Station 5 is installed
    Access the QNAP admin interface and navigate to the applications or App Center to confirm File Station 5 is installed and running on the system.
    Affected if File Station 5 is not installed on the QNAP device.
  2. Determine the installed File Station version
    In the QNAP admin interface, locate the File Station application details or version information. This is typically found in App Center by clicking on File Station and viewing its properties, or via the command line using qpkg commands if available.
    Affected if Unable to retrieve the version number for comparison.
  3. Compare version against affected range
    Check if the installed version falls within >= 5.5.6.4691 and < 5.5.6.4907. If the version is 5.5.6.4907 or later, the vulnerability is patched. If it is 5.5.6.4691 or later but below 5.5.6.4907, the system is affected.
    Affected if Installed version is 5.5.6.4691 or later but earlier than 5.5.6.4907.
  4. Confirm remote authentication is enabled
    Review the File Station and QNAP system settings to determine if remote access or network sharing features are enabled that allow authenticated users to access File Station over the network.
    Affected if Remote or network-based authenticated access to File Station is enabled, allowing a remote authenticated user to trigger the resource exhaustion.

You are affected if File Station 5 is installed with a version between 5.5.6.4691 and 5.5.6.4906 inclusive, and authenticated users can access it remotely or over the network.

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 to apply the vendor patch. Additionally, enforce the principle of least privilege for user accounts and monitor for anomalous resource consumption patterns.

Recommended fix High confidence

File Station 5 version 5.5.6.4907 or later

  1. 1. Identify the current version of File Station 5 installed on the QNAP NAS by accessing the QNAP admin interface
  2. 2. Navigate to the App Center or File Station application settings to verify the version number
  3. 3. If the installed version is between 5.5.6.4691 and 5.5.6.4906 (exclusive), update to version 5.5.6.4907 or later
  4. 4. Update through the QNAP App Center or download the updated File Station 5 package from the official QNAP website
  5. 5. After installation, verify the new version is 5.5.6.4907 or higher

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-29900 — 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-29900 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