GHSA-x4vh-j75g-268g

Suggest an improvement
Source
https://github.com/advisories/GHSA-x4vh-j75g-268g
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-x4vh-j75g-268g/GHSA-x4vh-j75g-268g.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-x4vh-j75g-268g
Aliases
Published
2026-03-02T19:53:17Z
Modified
2026-03-04T15:17:06.274906Z
Severity
  • 4.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U CVSS Calculator
Summary
NocoDB's Refresh Tokens Not Revoked on Password Reset
Details

Summary

The password reset flow did not revoke existing refresh tokens, allowing an attacker with a previously stolen refresh token to continue minting valid JWTs after the victim resets their password.

Details

passwordReset() in users.service.ts updated token_version (invalidating JWTs) but did not call UserRefreshToken.deleteAllUserToken(). The refreshToken() method only checked token existence, not token_version. Both passwordChange() and signOut() correctly deleted all refresh tokens.

Impact

An attacker who previously obtained a refresh token retains access after password reset until the token expires.

Credit

This issue was reported by @bugbunny-research (bugbunny.ai).

Database specific
{
    "severity": "MODERATE",
    "cwe_ids": [
        "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-02T19:53:17Z",
    "nvd_published_at": "2026-03-02T17:16:34Z"
}
References

Affected packages

npm / nocodb

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.301.3

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-x4vh-j75g-268g/GHSA-x4vh-j75g-268g.json"
last_known_affected_version_range
"<= 0.301.2"