Approved changes feed: RSS · Atom
cpe:2.3:a:go-pkgz:auth:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Go Pkgz (eb8dd23a-df34-5fcf-8621-585303186b39) |
|---|---|
| Product | Auth (86720101-33c4-5433-aefa-b3932ad62785) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42560 |
vulnerable | 2026-06-08 08:03:16.514048 |
auth: Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation
CRITICAL (9.1)
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.
Published: 2026-05-09T04:15:01.408Z
Updated: 2026-05-11T17:31:32.968Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.