CVE-2026-53928

NocoDB: Refresh Tokens Persist Through Password Recovery

MEDIUM
6.3
CVSS Score
Published: June 23, 2026 at 08:03 PM UTC
Updated: June 27, 2026 at 11:42 AM UTC
1 product affected across 1 vendorNocodb

Using nocodb by nocodb?

Get instant alerts when new vulnerabilities affect nocodb - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2026.05.1
Affected range stops below 2026.05.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.3MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-613

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card