Disabled staff accounts keep access to the Mastodon admin API
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-62j4-hvj7-px3f. 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. Incomplete permission checks let users whose login was frozen with the moderation disable action keep using the admin API. A user with moderation or admin permissions can use the admin API, including restoring their own login, after the freeze.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
## Summary Incomplete permission checks allow users with admin API access to continue using it even after they have their ability to log in temporarily disabled. ## Impact Users with moderation or admin permissions could still use the admin APIs, including the ability to restore their ability to log in, when their ability to log-in has been temporarily disabled. This is specific to the “Freeze” (or `disable`) action available in the moderation interface. Users that are demoted of their roles correctly lose access to the API, as well as those who are suspended. ## Patches Mastodon versions v4.6.7, v4.5.17, and v4.4.24 are patched.
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 | < 4.4.24 | 4.4.24 | Patch available | GHSA-62j4-hvj7-px3f |
| — | mastodon | >= 4.5.0-alpha.1, < 4.5.17 | 4.5.17 | Patch available | GHSA-62j4-hvj7-px3f |
| — | mastodon | >= 4.6.0-alpha.1, < 4.6.7 | 4.6.7 | Patch available | GHSA-62j4-hvj7-px3f |
| — | mastodon | >= 4.7.0-alpha.1, < 4.7.1 | 4.7.1 | Patch available | GHSA-62j4-hvj7-px3f |
| — | mastodon | 4.8.0-alpha.1 | 4.8.0-alpha.2 | Patch available | GHSA-62j4-hvj7-px3f |
- mastodon Vendor— Affected < 4.4.24 Fixed in 4.4.24 Patch available GHSA-62j4-hvj7-px3f
- mastodon Vendor— Affected >= 4.5.0-alpha.1, < 4.5.17 Fixed in 4.5.17 Patch available GHSA-62j4-hvj7-px3f
- mastodon Vendor— Affected >= 4.6.0-alpha.1, < 4.6.7 Fixed in 4.6.7 Patch available GHSA-62j4-hvj7-px3f
- mastodon Vendor— Affected >= 4.7.0-alpha.1, < 4.7.1 Fixed in 4.7.1 Patch available GHSA-62j4-hvj7-px3f
- mastodon Vendor— Affected 4.8.0-alpha.1 Fixed in 4.8.0-alpha.2 Patch available GHSA-62j4-hvj7-px3f
Remediation
Upgrade Mastodon to 4.4.24, 4.5.17, 4.6.7, 4.7.1, or 4.8.0-alpha.2, matching the release line in use.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-62j4-hvj7-px3f mastodon Fixed in 4.4.24 Advisory →
- Fix · GHSA-62j4-hvj7-px3f mastodon Fixed in 4.5.17 Advisory →
- Fix · GHSA-62j4-hvj7-px3f mastodon Fixed in 4.6.7 Advisory →
- Fix · GHSA-62j4-hvj7-px3f mastodon Fixed in 4.7.1 Advisory →
- Fix · GHSA-62j4-hvj7-px3f mastodon Fixed in 4.8.0-alpha.2 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-62j4-hvj7-px3f
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences