dbcve.org
File StationApplication · Qnap

CVE-2025-29901

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 5.5.6.4933 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.4933 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

CVE-2025-29901 is a NULL pointer dereference vulnerability in QNAP File Station 5. An authenticated remote attacker can exploit this flaw to cause a denial-of-service condition. The vulnerability requires the attacker to first obtain valid user credentials before triggering the NULL pointer dereference.

MitigationUpdate File Station 5 to version 5.5.6.4933 or later. Additionally, enforce strong password policies and consider network segmentation to limit exposure of the management interface.

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.4933

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. Confirm File Station 5 is installed
    Access the QNAP NAS admin interface, open App Center, and look for File Station in the installed applications list. Alternatively, check via command line using qpkg command if available.
    Affected if File Station 5 is not present on the system, the vulnerability does not apply.
  2. Identify the installed File Station version
    In the QNAP App Center, click on File Station and view the version information displayed. The version number is shown in the format x.x.x.xxxx.
    Affected if Unable to determine the version means the check is inconclusive.
  3. Compare version to affected range
    Verify the installed version against the vulnerable range: versions 5.5.6.4691 through 5.5.6.4932 are affected. Versions below 5.5.6.4691 or at and above 5.5.6.4933 are not vulnerable.
    Affected if The installed version falls within >= 5.5.6.4691 and < 5.5.6.4933, meaning the system may be affected.
  4. Verify authentication requirements
    The vulnerability requires valid user credentials to exploit. Check whether user accounts are configured on the NAS and whether File Station remote access is enabled.
    Affected if If the NAS has no users configured or File Station remote access is disabled, exploitation is less likely but the vulnerable code may still be present.

The system is affected if File Station 5 is installed with a version between 5.5.6.4691 and 5.5.6.4932 inclusive, regardless of whether remote access is currently enabled.

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.4933 or later
Fixed in 5.5.6.4933
Interim mitigation

Update File Station 5 to version 5.5.6.4933 or later. Additionally, enforce strong password policies and consider network segmentation to limit exposure of the management interface.

Recommended fix High confidence

File Station 5 version 5.5.6.4933 or later

  1. Log in to the QNAP NAS as an administrator
  2. Open App Center or the File Station application
  3. Check the current installed version of File Station 5
  4. If the installed version is less than 5.5.6.4933, update File Station to version 5.5.6.4933 or later
  5. Verify the update was successful by confirming the new version number

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