Search results in Mastodon can link to the wrong account profile
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-3m9q-ww7w-qc5j. Fix status from GitHub.
Summary
Mastodon, the open-source social network server, has a flaw in its web interface where clicking a username in search results could open a different profile. The search result can link to another account when two usernames are identical and one server name starts with the other, depending on the order in which account data loads. An unauthenticated remote attacker can use crafted fake accounts to impersonate other accounts if a user clicks the corrupted result. The issue only affected nightly and beta 1 builds of Mastodon 4.3 and was never in a stable release.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Summary In the web interface, clicking on the result returned by a search for a username could have lead to a different profile instead. ### Details Clicking on a username in search results could have lead to a different profile, if all of the following conditions were met: * The usernames were identical * The server name of one user started with the server name of the other user and * Account data was loaded in a certain order. Example: Given a user `@[email protected]` and a user `@[email protected]`, _if_ the app loaded and cached the latter user's data first and someone searched for "user" then both users would have been displayed correctly, but both would have linked to the profile of `@[email protected]`. ### Impact Carefully crafted fake accounts could have impersonated other accounts if a user clicked on corrupted search results. The impact is limited by the fact that this was never in a stable release. But we urge everyone who has installed nightly builds or beta 1 of Mastodon 4.3. to update to beta 2.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | mastodon | v4.3.0-beta.1 | v4.3.0-beta.2 | Patch available | GHSA-3m9q-ww7w-qc5j |
- mastodon Vendor— Affected v4.3.0-beta.1 Fixed in v4.3.0-beta.2 Patch available GHSA-3m9q-ww7w-qc5j
Remediation
Mastodon v4.3.0-beta.2 fixes this issue, so users of nightly builds or Mastodon 4.3.0-beta.1 should update to v4.3.0-beta.2.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-3m9q-ww7w-qc5j mastodon Fixed in v4.3.0-beta.2 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-3m9q-ww7w-qc5j
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences