Skip to main content
Menu
CVEs

CVE

ONLYOFFICE Docs authorization bypass in document export

CVE-2026-113631EUVD-2026-126501GHSA-FCQJ-MCHH-9J6F

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 10.0.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 10.0.0.

Published
Last modified
Reference
Last checked
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

ONLYOFFICE Docs (Document Server) has a flaw that lets a logged-in, view-only user export a rebuilt copy of a document containing content they never saw, such as custom XML, custom document properties and field instruction text, even when downloading and form-filling are disabled. Reached remotely over the network, the user reconnects with a valid session token while substituting an attacker-controlled callback URL, then calls sendForm so the server sends the rebuilt DOCX file to that URL.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Incorrect authorization in the sendForm RPC handler and Session JWT reconnect handling in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows an authenticated view-only user to export a reconstructed copy of a document, including content the viewer never displayed such as custom XML, custom document properties and field instruction text, even when download and form-filling are disabled. The attacker reconnects with a valid Session JWT while substituting an attacker-controlled callback URL, which the Session JWT does not bind, then invokes sendForm over RPC, causing DocumentServer to send the reconstructed DOCX to that URL.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 10.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-113631 (ONLYOFFICE Docs View-Only Users Can Export Non-Rendered Document Data via sendForm Callback URL Replacement), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-113631 (entry last updated 2026-11-16):
Affected:
- ONLYOFFICE Docs (Document Server): from 9.4.0-129, fixed in 10.0.0
Fixed versions: 10.0.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-113631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113631 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.rapid7.com/blog/post/ve-from-view-only-access-to-container-root-five-vulnerabilities-in-onlyoffice-docs-fixed/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-113631
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-113631"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • ONLYOFFICE Docs (Document Server)

    From 9.4.0-129 · fixed in 10.0.0

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-113631

Is CVE-2026-113631 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-113631?

Docs (Document Server): from 9.4.0-129 before 10.0.0.Source: cve.now feed data

How do I fix CVE-2026-113631?

Upgrade to a fixed version: 10.0.0.Source: cve.now feed data