File StationApplication · Qnap

CVE-2025-29889

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
A NULL pointer dereference vulnerability has been reported to affect File Station 5. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. 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

A NULL pointer dereference vulnerability in QNAP File Station 5 allows an authenticated remote attacker to crash the application, causing denial of service. The attacker must first obtain valid user credentials before exploiting this vulnerability.

MitigationUpdate File Station to version 5.5.6.4907 or later. Since exploitation requires valid user accounts, enforce strong password policies and limit account access.

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 information
    Access the QNAP QTS web interface, navigate to App Center, find File Station in the installed applications list, and record the version number displayed
    Affected if The displayed version is 5.5.6.4691 through 5.5.6.4906 (any version >= 5.5.6.4691 but < 5.5.6.4907)
  2. Query File Station package via command line
    If you have SSH access to the QNAP NAS, run the command to query the File Station package version (typically via qpkg or similar package query tool)
    Affected if The returned version falls within 5.5.6.4691 to 5.5.6.4906 inclusive
  3. Verify File Station is running and accessible
    Confirm that the File Station web interface is accessible on the NAS (typically at /station/ or /file-station/)
    Affected if The service is running and the version is within the affected range, making it vulnerable to remote denial of service via the NULL pointer dereference

The environment is affected if QNAP File Station version is 5.5.6.4691 or any version up to 5.5.6.4906, since the NULL pointer dereference flaw exists in that specific version range.

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 to version 5.5.6.4907 or later. Since exploitation requires valid user accounts, enforce strong password policies and limit account access.

Recommended fix High confidence

File Station 5.5.6.4907 or later

  1. Log in to the QNAP NAS admin interface (QTS or QuTScloud)
  2. Navigate to App Center
  3. Search for File Station or locate it in the installed applications
  4. Check the current version of File Station to confirm it is below 5.5.6.4907
  5. Update File Station when the update (version 5.5.6.4907 or later) becomes available in App Center
  6. Alternatively, manually download File Station 5.5.6.4907 or later from the QNAP download center and install via App Center > Manual Install
  7. Verify the installed version is 5.5.6.4907 or higher after updating

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-29889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-29889 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