# CVE-2026-48073: Docmost: Page export can include restricted same-space attachments through forged attachmentId

> Low-privileged users can read restricted attachments from other pages by forging attachment IDs during page export, bypassing direct download access controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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-rxm9-xp9h-4c84

## What is CVE-2026-48073?

CVE-2026-48073 is a medium-severity missing authorization 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.70.0 until 0.80.1, a low-privileged authenticated user who can edit an exportable page can embed a forged attachmentId that belongs to a restricted page in the same space. Exporting the attacker-controlled page with includeAttachments=true causes the page export flow to read the restricted attachment from storage and include it in the returned ZIP archive even though direct file download denies access. This issue is fixed in version 0.80.1.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-48073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48073 is a medium-severity missing authorization 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-48073 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-48073/ (Markdown: https://insights.sbomify.com/CVE-2026-48073/index.md)
```

## Sources

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

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