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

ONLYOFFICE Docs SaveFile Code Execution (CVE-2026-110385)

CVE-2026-110385 is a code execution flaw in ONLYOFFICE Docs Document Server's Document Builder.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-110385
Vendor
ONLYOFFICE
Affected Product
ONLYOFFICE Docs Document Server
Exploitation
Not confirmed
Published
2026-10-14

The SaveFile conversion parameters can override server-selected paths and write content outside the job directory. Rapid7 demonstrated command execution as the ds service account on package 9.4.0-129.The tested direct route needed a DocBuilder request accepted with a valid token. Rapid7 reached that condition from view-only document access through a separate authorization flaw, CVE-2026-113627. Container-root execution required another separate flaw, CVE-2026-113630. ONLYOFFICE confirmed Document Server 10.0 fixed the reported findings.

What it allows

How Does CVE-2026-110385 Lead to Code Execution?

Rapid7 found that Document Builder passed the optional SaveFile conversion parameters into an XML conversion task without restricting them to supported options. Later duplicate fields replaced the paths selected by Document Server. This let the tested server write content to an existing location writable by ds.

In Rapid7's official container test, a writable configuration location let the service load attacker-controlled code without a restart. The resulting command ran as ds. A separate root-helper flaw was needed for the report's container-root result; CVE-2026-110385 alone does not establish that outcome.

What Do Rapid7 and CISA Say About CVE-2026-110385?

Rapid7 published proof-of-concept code with its 16 November 2026 disclosure. Rapid7's proof of concept tested the reported access conditions on package 9.4.0-129.

The CISA KEV catalog snapshot dated 13 November 2026 did not list this CVE. Its published CVSS 4.0 score is 8.7 High; the opened sources give no CVSS 3.1 score. Read the vulnerability prioritization glossary entry when weighing these access conditions against the installed build.

Who is affected

Which ONLYOFFICE Docs Deployments Need a CVE-2026-110385 Review?

Rapid7 demonstrated exploitation on the official Document Server 9.4.0 image with package 9.4.0-129. The direct finding requires an accepted DocBuilder request and an existing destination writable by ds. Immediate process execution also depended on a writable configuration location watched by DocService in that tested image.

The NVD description labels Document Server versions before 10.0.0 as affected, while Rapid7 says it demonstrated exploitation only on 9.4.0-129. The complete lower boundary is not established by the research. Verify the actual package or image version and integration configuration rather than inferring that every installation has the same path.

Rapid7 reached DocBuilder from view-only access through CVE-2026-113627 because the tested Browser and Inbox checks shared a signing key. An unauthenticated WOPI entry required WOPI to be enabled, an attacker-controlled source to be reachable, and the configured IP filter to permit it. Those conditions must be checked separately.

Inventory self-hosted instances and prioritize the 10.0 update in the Vulnerability Intelligence queue. Record the installed build and change window in the team's patch management process. These are defensive workflow recommendations based on the reported exposure.

Timeline

  1. 2026-08-28

    Rapid7 contacted ONLYOFFICE about five findings, including this SaveFile flaw.

  2. 2026-10-14

    The CVE record was published, according to the NVD entry.

  3. 2026-10-23

    ONLYOFFICE confirmed to Rapid7 that Document Server 10.0 fixed all five findings.

  4. 2026-11-16

    Rapid7 published its technical report and accompanying proof-of-concept code.

What to do

  1. Inventory Document Server

    Record each self-hosted ONLYOFFICE Docs package or container image version. Check access to Document Builder and whether the WOPI integration is enabled.

  2. Upgrade to Document Server 10.0 or later

    Apply the supported update for the installed distribution. ONLYOFFICE confirmed the five reported findings were fixed in 10.0, and Rapid7 checked package 10.0.0-169.

  3. Verify the running build

    After upgrading, verify the active service reports Document Server 10.0 or later. Confirm the deployed package or image matches the planned update and that normal document jobs still work.

  4. Review suspicious activity

    Review available Document Server logs for unusual Document Builder jobs and unexpected configuration changes. Preserve evidence before remediation if compromise is suspected, then assess exposed signing keys and service credentials.

What Brandefense can do

Frequently Asked Questions

Can a view-only user exploit CVE-2026-110385 directly?

Rapid7's view-only demonstration also used CVE-2026-113627 to get a DocBuilder request accepted. The SaveFile flaw itself requires an accepted request and a writable destination.

Does CVE-2026-110385 alone provide container-root access?

Rapid7 demonstrated code execution as ds for this finding. Its container-root result chained a separate root-helper flaw, CVE-2026-113630.

Which release fixes CVE-2026-110385?

ONLYOFFICE confirmed Document Server 10.0 fixed the reported findings, according to Rapid7. The researcher checked package 10.0.0-169; verify the running version after updating.

Sources

  1. From view-only access to container root: five vulnerabilities in ONLYOFFICE DocsRapid7
  2. ONLYOFFICE 10.0: A closer look at the latest 40 security fixesONLYOFFICE
  3. CVE-2026-110385 DetailNVD
  4. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
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 →