# CVE-2026-113611: Outline before 1.8.0 Information Disclosure via Orphaned Webhook Subscriptions


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-33jq-x32c-3ccw, GHSA-5w2f-v435-9jjc

## What is CVE-2026-113611?

CVE-2026-113611 is a medium-severity vulnerability in outline, published on 20 Oct 2026. 

### Official description

Outline before 1.8.0 contains an improper access revocation vulnerability that allows deleted administrators to keep receiving document contents because UserDeletedProcessor never disables their WebhookSubscription rows. Former admins who registered webhooks before deletion continue receiving full document bodies, including Markdown and Yjs data, via DeliverWebhookTask for every matching workspace event.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-113611 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113611 is a medium-severity vulnerability in outline, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113611 exists.

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

## Sources

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

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