CVE-2026-22894
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 · uneditedA path traversal vulnerability has been reported to affect File Station 6. If a remote attacker gains a user account, they can then exploit the vulnerability to read the contents of unexpected files or system data. We have already fixed the vulnerability in the following version: File Station 5 5.5.6.5190 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 confidenceQNAP File Station 6 contains a path traversal vulnerability where an authenticated remote attacker can use directory traversal sequences (e.g., ../) in file request parameters to access files and directories outside the intended storage root, potentially exposing sensitive system files.
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>= 5.5.6.4691, < 5.5.6.5190CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify File Station is installedAccess QNAP NAS admin interface and navigate to App Center to confirm File Station application is installed, or use QCLI command line tool if availableAffected if File Station is present on the system
-
Determine installed File Station versionIn QNAP admin interface, go to App Center > File Station > click the gear icon or 'About' to view the version number. Compare against the affected range: 5.5.6.4691 through 5.5.6.5189Affected if Installed version is 5.5.6.4691 or higher but lower than 5.5.6.5190
-
Confirm remote access is enabledCheck File Station settings to see if remote access or file sharing features are enabled, allowing remote authenticated users to access the File Station web interfaceAffected if Remote access to File Station is enabled and the web interface is accessible to users
-
Review for anomalous file access patternsCheck QNAP system logs and File Station access logs for requests containing '../' traversal sequences in file path parameters, especially from external IP addressesAffected if Logs show file requests containing '../' sequences accessing paths outside the configured shared folders
A system is affected if File Station version is 5.5.6.4691 or higher but below 5.5.6.5190, the application is accessible remotely, and an attacker with valid credentials could exploit the path traversal to access files outside intended storage boundaries.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.5.6.5190
Update File Station to version 5.5.6.5190 or later. If immediate patching is not possible, enforce strict user access controls, limit file operation permissions, and monitor for anomalous file access patterns using ../ sequences.
File Station 5.5.6.5190 or later (File Station 5)
- Log into the QNAP NAS device with administrator credentials
- Open App Center or the File Station application
- Check current File Station version (should be >= 5.5.6.4691 and < 5.5.6.5190 to be vulnerable)
- Update File Station to version 5.5.6.5190 or later through the QNAP firmware/software update mechanism
- Verify the update was successful by checking the File Station version after upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-22894 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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