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

> Attackers can bypass consent checks to forge authorization for featuring accounts in remote Collections on Mastodon servers with experimental features enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** BIT-mastodon-2026-47777, GHSA-vg36-gxjg-2v46

## What is CVE-2026-47777?

CVE-2026-47777 is a high-severity vulnerability in mastodon, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-47777?

1 open source package ship an affected version, including mastodon.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | From nightly.2026-03-10.0 | 4.6.0 |

## How do I fix CVE-2026-47777?

Upgrade mastodon to 4.6.0 or later.

## Is CVE-2026-47777 being exploited?

There is no known exploitation of CVE-2026-47777 in the wild and no public exploit code.

Public exploit code:

- https://github.com/bekwiner/cve-2026-47777 (github_poc): https://github.com/bekwiner/cve-2026-47777

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47777 and fix it if it is affected.

What it is: CVE-2026-47777 is a high-severity vulnerability in mastodon, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47777 in the wild and no public exploit code.

Affected packages and fixed versions:
- mastodon (Bitnami): affected from nightly.2026-03-10.0; fixed in 4.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47777/ (Markdown: https://insights.sbomify.com/CVE-2026-47777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47777
- OSV: https://osv.dev/vulnerability/CVE-2026-47777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47777/
Summaries are generated and may contain mistakes; the official description above is the record.