# CVE-2025-59384: Qfiling

> Remote attackers can exploit a path traversal flaw in Qfiling to read unexpected files or system data.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-jqhp-ccp6-mgpw

## What is CVE-2025-59384?

CVE-2025-59384 is a high-severity path traversal vulnerability in QNAP Systems Inc. Qfiling, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability has been reported to affect Qfiling. The remote attackers 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:
Qfiling 3.13.1 and later

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-59384?

It affects 1 product.


Products: Qnap Qfiling.

## How do I fix CVE-2025-59384?

No fix has been published for CVE-2025-59384 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59384 being exploited?

There is no known exploitation of CVE-2025-59384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59384 and fix it if it is affected.

What it is: CVE-2025-59384 is a high-severity path traversal vulnerability in QNAP Systems Inc. Qfiling, published on 2 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59384 in the wild and no public exploit code.

Affected product: QNAP Systems Inc. Qfiling. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59384/ (Markdown: https://insights.sbomify.com/CVE-2025-59384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59384
- OSV: https://osv.dev/vulnerability/CVE-2025-59384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59384/
Summaries are generated and may contain mistakes; the official description above is the record.