CVE-2026-23964: Mastodon has insufficient access control to push notification settings
Mastodon is a free, open-source social network server based on ActivityPub. Prior to versions 4.5.5, 4.4.12, and 4.3.18, an insecure direct object reference in the web push subscription update endpoint lets any authenticated user update another user's push subscription by guessing or obtaining the numeric subscription id. This can be used to disrupt push notifications for other users and also leaks the web push subscription endpoint. Any user with a web push subscription is impacted, because another authenticated user can tamper with their push subscription settings if they can guess or obtain the subscription id. This allows an attacker to disrupt push notifications by changing the policy (whether to filter notifications from non-followers or non-followed users) and subscribed notification types of their victims. Additionally, the endpoint returns the subscription object, which includes the push notification endpoint for this subscription, but not its keypair. Mastodon versions v4.5.5, v4.4.12, v4.3.18 are patched.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23964?
CVE-2026-23964 is considered to have a medium severity rating due to its impact on user privacy through insufficient access control.
How do I fix CVE-2026-23964?
To fix CVE-2026-23964, upgrade your Mastodon installation to version 4.5.5 or later.
What is the impact of CVE-2026-23964?
CVE-2026-23964 allows authenticated users to access and potentially modify push notification settings of other users due to insecure direct object reference.
Which versions of Mastodon are affected by CVE-2026-23964?
Mastodon versions prior to 4.5.5, 4.4.12, and 4.3.18 are affected by CVE-2026-23964.
Who is at risk from CVE-2026-23964?
Users of Mastodon prior to the patched versions are at risk of having their push notification settings accessed by other authenticated users.