User object created with invalid provider data in GoTrue

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? Under certain circumstances a valid user object would have been created with invalid provider metadata. This vulnerability affects everyone running an instance of GoTrue as a service. We advise you to update especially if you are using the provider metadata from the user object to secure other resources. Patches Has the problem been patched? What versions should users upgrade to? A patch is available with the release of version 1.0.1 on Github. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? If you don't rely on the provider metadata in the user object, you might not be affected. We still strongly recommend upgrading. References Are there any links users can visit to find out more? This problem was initially found and reported by the team at Supabase: https://github.com/supabase/gotrue/security/advisories/GHSA-5hvv-9cqv-894r. We want to thank them for the cooperation around this…

Published by the source

9 Feb 2022, 22:29 UTC

Last modified by the source

11 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wpfr-6297-9v57

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-wpfr-6297-9v57

Advisory: User object created with invalid provider data in GoTrue
IDs: GHSA-wpfr-6297-9v57
Record: https://patchnext.com/advisories/ghsa-wpfr-6297-9v57 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/netlify/gotrue 1.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/netlify/gotrue: affected < 1.0.1; fixed in 1.0.1

## Suggested inspection (read-only)
- Go github.com/netlify/gotrue: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/netlify/gotrue.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wpfr-6297-9v57 (GitHub-reviewed advisory GHSA-wpfr-6297-9v57 lists affected ranges: Go github.com/netlify/gotrue >=0 <1.0.1)

Commands are suggestions: review each one before running it.