Advisory record · GHSA-f6qq-3m3h-4g42

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

CVSS 9.1 CriticalCriticalEPSS 0.0042 · 36th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 30 Apr 2026, 20:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/go-pkgz/authGo>=1.18.0, <1.25.21.25.2
github.com/go-pkgz/auth/v2Go>=2.0.0, <2.1.22.1.2
Identifiers
GHSA-f6qq-3m3h-4g42 · CVE-2026-42560 · GO-2026-5348
Weakness (CWE)
CWE-287
Published
30 Apr 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Patreon authentication in github.com/go-pkgz/auth (versions >=1.18.0, <1.25.2) and github.com/go-pkgz/auth/v2 (versions >=2.0.0, <2.1.2) assigns the same local user ID to every Patreon account, so distinct Patreon users are merged into one identity. An application that treats the user ID as an account key can then expose or mix data across Patreon users, with the impact depending on how the application uses that ID. Upgrade to 1.25.2 or 2.1.2 to fix the issue; the source gives no workaround.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 36th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.