# nhost has Session Persistence After Password Change

Advisory record · `GHSA-7hgr-xvrr-xpw3`

- **Identifiers:** `GHSA-7hgr-xvrr-xpw3` · `GO-2026-5222`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 8 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 May 2026, 17:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/nhost/nhost` (Go): affected `<0.0.0-20260430132514-52c70664a7e9`; fixed in `0.0.0-20260430132514-52c70664a7e9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> nhost (Go module github.com/nhost/nhost) versions before 0.0.0-20260430132514-52c70664a7e9 do not revoke existing sessions when a user changes their password, whether through the authenticated change endpoint or a password reset ticket. An attacker who has already stolen a victim's refresh token can keep using it to obtain new access tokens after the password change, potentially for as long as the configured token lifetime allows. Upgrade to 0.0.0-20260430132514-52c70664a7e9 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7hgr-xvrr-xpw3)

## Sources

- [GitHub Advisory Database: GHSA-7hgr-xvrr-xpw3](https://github.com/advisories/GHSA-7hgr-xvrr-xpw3)
- [OSV: GHSA-7hgr-xvrr-xpw3](https://osv.dev/vulnerability/GHSA-7hgr-xvrr-xpw3)
- <https://github.com/nhost/nhost/security/advisories/GHSA-7hgr-xvrr-xpw3>
- <https://github.com/nhost/nhost/commit/52c70664a7e92031e592b873471939b10ca18079>
- <https://github.com/nhost/nhost>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-7hgr-xvrr-xpw3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7hgr-xvrr-xpw3/>. Everything for agents: <https://agentprime.io/llms.txt>.
