CVE-2026-42560

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
33.6%
KEV
Not listed

Published

May 9, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated May 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation · Advisory · go-pkgz/auth · GitHub

https://github.com/go-pkgz/auth/security/advisories/GHSA-f6qq-3m3h-4g42
generic

Release Version 2.1.2 · go-pkgz/auth · GitHub

https://github.com/go-pkgz/auth/releases/tag/v2.1.2
generic

Release Version 1.25.2 · go-pkgz/auth · GitHub

https://github.com/go-pkgz/auth/releases/tag/v1.25.2
generic

Merge commit from fork · go-pkgz/auth@c0b15ee · GitHub

https://github.com/go-pkgz/auth/commit/c0b15ee72a8401da83c01781c16636c521f42698

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/go-pkgz/auth—1.25.2—
github.com/go-pkgz/auth/v2—2.1.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 08:54 UTCEG score recompute
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 03:43 UTCEG score recompute
  18. 2026-06-27 14:41 UTCEG score recompute
  19. 2026-06-27 10:33 UTCEG score recompute
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 21:12 UTCEG score recompute
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 75 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 17:53 UTCEPSS rescore
  10. 2026-06-17 05:42 UTCEG score recompute
  11. 2026-06-17 01:15 UTCEG score recompute
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-16 07:52 UTCEG score recompute
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-15 08:03 UTCEG score recompute
  16. 2026-06-15 03:03 UTCEG score recompute
  17. 2026-06-14 23:00 UTCEG score recompute
  18. 2026-06-14 18:58 UTCEG score recompute
  19. 2026-06-14 14:53 UTCEG score recompute
  20. 2026-06-14 10:50 UTCEG score recompute
  21. 2026-06-14 06:44 UTCEG score recompute
  22. 2026-06-14 02:22 UTCEG score recompute
  23. 2026-06-13 23:00 UTCEPSS rescore
  24. 2026-06-13 09:15 UTCEG score recompute
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 22:45 UTCEG score recompute
  28. 2026-06-12 18:33 UTCEG score recompute
  29. 2026-06-12 11:35 UTCEG score recompute
  30. 2026-06-12 07:27 UTCEG score recompute
  31. 2026-06-12 03:23 UTCEG score recompute
  32. 2026-06-11 23:19 UTCEG score recompute
  33. 2026-06-11 19:17 UTCEG score recompute
  34. 2026-06-11 15:14 UTCEG score recompute
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-11 11:03 UTCEG score recompute
  37. 2026-06-11 06:59 UTCEG score recompute
  38. 2026-06-11 02:56 UTCEG score recompute
  39. 2026-06-10 22:54 UTCEG score recompute
  40. 2026-06-10 22:18 UTCEPSS rescore
  41. 2026-06-10 18:51 UTCEG score recompute
  42. 2026-06-10 14:49 UTCEG score recompute
  43. 2026-06-10 13:22 UTCEPSS rescore
  44. 2026-06-10 13:22 UTCEPSS rescore
  45. 2026-06-10 10:47 UTCEG score recompute
  46. 2026-06-10 06:45 UTCEG score recompute
  47. 2026-06-10 02:43 UTCEG score recompute
  48. 2026-06-09 22:41 UTCEG score recompute
  49. 2026-06-09 16:46 UTCEG score recompute
  50. 2026-06-09 12:44 UTCEG score recompute
  51. 2026-06-09 08:42 UTCEG score recompute
  52. 2026-06-09 04:38 UTCEG score recompute
  53. 2026-06-09 00:36 UTCEG score recompute
  54. 2026-06-08 20:33 UTCEG score recompute
  55. 2026-06-08 14:17 UTCEPSS rescore
  56. 2026-06-08 14:17 UTCEPSS rescore
  57. 2026-06-08 13:25 UTCEG score recompute
  58. 2026-06-08 09:23 UTCEG score recompute
  59. 2026-06-08 05:21 UTCEG score recompute
  60. 2026-06-08 01:19 UTCEG score recompute
  61. 2026-06-07 21:17 UTCEG score recompute
  62. 2026-06-07 17:15 UTCEG score recompute
  63. 2026-06-07 15:25 UTCEPSS rescore
  64. 2026-06-07 15:25 UTCEPSS rescore
  65. 2026-06-07 13:12 UTCEG score recompute
  66. 2026-06-07 09:09 UTCEG score recompute
  67. 2026-06-07 05:07 UTCEG score recompute
  68. 2026-06-07 01:05 UTCEG score recompute
  69. 2026-06-06 21:03 UTCEG score recompute
  70. 2026-06-06 17:01 UTCEG score recompute
  71. 2026-06-06 13:47 UTCEPSS rescore
  72. 2026-06-06 13:47 UTCEPSS rescore
  73. 2026-06-06 12:59 UTCEG score recompute
  74. 2026-06-06 08:54 UTCEG score recompute
  75. 2026-06-06 04:52 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42560?
CVE-2026-42560 is a critical vulnerability published on May 9, 2026. 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…
When was CVE-2026-42560 disclosed?
CVE-2026-42560 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42560 actively exploited?
CVE-2026-42560 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42560?
CVE-2026-42560 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-42560?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42560, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42560

Explore →

Is Your Infrastructure Affected by CVE-2026-42560?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs