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.
Published: 2026-05-09
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises from the Patreon OAuth provider in the go-pkgz/auth library mapping every authenticated Patreon account to the same local user.ID value, rather than deriving a unique identifier from the Patreon account. This flaw causes all Patreon-authenticated users to collapse into a single local identity. Applications that rely on token.User.ID as a stable account identifier can inadvertently merge unrelated users, resulting in cross‑account access, privilege confusion and leakage of subscription data. The weakness is an access control bypass identified as CWE‑287.

Affected Systems

Vulnerable applications use the go-pkgz/auth library version range 1.18.0 through 1.25.2‑exclusive in the v1 branch, or 2.0.0 through 2.1.2‑exclusive in the v2 branch. Versions 1.25.2 and 2.1.2 contain the patch that assigns unique local IDs for each Patreon account. Systems built on earlier releases are at risk unless the library is updated.

Risk and Exploitability

The CVSS score of 9.1 indicates high severity and a substantial impact if exploited. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. Attacks are likely to occur within applications that trust the provider’s user identifier for authentication state. The exploit requires only a legitimate Patreon login and the affected library, so an attacker can impersonate any Patreon user without additional privileges. Given the critical Nature of the flaw and the ease of exploitation, a rapid response is advised.

Generated by OpenCVE AI on May 9, 2026 at 06:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the go-pkgz/auth library to v1.25.2 or newer in the v1 branch, or to v2.1.2 or newer in the v2 branch, to restore unique local identity assignment.
  • If an immediate upgrade is infeasible, modify the authentication flow to use the Patreon account identifier returned in the token payload instead of token.User.ID as the stable key for user identity and access control.
  • Re‑architect any logic that hinges on the assumption that token.User.ID equals a unique, persistent local ID; ensure that user session state and privilege enforcement are based on the corrected identifier to prevent cross‑account contamination.

Generated by OpenCVE AI on May 9, 2026 at 06:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-f6qq-3m3h-4g42 auth: Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation
History

Sat, 09 May 2026 05:30:00 +0000

Type Values Removed Values Added
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.
Title auth: Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-09T04:15:01.408Z

Reserved: 2026-04-28T16:56:50.192Z

Link: CVE-2026-42560

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-09T06:16:10.603

Modified: 2026-05-09T06:16:10.603

Link: CVE-2026-42560

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-09T06:30:25Z

Weaknesses