# CVE-2026-65827: Docmost: Unbounded ZIP decompression (zip-bomb) in page import allows denial of service

> Authenticated users can cause denial of service by uploading malicious ZIP files that exhaust server disk space during import.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-frjw-66gr-799m

## What is CVE-2026-65827?

CVE-2026-65827 is a medium-severity denial of service vulnerability in docmost, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Docmost is open-source collaborative wiki and documentation software. From 0.21.0 until 0.95.0, any authenticated workspace member with edit rights to a space can upload an archive to the page-import feature whose ZIP extraction routine does not limit total uncompressed size, per-entry size, or entry count. The extractor writes entries to the server temp directory and automatically extracts one nested ZIP, allowing an outer upload within the default 200 MB limit to expand by multiple GB. The resulting disk exhaustion can crash the import worker and degrade or take down the instance for all tenants. This issue is fixed in version 0.95.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification)), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-65827?


## How do I fix CVE-2026-65827?

No fix has been published for CVE-2026-65827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65827 being exploited?

There is no known exploitation of CVE-2026-65827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65827 and fix it if it is affected.

What it is: CVE-2026-65827 is a medium-severity denial of service vulnerability in docmost, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65827 in the wild and no public exploit code.

Affected product: docmost. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65827/ (Markdown: https://insights.sbomify.com/CVE-2026-65827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65827
- OSV: https://osv.dev/vulnerability/CVE-2026-65827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65827/
Summaries are generated and may contain mistakes; the official description above is the record.