Skip to content

CVE-2026-42560 auth: Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation

CriticalCVSS 9.1 EPSS 0.42%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: yes · technical impact: partial

Description

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.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
go-pkgz auth(Go) >= 1.18.0, < 1.25.2; >= 1.18.0, <= 1.25.1; >= 2.0.0, < 2.1.2; >= 2.0.0, <= 2.1.1 1.25.2, 2.1.2 Fixed
go-pkgz auth = >= 1.18.0, < 1.25.2; = >= 2.0.0, < 2.1.2 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
go-pkgz auth = >= 1.18.0, < 1.25.2 No fix listed
go-pkgz auth = >= 2.0.0, < 2.1.2 No fix listed
go-pkgz auth(Go) >= 1.18.0, < 1.25.2 1.25.2
go-pkgz auth(Go) >= 2.0.0, < 2.1.2 2.1.2
go-pkgz auth(Go) >= 1.18.0, <= 1.25.1 No fix listed
go-pkgz auth(Go) >= 2.0.0, <= 2.1.1 No fix listed

References