Read the docs

Mastodon lets attackers sign in to 2FA accounts without a password

Priority MEDIUM 48Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-vx32-x96w-qq65. Fix status from GitHub.

Summary

Mastodon versions before 4.4.24, from 4.5.0-alpha.1 before 4.5.17, from 4.6.0-alpha.1 before 4.6.7, from 4.7.0-alpha.1 before 4.7.1, and 4.8.0-alpha.1 are affected. An incorrect check in the authentication flow lets a user advance to the second factor without a valid password when the account has no database-stored password. An attacker who holds a victim's security key, backup code or TOTP token can sign in to two-factor accounts that authenticate through LDAP, PAM or a server-configured SSO.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

## Summary An incorrect check in Mastodon's authentication flow allows moving on to the second authentication factor (TOTP, security key, backup code) without providing a valid password when the user has no database-stored password (when the account is normally authenticated using LDAP, PAM or OmniAuth). ## Impact This vulnerability allows attackers to log into accounts without requiring their password or going through the SSO flow, provided that: - the victim has enabled 2FA and the attacker has a valid security key, backup code or TOTP token - the victim has no database-stored password: the server is configured to use LDAP or PAM, or the user logs in exclusively using a server-configured SSO ## Patches Mastodon versions v4.6.7, v4.5.17, and v4.4.24 are patched.

Why it matters now

Fix Fixed mastodon: 4.4.24, 4.5.17, 4.6.7 +2

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—mastodon< 4.4.244.4.24Patch availableGHSA-vx32-x96w-qq65
—mastodon>= 4.5.0-alpha.1, < 4.5.174.5.17Patch availableGHSA-vx32-x96w-qq65
—mastodon>= 4.6.0-alpha.1, < 4.6.74.6.7Patch availableGHSA-vx32-x96w-qq65
—mastodon>= 4.7.0-alpha.1, < 4.7.14.7.1Patch availableGHSA-vx32-x96w-qq65
—mastodon4.8.0-alpha.14.8.0-alpha.2Patch availableGHSA-vx32-x96w-qq65
  • mastodon Vendor— Affected < 4.4.24 Fixed in 4.4.24 Patch available GHSA-vx32-x96w-qq65
  • mastodon Vendor— Affected >= 4.5.0-alpha.1, < 4.5.17 Fixed in 4.5.17 Patch available GHSA-vx32-x96w-qq65
  • mastodon Vendor— Affected >= 4.6.0-alpha.1, < 4.6.7 Fixed in 4.6.7 Patch available GHSA-vx32-x96w-qq65
  • mastodon Vendor— Affected >= 4.7.0-alpha.1, < 4.7.1 Fixed in 4.7.1 Patch available GHSA-vx32-x96w-qq65
  • mastodon Vendor— Affected 4.8.0-alpha.1 Fixed in 4.8.0-alpha.2 Patch available GHSA-vx32-x96w-qq65

Remediation

Mastodon versions 4.4.24, 4.5.17, 4.6.7, 4.7.1 and 4.8.0-alpha.2 fix this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-vx32-x96w-qq65 mastodon Fixed in 4.4.24 Advisory →
  • Fix · GHSA-vx32-x96w-qq65 mastodon Fixed in 4.5.17 Advisory →
  • Fix · GHSA-vx32-x96w-qq65 mastodon Fixed in 4.6.7 Advisory →
  • Fix · GHSA-vx32-x96w-qq65 mastodon Fixed in 4.7.1 Advisory →
  • Fix · GHSA-vx32-x96w-qq65 mastodon Fixed in 4.8.0-alpha.2 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-vx32-x96w-qq65

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences