Read the docs

Mastodon API lets unregistered users read public timelines

Priority LOW 39Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-58x8-3qxw-6hm7. Fix status from GitHub.

Summary

Mastodon fails to check that authentication tokens belong to an actual user in several API controllers, and it does not verify token scopes for the public timeline controller. Unregistered users can read the public timeline on servers that allow unauthenticated access to public timelines, even though that setting should block it for hashtag timelines. Any application token can also see whether the current user interacted with public timeline posts, regardless of its permissions. Servers that set DISALLOW_UNAUTHENTICATED_API_ACCESS=true are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Summary Various API controllers that were conditionally checking existence of an authentication token were failing to check they were owned by an actual user, allowing access to certain resources through application tokens. In addition, authentication token scopes were never verified for the public timeline controller, and scopes of other endpoints were only checked when the “Allow unauthenticated access to public timelines” setting was disabled. ### Impact This vulnerability effectively prevents the “Allow unauthenticated access to public timelines” setting from being correctly enforced for hashtag timelines (and, on development versions, on link timelines), allowing unregistered users to access the server's public timeline. Servers using `DISALLOW_UNAUTHENTICATED_API_ACCESS=true` are not affected. In addition, any application was able to access the public timeline and see whether the current user had interacted with them, regardless of the application's permissions.

Why it matters now

Fix Fixed mastodon: 4.2.10, 4.1.18

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—mastodon—4.2.10, 4.1.18Patch availableGHSA-58x8-3qxw-6hm7
  • mastodon Vendor— Affected — Fixed in 4.2.10, 4.1.18 Patch available GHSA-58x8-3qxw-6hm7

Remediation

Upgrade mastodon to version 4.2.10 or 4.1.18.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-58x8-3qxw-6hm7 mastodon Fixed in 4.2.10, 4.1.18 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-58x8-3qxw-6hm7

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences