GHSA-7hgr-xvrr-xpw3: Github.com/nhost/nhost Nhost Has Session Persistence After Vulnerability

LOW
Share
CWE-613
Published
Advisory Summary

GHSA-7hgr-xvrr-xpw3 is a LOW nhost has session persistence after vulnerability (CWE-613: Insufficient Session Expiration) affecting Github.com/nhost/nhost libraries in the Go ecosystem. The issue involves nhost has session persistence after password change. Remediation is available by upgrading affected packages to version 0.0.0-20260430132514-52c70664a7e9.

GHSA-7hgr-xvrr-xpw3 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7hgr-xvrr-xpw3
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product Github.com/nhost/nhost
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-7hgr-xvrr-xpw3

To remediate this vulnerability, upgrade all affected Github.com/nhost/nhost dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/nhost/nhost fixed: 0.0.0-20260430132514-52c70664a7e9 
Upgrade github.com/nhost/nhost to 0.0.0-20260430132514-52c70664a7e9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/nhost/nhost

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7hgr-xvrr-xpw3, inspect your project dependencies for Github.com/nhost/nhost:

inspect dependencies for github.com/nhost/nhost

Analyze the terminal output to locate any version of Github.com/nhost/nhost in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260430132514-52c70664a7e9), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Github.com/nhost/nhost, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Description When a user changes their password, either through the authenticated password change endpoint or a password reset ticket, the [`ChangePassword`](https://github.com/nhost/nhost/blob/main/services/auth/go/controller/workflows.go#L731-L759) workflow correctly hashes and persists the new password via [`UpdateUserChangePassword`](https://github.com/nhost/nhost/blob/main/services/auth/go/sql/query.sql#L314-L318). However, it does not revoke existing sessions. The `auth.refresh_tokens` and `auth.oauth2_refresh_tokens` 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 [`change_user_password.go`](https://github.com/nhost/nhost/blob/main/services/auth/go/controller/change_user_password.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.oauth2_refresh_tokens` ## 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 server updates `password_hash` but performs no session cleanup, the stolen token remains fully functional. ## Impact The attacker retains persistent access even after the victim's password change. This is especially severe in credential theft scenarios, where the victim's only recovery action does nothing against an active session. Depending on configured TTL, the attacker's window could be days or weeks.

GHSA-7hgr-xvrr-xpw3 Affected Github.com/nhost/nhost Versions

1 component(s)
Fixed Versions:
0.0.0-20260430132514-52c70664a7e9
Product / Package Ecosystem Affected Versions Fixed Version
github.com/nhost/nhost
golang/github.com/nhost/nhost
Go
< 0.0.0-20260430132514-52c70664a7e9
0.0.0-20260430132514-52c70664a7e9

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nhost/nhost/security/advisories/GHSA-7hgr-xvrr-xpw3
Security Fix Commit FIX COMMIT
https://github.com/nhost/nhost/commit/52c70664a7e92031e592b873471939b10ca18079
Github.com/nhost/nhost Source Repository REPOSITORY
https://github.com/nhost/nhost

Frequently Asked Questions

What is GHSA-7hgr-xvrr-xpw3?
GHSA-7hgr-xvrr-xpw3 is a security vulnerability in Github.com/nhost/nhost involving nhost has Session Persistence After Password Change under CWE-613: Insufficient Session Expiration.
Which Github.com/nhost/nhost versions are affected?
Affected versions include releases prior to 0.0.0-20260430132514-52c70664a7e9 across affected packages: github.com/nhost/nhost.
What version fixes GHSA-7hgr-xvrr-xpw3?
Upgrading to 0.0.0-20260430132514-52c70664a7e9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/nhost/nhost affected?
Yes, github.com/nhost/nhost is affected in releases prior to 0.0.0-20260430132514-52c70664a7e9. Upgrade your dependency to 0.0.0-20260430132514-52c70664a7e9 or later.
What CWE is associated with GHSA-7hgr-xvrr-xpw3?
GHSA-7hgr-xvrr-xpw3 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check Go dependencies for GHSA-7hgr-xvrr-xpw3?
Run the dependency tree command: 'inspect dependencies for github.com/nhost/nhost'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7hgr-xvrr-xpw3",
  "modified" : "2026-05-08T17:39:48Z",
  "published" : "2026-05-08T17:39:48Z",
  "aliases" : [ ],
  "summary" : "nhost has Session Persistence After Password Change",
  "details" : "## Description\n\nWhen a user changes their password, either through the authenticated password change endpoint or a password reset ticket, the [`ChangePassword`](https://github.com/nhost/nhost/blob/main/services/auth/go/controller/workflows.go#L731-L759) workflow correctly hashes and persists the new password via [`UpdateUserChangePassword`](https://github.com/nhost/nhost/blob/main/services/auth/go/sql/query.sql#L314-L318). However, it does not revoke existing sessions. The `auth.refresh_tokens` and `auth.oauth2_refresh_tokens` tables are left untouched, meaning all previously issued refresh tokens remain valid and can continue generating new access tokens indefinitely.\n\nThis vulnerability affects all password change paths (handled in [`change_user_password.go`](https://github.com/nhost/nhost/blob/main/services/auth/go/controller/change_user_password.go)), since they share the same underlying workflow:\n\n- Authenticated password change via the Nhost dashboard or client SDK\n- Ticket-based password reset (magic links / recovery flows)\n- OAuth2/OIDC sessions managed via `auth.oauth2_refresh_tokens`\n\n## Attack Scenario\n\n1. An attacker steals a victim's refresh token via XSS or a compromised device.\n2. The victim changes their password, expecting it to terminate all active sessions.\n3. The server updates `password_hash` but performs no session cleanup, the stolen token remains fully functional.\n\n## Impact\n\nThe attacker retains persistent access even after the victim's password change. This is especially severe in credential theft scenarios, where the victim's only recovery action does nothing against an active session. Depending on configured TTL, the attacker's window could be days or weeks.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/nhost/nhost"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260430132514-52c70664a7e9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nhost/nhost/security/advisories/GHSA-7hgr-xvrr-xpw3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nhost/nhost/commit/52c70664a7e92031e592b873471939b10ca18079"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nhost/nhost"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-613" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T17:39:48Z",
    "nvd_published_at" : null
  }
}