# CVE-2026-86111: BookWyrm through 0.9.1 Insecure Direct Object Reference in EditStatus Exposes Followers-Only and Direct Statuses

> Authenticated attackers can read private followers-only and direct statuses by enumerating IDs in the edit endpoint, bypassing privacy controls.

- **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:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-phg3-p22v-rp9q

## What is CVE-2026-86111?

CVE-2026-86111 is a high-severity missing authorization vulnerability in bookwyrm-social bookwyrm, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BookWyrm through 0.9.1 fails to validate user visibility permissions in the status edit endpoint, allowing authenticated attackers to read followers-only and direct-message reviews by enumerating sequential status IDs. Attackers can access the raw content of restricted statuses through the edit view, bypassing the privacy protections documented for these message types.

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

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


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

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

## Is CVE-2026-86111 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86111 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86111 is a high-severity missing authorization vulnerability in bookwyrm-social bookwyrm, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86111 exists.

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

## Sources

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

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