How severe is GHSA-wpfr-6297-9v57?

No CVSS score has been assigned to GHSA-wpfr-6297-9v57 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wpfr-6297-9v57?

GHSA-wpfr-6297-9v57 affects the following packages: github.com/netlify/gotrue (Go). Ecosystems affected: Go.

How do I fix GHSA-wpfr-6297-9v57?

Update github.com/netlify/gotrue to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpfr-6297-9v57 is resolved across your whole dependency graph.

How do I detect GHSA-wpfr-6297-9v57 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/netlify/gotrue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-wpfr-6297-9v57 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-wpfr-6297-9v57 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wpfr-6297-9v57 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wpfr-6297-9v57 published, and has it been updated?

GHSA-wpfr-6297-9v57 was published on February 9, 2022 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

User object created with invalid provider data in GoTrueGHSA-wpfr-6297-9v57

Fix: netlify/gotrue#313

GHSA-wpfr-6297-9v57 is a security vulnerability in github.com/netlify/gotrue. A fix is available for github.com/netlify/gotrue — see the affected versions and patch details below.

Also known asGO-2022-0365

Published

Feb 9, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/netlify/gotrue

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 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]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/netlify/gotrue`	all versions	1.0.1`go get github.com/netlify/gotrue@v1.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/netlify/gotrue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/netlify/gotrue to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpfr-6297-9v57 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](https://github.com/netlify/gotrue/releases/tag/v1.0.1). ### Workarounds _Is

O3 Security · Impact-Aware SCA

Is GHSA-wpfr-6297-9v57 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works