DE EN IT

~/exploited / cve-2021-3199

CVE-2021-3199: ONLYOFFICE Docs

According to CISA this vulnerability is already used in attacks (added on 8 October 2026).

Key facts

CVECVE-2021-3199
VendorONLYOFFICE — Docs
VulnerabilityONLYOFFICE Docs Server Path Traversal Vulnerability
Added8 October 2026
Deadline (US agencies)11 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score9.8 (critical) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 88.14%. Higher than 99.8% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-22 — Path Traversal
Affected versionsdocument server: < 5.6.3

Description (NVD)

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.

Description (CISA)

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.

Required action (CISA)

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). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether ONLYOFFICE Docs is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 8 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).