# CVE-2026-39989: SSRF in QNAP Download Station

> A remote attacker with a user account can exploit an SSRF vulnerability in QNAP Download Station to read application data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gxh4-v8pp-4j5f

## What is CVE-2026-39989?

CVE-2026-39989 is a medium-severity server-side request forgery vulnerability in QNAP Systems Inc. Download Station, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A server-side request forgery (SSRF) vulnerability has been reported to affect Download Station. If a remote attacker gains a user account, they can then exploit the vulnerability to read application data.

We have already fixed the vulnerability in the following version:
Download Station 5.10.1.312 and later
Download Station 5.11.2.321 and later

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-39989?


## How do I fix CVE-2026-39989?

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

## Is CVE-2026-39989 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39989 and fix it if it is affected.

What it is: CVE-2026-39989 is a medium-severity server-side request forgery vulnerability in QNAP Systems Inc. Download Station, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39989 in the wild and no public exploit code.

Affected product: QNAP Systems Inc. Download Station. 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-2026-39989/ (Markdown: https://insights.sbomify.com/CVE-2026-39989/index.md)
```

## Sources

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

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