CVE-2026-24901
Received Received - Intake
IDOR Vulnerability in Outline Allows Unauthorized Draft Restoration

Publication date: 2026-03-17

Last updated on: 2026-03-19

Assigner: GitHub, Inc.

Description
Outline is a service that allows for collaborative documentation. Prior to 1.4.0, an Insecure Direct Object Reference (IDOR) vulnerability in the document restoration logic allows any team member to unauthorizedly restore, view, and seize ownership of deleted drafts belonging to other users, including administrators. By bypassing ownership validation during the restore process, an attacker can access sensitive private information and effectively lock the original owner out of their own content. Version 1.4.0 fixes the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-17
Last Modified
2026-03-19
Generated
2026-05-07
AI Q&A
2026-03-17
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
getoutline outline to 1.4.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-24901 is an Insecure Direct Object Reference (IDOR) vulnerability in Outline versions prior to 1.4.0, specifically in the document restoration logic.

This flaw allows any team member, even with low privileges, to unauthorizedly restore, view, and take ownership of deleted private drafts belonging to other users, including administrators.

The vulnerability occurs because the system does not properly verify if the user restoring a deleted draft is the original owner or has explicit permission, allowing attackers to bypass ownership validation.

  • An attacker who knows the UUID of a deleted draft can access its content and restore it under their own ownership.
  • The attacker can then publish the draft and lock the original owner out of their own content.

How can this vulnerability impact me? :

This vulnerability can have several serious impacts:

  • Unauthorized disclosure of sensitive private draft content to unauthorized team members.
  • Theft of ownership of deleted drafts, allowing attackers to control and publish content they do not own.
  • Denial of service for the original owner, who loses access to their own deleted drafts permanently.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring API requests to the `/api/documents.restore` endpoint, especially POST requests that attempt to restore deleted drafts. Suspicious activity includes restoration requests where the requester is not the original owner of the draft.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts, you can look for POST requests with parameters specifying draft IDs (UUIDs) and collection IDs that do not belong to the requester.'}, {'type': 'paragraph', 'content': 'Suggested commands to help detect this on a system running Outline might include:'}, {'type': 'list_item', 'content': 'Use network traffic monitoring tools (e.g., tcpdump, Wireshark) to filter HTTP POST requests to `/api/documents.restore`.'}, {'type': 'list_item', 'content': "Example tcpdump command: `tcpdump -A -s 0 'tcp port 80 or tcp port 443' | grep '/api/documents.restore'`"}, {'type': 'list_item', 'content': 'Check application logs for restoration events and verify if the user restoring the draft is the original owner.'}, {'type': 'list_item', 'content': 'Use API request logging or auditing features to track which user IDs are performing restore operations and on which draft UUIDs.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade Outline to version 1.4.0 or later, where this vulnerability is fixed.

Until the upgrade can be performed, restrict team membership to trusted users only, as the vulnerability requires team membership to exploit.

Additionally, monitor and audit restore operations to detect unauthorized restoration attempts.

If possible, temporarily disable or restrict access to the `/api/documents.restore` endpoint to prevent unauthorized restores.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart