VulnerabilityDeferred

CVE-2026-53928

An attacker holding a captured refresh cookie could still exchange it for a new access token after the victim triggered the recovery flow.

MEDIUM 6.3EPSS 0.31%

Does this matter?

Lower severity and a low EPSS score (0.31%). Track it; it rarely justifies an emergency change on its own.

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.

CVSS 4.0: 6.3 MEDIUMCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
EPSS: 0.31% probability · 24th percentile
CISA KEV: Not listed
Weakness: CWE-613
Source: security-advisories@github.com

References

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

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.