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.
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.
An attacker who previously obtained a refresh token retains access after password reset until the token expires.
This issue was reported by @bugbunny-research (bugbunny.ai).
{
"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"
}