nhost has Session Persistence After Password Change

Exploitation

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

CVSS 4.0

2.3 · 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 · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Description When a user changes their password, either through the authenticated password change endpoint or a password reset ticket, the ChangePassword workflow correctly hashes and persists the new password via UpdateUserChangePassword. However, it does not revoke existing sessions. The auth.refreshtokens and auth.oauth2refreshtokens tables are left untouched, meaning all previously issued refresh tokens remain valid and can continue generating new access tokens indefinitely. This vulnerability affects all password change paths (handled in changeuserpassword.go), since they share the same underlying workflow: - Authenticated password change via the Nhost dashboard or client SDK - Ticket-based password reset (magic links / recovery flows) - OAuth2/OIDC sessions managed via auth.oauth2refreshtokens Attack Scenario 1. An attacker steals a victim's refresh token via XSS or a compromised device. 2. The victim changes their password, expecting it to terminate all active sessions. 3. The…

Published by the source

8 May 2026, 17:39 UTC

Last modified by the source

8 May 2026, 17:39 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7hgr-xvrr-xpw3

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

# Patch Next advisory brief: GHSA-7hgr-xvrr-xpw3

Advisory: nhost has Session Persistence After Password Change
IDs: GHSA-7hgr-xvrr-xpw3
Record: https://patchnext.com/advisories/ghsa-7hgr-xvrr-xpw3 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/nhost/nhost 0.0.0-20260430132514-52c70664a7e9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/nhost/nhost: affected < 0.0.0-20260430132514-52c70664a7e9; fixed in 0.0.0-20260430132514-52c70664a7e9

## Suggested inspection (read-only)
- Go github.com/nhost/nhost: 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/nhost/nhost.
- 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-7hgr-xvrr-xpw3 (GitHub-reviewed advisory GHSA-7hgr-xvrr-xpw3 lists affected ranges: Go github.com/nhost/nhost >=0 <0.0.0-20260430132514-52c70664a7e9)

Commands are suggestions: review each one before running it.