vulns.co
/
GKData.io MCP and API Buy me a coffee

Outline

Outline: integration authority must end with its owning account

Outline's maintainer-published report demonstrates document content still being delivered by a webhook after its administrator creator's account was deleted (GHSA-33jq-x32c-3ccw). Account cleanup left the subscription in place, and delivery relied on its enabled status. The demonstration was local.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial lesson: revocation must cover durable integrations and every terminal account state, with delivery-time checks as defense in depth. The advisory identifies 1.8.0 as patched. Its proposed cleanup changes are recommendations, not evidence of the implemented patch.

Before reading

  • Basic server-side authorization concepts

Context and limits

  • Requires a webhook previously configured by an administrator, followed by account deletion and a matching document event. The demonstrated deployment used 0.86.0; the maintainer lists versions through 1.7.1 as affected.
  • Continued delivery was demonstrated locally; no production incident, measured duration or customer exposure is established. Persistent exposure is the report’s inference from absent expiry and revalidation.
  • Published June 6, 2026 by tommoor, with dizconnectz credited as reporter. Publication does not establish the release date of 1.8.0. Learning prerequisites are editorial.

Sources

  1. Webhook subscription persists after creator's account deletionOutline · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software