CVE-2026-53928

NocoDB: Refresh Tokens Persist Through Password Recovery

State: Published
Severity: 6.3 Medium
Published: Jun 23, 2026
Updated: Jun 24, 2026
Reserved: Jun 11, 2026

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.

Scores

CVSS	Score	Vector	Source
4.0	6.3 Medium	CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N	GitHub_M

Weaknesses

CWE-613 Insufficient Session Expiration

Affected Products

Product	Versions
nocodbnocodb	< 2026.05.1Affected

References

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

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.