CVE-2026-42560
CriticalCVSS 9.1Exploitation Probability (EPSS)
Low risk34th percentile - higher than 34% of all known CVEs
Summary
The auth library (versions 1.18.0 to 1.25.2 and 2.0.0 to 2.1.2) incorrectly maps all authenticated Patreon users to the same local ID. This collapses identities, leading to unauthorized access and subscription data leakage.
Risk Assessment
Risk of user account mixing, privilege escalation, and exposure of subscription data.
Recommendation
Update the auth library to version 1.25.2 or 2.1.2. Verify that your application does not rely on token.User.ID as a stable account key.
Original NVD description (English source)
auth provides authentication via oauth2, direct and email. From versions 1.18.0 to before 1.25.2 and 2.0.0 to before 2.1.2, the Patreon OAuth provider maps every authenticated Patreon account to the same local user.ID, instead of deriving a unique ID from the Patreon account returned by Patreon. In practice, this means all Patreon-authenticated users of an application using this library are collapsed into a single local identity. Any application that trusts token.User.ID as the stable account key can end up mixing or fully merging unrelated Patreon users, which can lead to cross-account access, privilege confusion, and subscription-state leakage. This issue has been patched in versions 1.25.2 and 2.1.2.