nocodb
Affected
- introduced
0, fixed0.301.3(semver)
Fixed versions
0.301.3
Fix
- Fixed version
0.301.3npm install [email protected]
Advisory
Also known as: CVE-2026-28396
NocoDB's Refresh Tokens Not Revoked on Password Reset
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.
DetailspasswordReset() 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).
Medium Basis: The source's own band: MODERATE
0, fixed 0.301.3 (semver)0.301.3
0.301.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0