CVE-2026-53928 NocoDB: Refresh Tokens Persist Through Password Recovery
Attackers with stolen refresh tokens can maintain access after password resets because the recovery flow fails to revoke existing tokens.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-53928?
CVE-2026-53928 is a medium-severity authentication bypass vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-613
Which versions are affected by CVE-2026-53928?
2 open source packages ship an affected version, including nocodb.
| Package | Affected | Fixed in |
|---|---|---|
nocodb npm | All versions to 0.301.3 | None |
nocodb npm | All versions to 0.301.3 | None |
How do I fix CVE-2026-53928?
No fix has been published for CVE-2026-53928 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-53928 being exploited?
There is no known exploitation of CVE-2026-53928 in the wild and no public exploit code.
Sources
Also known as GHSA-r989-7g3j-wjhw.