CVE-2026-42560Public exploitNetwork attack vector

Cross-user impersonation via uninitialized Patreon ID hash

Published May 9, 2026 · Updated May 9, 2026

Improper authentication in GO-PKGZ auth 1.18.0 through 1.25.1 and 2.0.0 through 2.1.1 allows remote attackers to access other accounts. In provider/providers.go and v2/provider/providers.go, Patreon mapping hashes the newly created, still-empty userInfo.ID instead of uinfoJSON.Data.ID, yielding the same local ID for every Patreon response. Exploitation requires a target application to enable Patreon login and trust token.User.ID as its account key; affected users can inherit another user's data, roles, entitlements, or subscription state.

CVSS severity9.1
Critical
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in GO-PKGZ auth 1.18.0 through 1.25.1 and 2.0.0 through 2.1.1 allows remote attackers to access other accounts. In provider/providers.go and v2/provider/providers.go, Patreon mapping hashes the newly created, still-empty userInfo.ID instead of uinfoJSON.Data.ID, yielding the same local ID for every Patreon response. Exploitation requires a target application to enable Patreon login and trust token.User.ID as its account key; affected users can inherit another user's data, roles, entitlements, or subscription state.

The record

CVE
CVE-2026-42560
Published
May 9, 2026
Updated
May 9, 2026
Vendor
Supabase
Product
auth
Classifications
CWE-287, T1078
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 9, 2026CVE publishedPublication date reported by the CVE source.
  2. May 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.18.0, < 1.25.2
  2. Affected versionversion=>= 2.0.0, < 2.1.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Supabase · authversion=>= 1.18.0, < 1.25.2; version=>= 2.0.0, < 2.1.2

Published CVSS scores

9.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-287Improper Authentication
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo