Vulnary
← back to the feed
Critical· 9.1official fix available

CVE-2026-42560

A critical flaw in the auth library used for Patreon OAuth causes all Patreon users to be treated as the same local account. This happens because the library incorrectly assigns the same local user ID to every authenticated Patreon account. As a result, users can inadvertently access each other's data or subscriptions.

publishedMay 9, 2026
last modifiedJul 24, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
34th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 25, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Applications that use the auth library for Patreon OAuth, specifically versions 1.18.0 through 1.25.1 and 2.0.0 through 2.1.1, are affected. Developers and site owners who rely on this library for user authentication should check their version.

02

Real-world impact

An attacker could gain access to another user's account, view or modify their subscription status, and potentially confuse or elevate privileges by exploiting the collapsed identity.

03

Why this severity

The CVSS score of 9.1 reflects that the vulnerability is exploitable over the network without authentication, provides complete confidentiality and integrity compromise for affected users, and has no mitigations in place. The lack of required privileges and the high impact on user data make it critical.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the auth library to version 1.25.2 or later, or to version 2.1.2 or later.

NVD-referenced vendor advisory

05

Timeline

  1. May 9, 2026 · May 9, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 24, 2026 · 11d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 26, 2026 · 10d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →