# CVE-2026-41649: Outline has IDOR in document share creation that allows unauthorized access to private documents across workspaces

> Authenticated attackers can generate public share links for private documents in other workspaces due to flawed authorization checks, exposing sensitive data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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:** 28 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-23jj-rp48-w7q7

## What is CVE-2026-41649?

CVE-2026-41649 is a high-severity missing authorization vulnerability in outline, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Outline is a service that allows for collaborative documentation. The `shares.create` API endpoint starting in version 0.86.0 and prior to version 1.7.0 has an insecure direct object reference.. When both `collectionId` and `documentId` are provided in the request, the authorization logic only checks access to the collection, completely ignoring the document. This allows an authenticated attacker to generate a valid public share link for any document on the platform, including documents belonging to other workspaces. The full document contents can then be retrieved via the `documents.info` endpoint. Version 1.7.0 contains a patch.

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

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

It affects 1 product.


Products: Getoutline Outline.

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

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

## Is CVE-2026-41649 being exploited?

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

## Other vulnerabilities in outline

- [CVE-2026-33640](https://insights.sbomify.com/CVE-2026-33640/): Outline has a rate limit bypass that allows brute force of email login OTP (critical 9.1)
- [CVE-2024-37829](https://insights.sbomify.com/CVE-2024-37829/): Auth bypass in n/a (high 8.8)
- [CVE-2023-54331](https://insights.sbomify.com/CVE-2023-54331/): Outline 1.6.0 - Unquoted Service Path (high 8.5)
- [CVE-2023-3532](https://insights.sbomify.com/CVE-2023-3532/): Cross-site Scripting (XSS) - Stored in outline/outline (high 8.5)
- [CVE-2026-24901](https://insights.sbomify.com/CVE-2026-24901/): Outline's IDOR allows unauthorized viewing and seizing of private deleted drafts (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41649 is a high-severity missing authorization vulnerability in outline, published on 28 Apr 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-41649 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-41649/ (Markdown: https://insights.sbomify.com/CVE-2026-41649/index.md)
```

## Sources

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

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