dbcve.org
File StationApplication · Qnap

CVE-2025-29879

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 cause a denial-of-service condition. Exploitation requires the attacker to first obtain valid user credentials for the system.

MitigationUpgrade File Station to version 5.5.6.4907 or later. If immediate upgrade is not possible, limit user account access and restrict network exposure to the File Station service.

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 is installed
    Log into the QNAP QTS admin interface, open App Center, and look for File Station in the installed applications list. Alternatively, access File Station via its web URL (typically https://[nas-ip]/filestation/) to confirm it is accessible.
    Affected if File Station is not installed on the QNAP device, this CVE does not apply.
  2. Locate the File Station version number
    In the QTS App Center, click on File Station and view the version information displayed under the application name. Or, access File Station and check the version via the application settings or about dialog.
    Affected if Unable to locate File Station version indicates it may not be installed or accessible.
  3. Compare installed version against the affected range
    Compare the discovered version number to the affected range: versions 5.5.6.4691 through 5.5.6.4906 are vulnerable. Versions below 5.5.6.4691 or at/below 5.5.6.4907 are not affected.
    Affected if The installed version falls within >= 5.5.6.4691 and < 5.5.6.4907, meaning the environment is vulnerable to this CVE.
  4. Confirm authentication requirements for exploitation
    Note that exploitation requires valid user credentials for the QNAP system. Review which user accounts have access to File Station and assess the exposure of these credentials.
    Affected if File Station is accessible to untrusted users or the credential exposure risk is high, the impact of this vulnerability is elevated.

A QNAP device running File Station with a version between 5.5.6.4691 and 5.5.6.4906 inclusive is affected by this CVE, provided the attacker can obtain valid credentials to authenticate to 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.4907 or later
Fixed in 5.5.6.4907
Interim mitigation

Upgrade File Station to version 5.5.6.4907 or later. If immediate upgrade is not possible, limit user account access and restrict network exposure to the File Station service.

Recommended fix High confidence

File Station 5 version 5.5.6.4907 or later

  1. 1. Log into the QNAP NAS admin interface
  2. 2. Navigate to File Station application settings
  3. 3. Check the current installed version of File Station (should be >= 5.5.6.4691 and < 5.5.6.4907)
  4. 4. Update File Station to version 5.5.6.4907 or later via QNAP App Center or firmware update mechanism
  5. 5. After updating, verify the installed 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
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA0.5 h
4.5 hours of engineering $770
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,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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