# CVE-2026-111364: MinDoc through 2.2-beta.2 IDOR via /api/:key/content/:id GET Branch

> Authenticated users can read private documents from unauthorized books by iterating sequential IDs, exposing sensitive content.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-c99c-gh3j-2mp4

## What is CVE-2026-111364?

CVE-2026-111364 is a high-severity missing authorization vulnerability in mindoc-org MinDoc, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MinDoc through 2.2-beta.2 contains an insecure direct object reference vulnerability in DocumentController.Content that allows authenticated users to read documents from unauthorized books. Attackers holding a non-observer role on any book can name that book and iterate sequential document ids to read markdown and HTML from private books.

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

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


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

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

## Is CVE-2026-111364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111364 is a high-severity missing authorization vulnerability in mindoc-org MinDoc, published on 15 Oct 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-111364 in the wild and no public exploit code.

Affected product: mindoc-org MinDoc. 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-111364/ (Markdown: https://insights.sbomify.com/CVE-2026-111364/index.md)
```

## Sources

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

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