CVE-2026-113631 · Package
NO FIX YET
ONLYOFFICE Docs (Document Server) 9.4.0-129 lets a user with view-only access export a rebuilt copy of a document, including hidden content such as custom XML and document properties, even when download is disabled. The attacker swaps in their own callback URL on reconnect so the server sends the reconstructed DOCX to them.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run ONLYOFFICE Docs (Document Server) themselves, most likely through the official onlyoffice/documentserver container, and share documents with view-only permissions. The attacker needs a valid view-only session, so servers where only trusted editors have access carry less exposure. Hosted or managed ONLYOFFICE services are handled by their vendor.
Not affected if managed-hosting, no-view-only-access
Who cares docker, document-server, onlyoffice, self-hosted
docker exec <container> cat /etc/onlyoffice/documentserver/product.json or the image tag, and compare against 9.4.0-129.No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.