CVE-2026-34969 Nhost Leaks the Refresh Token via URL Query Parameter in OAuth Provider Callback
Nhost leaks refresh tokens via URL query parameters in OAuth callbacks, exposing them to logs and history, allowing potential session hijacking.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-34969?
CVE-2026-34969 is a low-severity vulnerability in nhost, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Nhost is an open source Firebase alternative with GraphQL. Prior to 0.48.0, the auth service's OAuth provider callback flow places the refresh token directly into the redirect URL as a query parameter. Refresh tokens in URLs are logged in browser history, server access logs, HTTP Referer headers, and proxy/CDN logs. Note that the refresh token is one-time use and all of these leak vectors are on owned infrastructure or services integrated by the application developer. This vulnerability is fixed in 0.48.0.
Which versions are affected by CVE-2026-34969?
3 open source packages ship an affected version, including github.com/nhost/nhost. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/nhost/nhost Go | All versions | 0.0.0-20260330133707-294954e0fc3a |
github.com/nhost/nhost Go | All versions | 0.0.0-20260330133707-294954e0fc3a |
github.com/nhost/nhost Go | All versions | 0.0.0-20260330133707-294954e0fc3a |
Products include Nhost Nhost\/Auth.
How do I fix CVE-2026-34969?
Upgrade github.com/nhost/nhost to 0.0.0-20260330133707-294954e0fc3a or later.
Is CVE-2026-34969 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34969 exists.
Other vulnerabilities in nhost
Sources
Also known as GHSA-g2qj-prgh-4g9r, GO-2026-5388.