ONLYOFFICE Docs, CVE-2021-3199: on CISA's exploited list
The bottom line
If you run ONLYOFFICE Docs (Document Server) with JWT on, act now: CISA's date of 11 October 2026 has already passed. First find out whether it runs anywhere and which version; before 5.6.3 is affected. If you do not run it, stop reading.
At a glance
| Fact | Detail |
|---|---|
| Product | ONLYOFFICE Docs (CVE-2021-3199) |
| Severity | Critical: 9.8 (CVSS 3.1) |
| CISA | On its exploited list since 8 October 2026. Deadline for US federal agencies: 11 October 2026. |
| Chance of exploitation (EPSS) | 0.30, the estimated chance in the next 30 days, as at 6 November 2026 |
| Ransomware use | Not recorded by CISA. That is not the same as none. |
| Fixed in | No source we read names a fixed version |
| Who looks first | Anyone running ONLYOFFICE Document Server, called ONLYOFFICE Docs by CISA, with JWT turned on. Check first any copy that people outside your firm can reach. |
Does this apply to you?
| Question | If no | If yes |
|---|---|---|
| Do you or your IT provider run ONLYOFFICE Docs or Document Server anywhere? | Nothing to do for this CVE. | Find the version (next question). |
| Is the version before 5.6.3? | The record does not list it as affected; keep a note of the version. | Treat it as affected and go on. |
| Is JWT turned on for that server? | The record names JWT as a condition; confirm with your provider before you rely on that. | The stated condition is met; go on. |
| Can anyone outside your firm reach the server over the network? | Lower urgency, but still update it. | Restrict access now, then update. |
What it is
The record says an attacker can send a crafted image upload request to the server's /upload path. A /.. sequence in a parameter lets it step outside the intended folder (CWE-22). The record says this can lead to remote code execution, meaning the attacker runs commands on the server.
Exposure by situation
These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.
| Your situation | Priority | Timeframe |
|---|---|---|
| Server on a version before 5.6.3 with JWT on, reachable from the internet | High | Now; CISA's date has passed |
| Affected version with JWT on, reachable only from your internal network | Medium | This week |
| Version unknown, because a supplier or provider runs it for you | Medium | Ask this week |
| Version 5.6.3 or later | Low | Next patch cycle |
| You do not run ONLYOFFICE Docs | None | None for this CVE |
Things people will get wrong
- "It is a 2021 flaw, so it is long dead." CISA lists it as exploited, and any copy still before 5.6.3 stays in range however old the record is.
- "JWT is on, so uploads are protected." The record names JWT use as the condition under which the flaw occurs, not as a protection.
- "We use it through another product, so it is not ours." The sources do not say how it is packaged. Ask your provider whether a copy runs on your behalf.
How we would triage it
This is our judgement.
The commands only read: they print a version or list what is installed. They come from general knowledge of this kind of product, not from the sources, so check them against the vendor's page before you run them. Words in capitals are for you to fill in.
Step 1: Find the versions you run
- Ask your IT provider or supplier whether ONLYOFFICE Docs or Document Server runs anywhere on your estate.
- Record each version, as the record names versions before 5.6.3.
docker ps --format '{{.Names}} {{.Image}}' | grep -i onlyoffice
dpkg -l | grep -i onlyoffice
rpm -qa | grep -i onlyofficeStep 2: Reduce exposure
- Take any affected copy off the internet, or limit access to the people who need it, until it is updated.
- Do this first for copies that people outside your firm can reach.
Step 3: Update
- Move to a current release from the vendor. The sources name no fixed version beyond the record's "before 5.6.3", so get the target from the vendor.
- Ask for the new version in writing.
Step 4: Check for signs of misuse
- Review web server and application logs for upload requests containing /.. sequences.
- If any are found, treat the server as possibly compromised and involve your provider.
To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
Hello, CISA lists CVE-2021-3199, a path traversal flaw in ONLYOFFICE Docs (Document Server) that the record says can allow remote code execution when JWT is used. The record names versions before 5.6.3 as affected. Please tell us whether we run it anywhere, directly or through a supplier, and which version. If so, please update it and check its logs for unusual upload requests. Please confirm the version and the fix in writing by a date you suggest this week. Thank you.
Signs it was used
An update closes the hole. It does not tell you whether someone used it first. CISA's required action points to its forensic triage requirements (BOD 26-04). Look for:
- Upload requests in web or application logs whose paths contain /.. sequences.
- Files in the server's program folders that you did not put there or that changed unexpectedly.
- Unexpected outbound connections from the document server.
The weakness behind it
CISA's entry classes this as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Likely ATT&CK mapping
MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.
| The step, in plain words | Stage of an attack | Why we think so |
|---|---|---|
| Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page. | Initial Access: getting in | The flaw is in a web-facing upload endpoint that can be reached over HTTP without prior access to the host; a path traversal in the image upload parameter would likely be exploited by sending a crafted request directly to the public-facing Document Server. |
| Command and Scripting Interpreter (T1059): Running commands or scripts on a machine, such as a shell or PowerShell. | Execution: running the attacker's code | The PoC delivers a reverse shell payload by overwriting a server-side executable via the traversal, so successful exploitation would typically result in arbitrary command execution on the host through a scripting interpreter. |
How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.
MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.
The sources, in their words
CISA's catalogue entry:
ONLYOFFICE Docs contains a path traversal vulnerability that can occur when JWT is used, via a /.. sequence in an image upload parameter and could allow for remote code execution.
The CVE record, published by Mitre on 22 January 2021:
Directory traversal with remote code execution can occur in /upload in ONLYOFFICE Document Server before 5.6.3, when JWT is used, via a /.. sequence in an image upload parameter.
The record gives no version ranges. Use the vendor's advisory for the affected versions.
CISA's required action:
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).
Check your own project
If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2021-3199Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2021-3199A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- The sources do not name a fixed version or what the fix changed.
- The sources do not say how attacks were carried out in practice or who was targeted.
- It is not stated whether a default or weak JWT secret is needed for an attack to work.
- We have not tested this against any environment. Versions and scores are as the sources state them and as at 6 November 2026; the vendor's advisory wins where it differs.
- The sections headed "The bottom line", "Does this apply to you?", "What it is", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.
Sources
- CISA Known Exploited Vulnerabilities catalogue
- CVE record for CVE-2021-3199
- FIRST: Exploit Prediction Scoring System
- Advisory or release notes read: github.com/moehw/poc_exploits/blob/master/CVE-2021-3199/po
- Reference in the CVE record: github.com
- Reference in the CVE record: github.com
- Reference in the CVE record: github.com