Vulnerability · Published Jun 23, 2026 · Assigned by GitHub_M

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

Medium 6.3

In plain English

A medium-severity security flaw in nocodb from nocodb. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 29% of all known vulnerabilities).

Severity (CVSS 4.0)6.3Medium

Exploit odds (30 days)0.4%top 70.5% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	nocodb	no fix listed	GHSA-r989-7g3j-wjhw

Affected products (as reported)

Vendor	Product	Versions
nocodb	nocodb	< 2026.05.1

Weakness: CWE-613 · Vector: 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

References

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