CVE-2026-53928: NocoDB: Refresh Tokens Persist Through Password Recovery

Severity: medium (CVSS 6.3 v4.0)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-06-23 · updated 2026-06-25
Weakness: CWE-613

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.

Affected products

nocodb: before 2026.05.1

References

https://github.com/nocodb/nocodb/security/advisories/GHSA-r989-7g3j-wjhw

Get alerted when CVE-2026-53928 or the next vulnerability affects your stack