CVE-2026-47777: Mastodon has a consent-check bypass in its remote Collections
Mastodon is a free, open-source social network server based on ActivityPub. In versions there is a missing condition in the check if remote accounts consented to be featured in a remote Collection could lead to attackers bypassing the check and faking consent. An attacker could forge the FeatureAuthorization object that is used to verify consent to be featured in a Collection and thus make it appear as if an account is allowed to be in a Collection when it actually is not. While the FeatureAuthorization must reside on the same domain as the object it is for, a check is missing to make sure said object is actually the same as in the Collection item. This allows an attacker to forge the authorization. Mastodon servers are affected only if running the main branch or nightly builds who have opted into testing the experimental "Collections" feature by setting the environment variable EXPERIMENTALFEATURES to a value including collections. This has been patched in version 4.6.0-beta.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Mastodonto a version that resolves this vulnerability.Fixed in 4.6.0-beta.1 - Configuration
Remove 'collections' from the EXPERIMENTAL_FEATURES environment variable or unset EXPERIMENTAL_FEATURES to disable the experimental Collections feature unless you explicitly require it for testing.
Mastodon EXPERIMENTAL_FEATURES = does not include 'collections' or unset
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47777?
The severity of CVE-2026-47777 is high, with a score of 7.5.
What is the risk associated with CVE-2026-47777?
CVE-2026-47777 has a risk rating of 43.
How do I fix CVE-2026-47777?
To fix CVE-2026-47777, update to the latest version of Mastodon that addresses the consent-check bypass issue.
What impact does CVE-2026-47777 have on Mastodon users?
CVE-2026-47777 allows attackers to bypass consent checks, potentially leading to unauthorized feature inclusion.
Is there a workaround for CVE-2026-47777?
Currently, the recommended action is to update to a patched version of Mastodon, as there is no effective workaround available.