Most recent entries from all

EUVD-2026-329803

2026-10-06T08:35:11.484203+00:00

EUVD-2026-329803

fkie_cve-2026-53928

2026-10-06T08:35:11.484240+00:00

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a stolen refresh token survived a password-forgot flow and could be used to mint fresh JWTs even after the user reset their password. passwordChange and passwordReset deleted the user's refresh tokens, but passwordForgot only rotated token_version and revoked OAuth tokens — it did not call UserRefreshToken.deleteAllUserToken(user.id). An attacker holding a captured refresh cookie could still exchange it for a new access token after the victim triggered the recovery flow. This vulnerability is fixed in 2026.05.1.

GHSA-r989-7g3j-wjhw — NocoDB: Refresh Tokens Persist Through Password Recovery

2026-10-06T08:35:11.484279+00:00

Affected: npm: nocodb

### Summary A stolen refresh token survived a password-forgot flow and could be used to mint fresh JWTs even after the user reset their password.

### Details `passwordChange` and `passwordReset` deleted the user's refresh tokens, but `passwordForgot` only rotated `token_version` and revoked OAuth tokens — it did not call `UserRefreshToken.deleteAllUserToken(user.id)`. An attacker holding a captured refresh cookie could still exchange it for a new access token after the victim triggered the recovery flow.

### Impact Persistent unauthorized access after password recovery. Once a refresh token leaks, the documented "Forgot password" recovery flow did not in fact revoke the attacker's session.

### Credit This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research).