CVE-2026-47777: Mastodon has a consent-check bypass in its remote Collections

Published Jun 15, 2026
·
Updated

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

1 affected component
Mastodon Mastodon<4.6.0-beta.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Mastodon to a version that resolves this vulnerability.

    Fixed in 4.6.0-beta.1
  2. 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

Jun 15, 2026
CVE Published
via MITRE·04:54 PM
Data Sourced
via MITRE·04:54 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47777?

The severity of CVE-2026-47777 is high, with a score of 7.5.

2

What is the risk associated with CVE-2026-47777?

CVE-2026-47777 has a risk rating of 43.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203