Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Five ONLYOFFICE Docs Vulnerabilities and the View-Only Trust Boundary

ONLYOFFICE Docs vulnerabilities let view-only users cross permission boundaries in a tested build. Review five CVEs, the 10.0 fix, and deployment checks.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
17 November 2026
Reading time
7 min read
Layered document permission boundaries between a viewer, server, and container.

ONLYOFFICE Docs vulnerabilities disclosed by Rapid7 show how view-only document access crossed several trust boundaries in its tested Document Server build. Rapid7 demonstrated five distinct flaws in package 9.4.0-129, including server-file disclosure, service-level code execution, and root execution inside the official container. ONLYOFFICE confirmed on 23 October 2026 that Document Server 10.0 fixes all five findings.

The practical decision is to identify deployments, record the running package version, and update to a supported 10.0 release or later. Rapid7 demonstrated exploitation on 9.4.0-129 only; it did not establish the complete affected-version range. A version inventory is therefore more useful than assuming every earlier release is identical.

ONLYOFFICE Docs Vulnerabilities: What Boundary Failed?

ONLYOFFICE Docs can be embedded in an application that decides which document a person may open and what that person may do. The application supplies a signed opening configuration, while Document Server issues a separate session token for later operations. Rapid7 found that these tokens and downstream operations did not always preserve the original view-only boundary.

In the tested build, the same effective signing key validated browser and incoming service requests. Rapid7 showed that a token intended for opening a document could authorize a document-building request. That request could then read server files, including a readable session-signing key in the tested configuration.

A viewer who obtained that key could forge a session credential with permissions the application had never granted. Two alternative file-write paths could then lead to code execution as the Document Server service account, called ds. A separate maintenance-helper flaw allowed code already running as ds to become root inside the official container.

Rapid7's demonstrated view-only chain
Rapid7's demonstrated view-only chainAttack path in 5 steps: 1, View-only document access (Viewer), then Opening token issued; 2, Token accepted for builder work (Document Server), then Purpose boundary fails; 3, File access or write (Document Server), then Alternate routes enable progression; 4, Service code execution (Container), then ds account; 5, Maintenance helper (Container).ViewerDocument ServerContainerOpening token issuedPurpose boundary failsAlternate routes enable…ds accountView-only documentaccessToken accepted forbuilder workFile access or writeService codeexecutionMaintenance helper
  1. View-only document accessViewerOpening token issued
  2. Token accepted for builder workDocument ServerPurpose boundary fails
  3. File access or writeDocument ServerAlternate routes enable progression
  4. Service code executionContainerds account
  5. Maintenance helperContainer

This path summarizes Rapid7’s demonstration, not an outcome for every installation. It combines stages that have different prerequisites, and the two write routes are alternatives. The root result refers to the official container; the report does not show a breakout to the host.

What Does Each of the Five CVEs Change?

The five records should not be treated as one interchangeable remote-code-execution bug. Some expose information, some change files, and one requires local code execution before it can raise privileges. The table reflects Rapid7’s reported impact and score version for each finding.

CVE Boundary and effect Rapid7 score
CVE-2026-113627 View-only editor token can authorize native server-file reads. A readable session key enabled token forgery in the tested build. CVSS 3.1: 7.1 High
CVE-2026-110385 Accepted document-building work can change conversion parameters and execute code as ds when a suitable writable destination exists. CVSS 4.0: 8.7 High
CVE-2026-97727 A valid document session can write outside its storage path on filesystem-backed installations, where ds can write the destination. CVSS 3.1: 6.5 Medium
CVE-2026-113630 Code already running as ds can abuse a maintenance helper to execute as root inside the container. CVSS 3.1: 7.8 High
CVE-2026-113631 An authorized viewer can obtain a reconstructed DOCX containing data not shown in the viewer, when callback and document conditions permit. CVSS 3.1: 6.5 Medium

CVE-2026-113627 is the key authorization failure in Rapid7’s demonstrated chains. The file read alone exposes anything readable by ds; token forgery additionally depends on access to the session-signing key. Use vulnerability intelligence platform to connect this dependency to your inventory and patch priority.

CVE-2026-110385 and CVE-2026-97727 offer different routes to a writable service context. The former needs an accepted builder request and a suitable writable location. The latter needs a valid session credential, filesystem storage, and a destination writable by ds. CVE-2026-113630 then changes the privilege level of code already executing as ds.

CVE-2026-113631 is a separate disclosure path, not a required step to reach root. Rapid7 says a viewer denied download could receive a reconstructed document containing custom XML, properties, and field instructions absent from the visible view. The finding requires an authorized DOCX viewer, a reachable replacement callback, and non-rendered content to reveal extra data.

When Can View-Only Access Become Unauthenticated Access?

Rapid7 also described a conditional WOPI route into document-building work. This route requires WOPI to be enabled and an attacker-controlled source to be reachable and permitted by the configured IP filter. Only under those conditions did the researchers demonstrate entry without a pre-existing document token.

That caveat changes triage. A deployment with WOPI enabled deserves a configuration review alongside the version check. Teams should identify allowed source ranges and confirm whether the relevant service can reach untrusted sources. The described route should not be generalized to every ONLYOFFICE installation.

The two root chains used alternative write stages, while both relied on the maintenance-helper weakness for the final privilege step. Rapid7’s proof of concept was published with the research, but a working demonstration is not a count of real-world incidents. It establishes that the tested chain can work under the stated conditions.

What Should Defenders Check and Patch First?

Start with an inventory of Document Server deployments, including containers and integrations that expose document viewing. Record the product and package version actually running, rather than the image tag alone. Rapid7 tested package 9.4.0-129 and performed targeted checks on 10.0.0-169.

Prioritize an update to a supported Document Server 10.0 release or later, following the vendor’s release notes and your deployment procedure. After updating, verify the running package version and repeat a normal view-only workflow. Check that editing, printing, downloading, and forms still behave according to the integrating application’s permissions.

ONLYOFFICE response sequence
  • InventoryIdentify Document Server instances and integrations that issue view-only access
  • Verify buildRecord the running package version and deployment method
  • PatchInstall a supported 10.0 release or later and verify the running version
  • Review scopeCheck WOPI enablement, source restrictions, and service-file permissions
  • InvestigateCorrelate unusual builder activity, session changes, and service-account actions

For a system that cannot be updated immediately, limit access to the document service and review WOPI reachability. Restrict what ds can read and write where operationally possible, and preserve relevant application and container logs. These are Brandefense defensive recommendations, not substitute fixes claimed by the vendor.

For an investigation, look for a sequence rather than one isolated event. Review unexpected document-building jobs, changes to runtime configuration, unusual save operations, and root-helper activity from the service account. Rapid7’s paths make these useful hypotheses, but routine administration can create some of the same events.

The vulnerability alert triage guide gives a general workflow for ownership and verification. The CVSS explanation helps interpret why the five reported scores differ. Apply the specific vendor fix before relying on any scoring or monitoring workflow.

How Much Does Public Discussion Change the Risk?

Brandefense Blackhole counted 32 dark-chat posts matching “ONLYOFFICE” between 18 August and 16 November 2026. The measured unit is matching posts in this product-term search, not unique actors, affected organizations, or confirmed exploitation. The count may include discussion unrelated to these five CVEs.

The count is useful for watching attention to the product, but it does not change the patch decision. Rapid7’s reproduced findings and the vendor’s 10.0 security changes provide stronger evidence for action. Do not add this count to other source totals, since their underlying conversations may overlap.

Rapid7 reported the findings on 28 August, and ONLYOFFICE confirmed fixes on 23 October. The public technical analysis appeared on 16 November 2026. That gap gave administrators time to update before details were public, while deployments still running the tested build now warrant prompt review.

The right conclusion is narrow: five distinct weaknesses allowed serious outcomes in Rapid7’s tested configuration, and version 10.0 addresses them. Confirm the version and exposure of each deployment, then investigate any credible signs of progression. Keep the broader affected range and real-world incident count marked as unresolved.

Frequently Asked Questions

Does every ONLYOFFICE Docs installation allow the root chain?

Rapid7 demonstrated the chain on package 9.4.0-129 under its documented conditions. The report does not establish the complete affected-version range or identical exposure across installations.

Is view-only access enough for all five findings?

The findings have different prerequisites. Rapid7 showed a chain from view-only access, while the file-write and privilege-escalation stages require additional conditions.

What version fixes the five vulnerabilities?

ONLYOFFICE confirmed that Document Server 10.0 fixes all five. Rapid7 performed targeted checks on package 10.0.0-169.

Did Rapid7 show a host-container breakout?

Rapid7 demonstrated root execution inside the official Document Server container. Its report does not claim a breakout to the container host.

Sources

  1. Rapid7, From view-only access to container root: five vulnerabilities in ONLYOFFICE Docs (16 November 2026)
  2. ONLYOFFICE, DocumentServer 10.0.0 changelog, Security
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →