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 EXPERIMENTAL_FEATURES to a value including collections. This has been patched in version 4.6.0-beta.1.
CVE-2026-47777
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 6.3%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 16, 2026
Advisory Details (2)
Auto-updated Jun 15, 2026commit 22203f8aeb03 (mastodon/mastodon)
Patch available: mastodon/mastodon v4.6.0-beta.1 (contains commit 22203f8aeb03)
https://github.com/mastodon/mastodon/commit/22203f8aeb03e8f14dc62e253e83db39825a5bcfConsent-check bypass in remote Collections · Advisory · mastodon/mastodon · GitHub
https://github.com/mastodon/mastodon/security/advisories/GHSA-vg36-gxjg-2v46Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2026-47777?
When was CVE-2026-47777 disclosed?
Is CVE-2026-47777 actively exploited?
What is the CVSS score of CVE-2026-47777?
How do I remediate CVE-2026-47777?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47777
Is Your Infrastructure Affected by CVE-2026-47777?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.