# CVE-2026-110652: ONLYOFFICE DocumentServer before 10.0.0 SSRF via downloadfile isInJwtToken Bypass

> Remote attackers can bypass IP filtering to access internal network resources and cloud metadata via the downloadfile endpoint when JWT verification is disabled.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-hfqc-w8rp-668p

## What is CVE-2026-110652?

CVE-2026-110652 is a medium-severity server-side request forgery vulnerability in ONLYOFFICE DocumentServer, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ONLYOFFICE DocumentServer before 10.0.0 contains an unauthenticated server-side request forgery vulnerability in the /downloadfile/:docid endpoint that allows remote attackers to bypass the private-IP request-filtering-agent by exploiting the isInJwtToken flag when JWT verification is disabled in the default configuration. Attackers can submit a crafted request body containing an internal or loopback URL, which is treated as a DIRECT request skipping private-address filtering, causing the server to fetch and proxy back arbitrary private-network and cloud metadata content.

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

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


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

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

## Is CVE-2026-110652 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110652 is a medium-severity server-side request forgery vulnerability in ONLYOFFICE DocumentServer, published on 14 Oct 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-2026-110652 in the wild and no public exploit code.

Affected product: ONLYOFFICE DocumentServer. 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-110652/ (Markdown: https://insights.sbomify.com/CVE-2026-110652/index.md)
```

## Sources

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

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