Skip to main content
VulnerabilityPublished

CVE-2026-113631: ONLYOFFICE Docs (Document Server) · Missing Authorization

Affects ONLYOFFICE Docs (Document Server)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 10.0.0 when convenient.

Data as of 16 Nov 2026, 16:51 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (rapid7)CVSS 3.16.5
Patch
Available – fixed in 10.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade ONLYOFFICE Docs (Document Server) to 10.0.0.

Affected software

ProductAffectedFixed in
ONLYOFFICEDocs (Document Server)Affected
  • >=9.4.0-129 <10.0.0
Fixed in
  • 10.0.0

AI-suggested

A fix is available in ONLYOFFICE Docs (Document Server) version 10.0.0. Users should upgrade to version 10.0.0 or later to remediate this vulnerability. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

CVE-2026-113631 is an authorization vulnerability in ONLYOFFICE Docs (Document Server) versions 9.4.0-129 up to but not including 10.0.0. It allows an authenticated view-only user to export a reconstructed copy of a document, including content not displayed to the viewer, such as custom XML and document properties, even when download and form-filling are disabled. The exploit involves reconnecting with a valid Session JWT while substituting an attacker-controlled callback URL, which the JWT does not bind, then invoking the sendForm RPC handler to exfiltrate the document.

References

Community reviews

Loading reviews…