Mastodon streaming API sends user events after access token revocation
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-vp5r-5pgw-jwqx. Fix status from GitHub. Impact type from CWE-613.
Summary
Mastodon does not close open streaming API connections when a user revokes an application's access token. An application that holds a connection opened before the revocation keeps receiving the user's private events, such as mentions and notifications, and can still subscribe to streamable timelines. An attacker needs to be an authorized application that keeps a streaming connection open. The flaw is classified as CWE-613, insufficient session expiration.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary After a user revokes an application’s access token, the application can still receive the user’s private mentions, notifications, etc via existing connection(s) to the streaming API. ### Details Revoking an application’s access token does not cause open WebSocket streaming connections using that access token to be closed. Mastodon continues to send all events listed [in the documentation](https://docs.joinmastodon.org/methods/streaming/#events) indefinitely over any connections that were opened prior to the revocation. It also continues to allow the application to subscribe to any streamable timeline listed [here](https://docs.joinmastodon.org/methods/streaming/#streams) even after the user revokes access. ### Impact If a user authorizes an application, the application can continue to watch that user’s timelines and notifications even if the user withdraws their consent. A malicious server-based application could potentially maintain a streaming connection from their server indefinitely, leaving the user with no way to stop the sharing or even know that it is still going on after the Mastodon web UI no longer shows the application in the list of authorized applications. The potentially sensitive information that can be exposed is limited to what is defined in the [Streaming API](https://docs.joinmastodon.org/methods/streaming), but includes all posts visible to the user including followers-only posts, direct messages, conversations, notifications, as well as the contents of the user’s lists. The `status` objects received via streaming may also contain information about whether the user has taken private actions such as favoriting or bookmarking posts, muting other users, the user's votes in polls, and/or their configured filters. If the affected user is an administrator, the leaked information could also include the contents of reports and sign-ups they receive [Notifications](https://docs.joinmastodon.org/entities/Notification/) about.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | mastodon | — | 4.2.10, 4.1.18 | Patch available | GHSA-vp5r-5pgw-jwqx |
- mastodon Vendor— Affected — Fixed in 4.2.10, 4.1.18 Patch available GHSA-vp5r-5pgw-jwqx
Remediation
Upgrade mastodon to version 4.2.10 or 4.1.18 or later, the fixed versions for the affected product.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-vp5r-5pgw-jwqx mastodon Fixed in 4.2.10, 4.1.18 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-vp5r-5pgw-jwqx
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences