dbcve.org
File StationApplication · Qnap

CVE-2025-54169

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 5.5.6.5190 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 out-of-bounds read vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to obtain secret data. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5068 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 an out-of-bounds read vulnerability in QNAP File Station 5. A remote attacker who has obtained a valid user account can exploit this vulnerability to read beyond allocated memory boundaries, potentially exposing sensitive data such as secrets or other process memory contents.

MitigationUpdate File Station 5 to version 5.5.6.5068 or later. Additionally, enforce strong account credentials, limit the number of privileged accounts, and monitor for unusual access 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.5190

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm File Station 5 is installed
    Access the QNAP QTS admin interface and navigate to App Center to verify File Station 5 is installed, or use the command line to list installed QNAP applications.
    Affected if File Station 5 is present on the system
  2. Identify the installed File Station version
    In QTS, go to App Center, locate File Station 5, and note the version number displayed. Alternatively, access the NAS via SSH and query the package management system for the File Station version.
    Affected if Unable to determine the version number
  3. Compare version against affected range
    Review the identified version number and compare it to the affected range: version 5.5.6.4691 or higher AND version 5.5.6.5190 or lower (versions 5.5.6.4691 through 5.5.6.5189 are affected).
    Affected if The installed version falls within >= 5.5.6.4691 and < 5.5.6.5190
  4. Verify user account access exists
    Confirm that user accounts with valid credentials exist on the QNAP system, as the vulnerability requires a remote attacker to have obtained a valid user account.
    Affected if Valid user accounts are configured on the system

The environment is affected if File Station 5 is installed with version 5.5.6.4691 or higher but lower than 5.5.6.5190, and valid user accounts exist on the system.

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.5190 or later
Fixed in 5.5.6.5190
Interim mitigation

Update File Station 5 to version 5.5.6.5068 or later. Additionally, enforce strong account credentials, limit the number of privileged accounts, and monitor for unusual access patterns.

Recommended fix High confidence

File Station 5 version 5.5.6.5190 or later

  1. 1. Log in to the QNAP NAS administrative interface.
  2. 2. Navigate to File Station settings or the App Center to check the current File Station version.
  3. 3. If running a version lower than 5.5.6.5190, download File Station 5 version 5.5.6.5190 or later from the official QNAP website or QNAP App Center.
  4. 4. Install or update File Station to the new version.
  5. 5. Verify the installation by checking that File Station is now running version 5.5.6.5190 or later.
  6. 6. Confirm normal operation of File Station features.

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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