# CVE-2026-117563: MrDoc through 1.1.1 Broken Access Control via manage_doc_share


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-rf24-chhw-3jch

## What is CVE-2026-117563?

CVE-2026-117563 is a medium-severity vulnerability in zmister2016 MrDoc, published on 27 Oct 2026. 

### Official description

MrDoc through 1.1.1 contains a broken access control vulnerability in the manage_doc_share type 3 branch that allows authenticated users to modify other users' document share settings because updates lack an ownership check. Attackers can compute predictable share tokens from the MD5 of document ID and username to re-enable disabled shares or remove access codes, exposing private documents.

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

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


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

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

## Is CVE-2026-117563 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117563 is a medium-severity vulnerability in zmister2016 MrDoc, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117563 in the wild and no public exploit code.

Affected product: zmister2016 MrDoc. 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-117563/ (Markdown: https://insights.sbomify.com/CVE-2026-117563/index.md)
```

## Sources

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

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