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

ONLYOFFICE Docs Complete-Save Path Traversal (CVE-2026-97727)

CVE-2026-97727 is a path traversal flaw in ONLYOFFICE Document Server's complete-save operation.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-97727
Vendor
ONLYOFFICE
Affected Product
ONLYOFFICE Docs (Document Server)
Exploitation
Not confirmed
Published
2026-11-16

Rapid7 demonstrated that a valid save session could write outside the intended document storage directory.Rapid7 assigns the file-write flaw a CVSS 3.1 score of 6.5, Medium. The demonstrated effect is a file created or overwritten with the document service account's permissions, not root execution by this flaw alone.

What it allows

How Does CVE-2026-97727 Escape Document Storage?

Rapid7 traced the flaw to the complete-save path. The server appended a user-supplied format value to a filename, while this save mode skipped the filename normalization used for other save types.

On the tested filesystem backend, the storage layer then wrote the resulting path without enforcing the document-root boundary. A valid Session JWT and a destination writable by the service account were required; no victim interaction was needed.

This is a separate file-write flaw. Rapid7 first used CVE-2026-113627 to obtain a forged save credential from view-only document access, then used CVE-2026-97727 to place files writable by the service account.

Rapid7's demonstrated chain later used another flaw, CVE-2026-113630, to run a command as root inside the official container. The CVE-2026-97727 primitive itself provides file write under the service account's permissions. For prioritization context, see Vulnerability Intelligence.

What Is Known About Exploitation?

Rapid7 published proof-of-concept code with its November 16, 2026 research and demonstrated the chain in a controlled test. That research establishes a working file-write path in the tested build, not an observed attack campaign.

The CVE was absent from CISA's KEV catalog version 2026.11.13, checked on November 16. Brandefense treats real-world exploitation status as unknown and recommends prioritizing exposed self-managed installations.

Who is affected

Which ONLYOFFICE Docs Installations Need Review?

Rapid7 demonstrated CVE-2026-97727 on the official DocumentServer 9.4.0 image with package 9.4.0-129 and filesystem storage. The researcher says the broader affected-version range is unknown, so do not infer that every earlier release is vulnerable.

The file-write stage needs a valid document Session JWT and a path writable by the Document Server service account. View-only access alone reached this stage in Rapid7's chain only after a separate token-forgery flaw supplied that credential.

Rapid7 tested package 10.0.0-169 and found that the traversal attempt was rejected. It attributes the fix to a storage-layer check that keeps the normalized object key inside the storage root; the vendor's 10.0 release notes also list security fixes.

Inventory self-managed deployments, record their installed package or container image version, and confirm the storage backend. The Vulnerability Management 101 guide gives a general patch-prioritization workflow. The vulnerability intelligence glossary defines the broader prioritization discipline.

Timeline

  1. 2026-08-28

    Rapid7 says it reported five ONLYOFFICE findings to the vendor.

  2. 2026-10-23

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

  3. 2026-11-16

    Rapid7 published its analysis and accompanying proof-of-concept code.

What to do

  1. Inventory and scope exposure

    Identify self-managed ONLYOFFICE Document Server instances, their installed versions, storage backends, and who can open documents. Prioritize installations matching Rapid7's tested conditions.

  2. Upgrade Document Server

    Move affected or potentially exposed self-managed installations to ONLYOFFICE Document Server 10.0 or a later supported release. Follow the vendor's update instructions for the actual deployment method.

  3. Check files and save activity

    Compare service-writable configuration and runtime files with trusted deployment baselines. Review unusual save activity and investigate anomalies as leads, not proof of this CVE.

  4. Verify the running release

    After maintenance, confirm that the running package or container image reports Document Server 10.0 or later. Recheck the vendor release notes and the deployment's change record.

What Brandefense can do

Frequently Asked Questions

What access does CVE-2026-97727 require?

Rapid7 says the file-write step needs a valid document Session JWT, filesystem storage, and a destination writable by the service account.

Does CVE-2026-97727 alone grant root access?

No. It writes files with the service account's permissions. Rapid7's root demonstration added separate token-forgery and privilege-escalation flaws.

Which release fixes the tested path traversal?

Rapid7 says ONLYOFFICE confirmed a fix in Document Server 10.0. Its targeted test on package 10.0.0-169 rejected the traversal attempt.

Are all releases before 10.0 affected?

Rapid7 demonstrated exploitation on 9.4.0-129 but says the broader affected-version range is unknown. Check the installed release against vendor guidance.

Sources

  1. From view-only access to container root: five vulnerabilities in ONLYOFFICE Docs (FIXED)Rapid7
  2. DocumentServer 10.0.0 change log, SecurityONLYOFFICE
  3. 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 →