CVE-2024-25618

External OpenID Connect Account Takeover by E-Mail Change in mastodon

HIGH
7.4
CVSS Score
Published: February 14, 2024 at 08:45 PM UTC
Updated: June 17, 2026 at 07:16 AM UTC
2 products affected across 2 vendorsMastodonMastodon

Using mastodon by mastodon?

Get instant alerts when new vulnerabilities affect mastodon - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.5%
SSVC
PoC

Description

Mastodon is a free, open-source social network server based on ActivityPub. Mastodon allows new identities from configured authentication providers (CAS, SAML, OIDC) to attach to existing local users with the same e-mail address. This results in a possible account takeover if the authentication provider allows changing the e-mail address or multiple authentication providers are configured. When a user logs in through an external authentication provider for the first time, Mastodon checks the e-mail address passed by the provider to find an existing account. However, using the e-mail address alone means that if the authentication provider allows changing the e-mail address of an account, the Mastodon account can immediately be hijacked. All users logging in through external authentication providers are affected. The severity is medium, as it also requires the external authentication provider to misbehave. However, some well-known OIDC providers (like Microsoft Azure) make it very easy to accidentally allow unverified e-mail changes. Moreover, OpenID Connect also allows dynamic client registration. This issue has been addressed in versions 4.2.6, 4.1.14, 4.0.14, and 3.5.18. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.5.184.0.0 ≤ v < 4.0.144.1.0 ≤ v < 4.1.144.2.0 ≤ v < 4.2.6
Affected range stops below 3.5.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.6, so it looks safe — our inference, not a vendor statement
v < 3.5.18v < 4.0.14v < 4.1.14v < 4.2.6
Affected range stops below 3.5.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-287CWE-306

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card