Summary
User object created with invalid provider data in GoTrue
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 report.
In contrast to their advisory, we decided to set the severity to "Moderate" since the provider metadata is not an inherent security feature of this GoTrue codebase or the Netlify ecosystem.
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-WPFR-6297-9V57? GHSA-WPFR-6297-9V57 is a medium-severity security vulnerability in github.com/netlify/gotrue (go), affecting versions < 1.0.1. It is fixed in 1.0.1.
- Which versions of github.com/netlify/gotrue are affected by GHSA-WPFR-6297-9V57? github.com/netlify/gotrue (go) versions < 1.0.1 is affected.
- Is there a fix for GHSA-WPFR-6297-9V57? Yes. GHSA-WPFR-6297-9V57 is fixed in 1.0.1. Upgrade to this version or later.
- Is GHSA-WPFR-6297-9V57 exploitable, and should I be worried? Whether GHSA-WPFR-6297-9V57 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-WPFR-6297-9V57 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-WPFR-6297-9V57? Upgrade
github.com/netlify/gotrueto 1.0.1 or later.