Quick answers
- Is CVE-2026-47777 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47777 being exploited in the wild.
- How severe is CVE-2026-47777?
- High severity, with a CVSS score of 7.5, published 15 June 2026.
- Which products and versions are affected?
- Mastodon nightly builds between 2026-03-10 and 2026-05-21; main branch prior to commit 22203f8.
- Is there a fix for CVE-2026-47777?
- A patch was published on 2026-05-21: Fixed in nightly builds and main branch commit 22203f8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47777 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-47777?
- Check whether you run Mastodon at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authorization bypass exists in Mastodon's experimental 'Collections' feature due to insufficient verification of the FeatureAuthorization object. While the system checks that the authorization originates from the correct domain, it fails to verify that the object referenced in the authorization matches the item being added to the Collection. A remote, unauthenticated attacker can exploit this missing condition to forge consent, making it appear as if a remote account has agreed to be featured. This vulnerability only affects servers running nightly or main branch builds with the EXPERIMENTAL_FEATURES environment variable set to include 'collections'. The issue is addressed in version 4.6.0-beta.1 and nightly builds starting from 2026-05-21.
Affected products
- Mastodon Mastodon nightly builds between 2026-03-10 and 2026-05-21; main branch prior to commit 22203f8
Timeline
- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-05-21: patched: Fixed in nightly builds and main branch commit 22203f8
- 2026-06-15: disclosed: CVE-2026-47777 published to NVD