CVE-2026-28396
NocoDB's Refresh Tokens Not Revoked on Password Reset
Auswirkung
### 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](https://github.com/bugbunny-research) (bugbunny.ai).
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, mit einem normalen Benutzerkonto, ohne Zutun eines Nutzers. Bei Erfolg: hohes Risiko, dass Daten oder Systeme verändert werden.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| npm | nocodb | <= 0.301.2 | 0.301.3 |
Betroffene Produkte · Nocodb
| Produkt | Betroffene Versionen |
|---|---|
| Nocodb | vor 0.301.3 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://github.com/nocodb/nocodb/releases/tag/0.301.3
- https://github.com/nocodb/nocodb/security/advisories/GHSA-x4vh-j75g-268g
- https://github.com/advisories/GHSA-x4vh-j75g-268g
- https://nvd.nist.gov/vuln/detail/CVE-2026-28396
- https://github.com/nocodb/nocodb/commit/dfbe836577354ba780563a5cf8cb50bfc61a203e