# CVE-2026-44695: Outline: Slack OAuth state can link a victim Outline account to an attacker Slack identity

> Attackers can link victim Outline accounts to attacker Slack identities via unsigned OAuth state, enabling unauthorized access to victim data.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-mjgw-5j7q-gv8v

## What is CVE-2026-44695?

CVE-2026-44695 is a medium-severity vulnerability in outline, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Outline is a service that allows for collaborative documentation. Prior to 1.7.1, the Slack integration callback for GET /auth/slack.post accepts an unsigned, session-independent OAuth state value. A third party who can obtain a Slack OAuth code for the same Outline Slack client can make a logged-in Outline user complete the callback and link that user's Outline account to the attacker's Slack team_id and user_id. The linked Slack identity can then use the Slack /outline search command as the victim Outline user. This vulnerability is fixed in 1.7.1.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Getoutline Outline.

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

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

## Is CVE-2026-44695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44695 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-44695 and fix it if it is affected.

What it is: CVE-2026-44695 is a medium-severity vulnerability in outline, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44695 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-44695/ (Markdown: https://insights.sbomify.com/CVE-2026-44695/index.md)
```

## Sources

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

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