Outline before 1.12.0 Incorrect Authorization via authorizeDocumentPublish() Detached Draft
Affects Outline versions before 1.12.0 when a detached draft keeps its parent document, letting an authenticated workspace member publish into private collections. Fixed in 1.12.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.12.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected: Outline versions before 1.12.0 The document being published is a detached draft that still retains a parentDocumentId (created via documents.unpublish with detach: true) Attacker must be an authenticated workspace member who knows the destination private collection UUID
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.12.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Outline before 1.12.0 contains an incorrect authorization vulnerability in authorizeDocumentPublish() that allows authenticated members to publish documents into private collections without write access. Attackers can detach a child document via documents.unpublish, retaining parentDocumentId, then call documents.update with a private collection UUID to inject phishing content.
What to do
Check whether your setup matches what the bug needs.
Affected: Outline versions before 1.12.0 The document being published is a detached draft that still retains a parentDocumentId (created via documents.unpublish with detach: true) Attacker must be an authenticated workspace member who knows the destination private collection UUIDUpgrade to a fixed version: 1.12.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Outline Outline
fixed in 1.12.0
Evidence 5
- Advisory
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120489
What does this mean?
An authenticated workspace member can publish arbitrary documents into private collections they cannot access, which is an integrity problem with no confidentiality impact observed. It occurs when a detached draft still retains a parentDocumentId.Source: github.com
Am I affected, and how do I check?
Outline versions before 1.12.0 are affected, and the issue occurs when a detached draft retains a parentDocumentId, created via documents.unpublish with detach: true. The attacker must be an authenticated workspace member who knows the destination private collection UUID.Source: github.com
What should I do about it?
Upgrade Outline to version 1.12.0 or later, which contains the fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data