nocodb
Affected
- introduced
0, fixed2026.05.1(ecosystem)
Fixed versions
2026.05.1
Fix
- Fixed version
2026.05.1npm install [email protected]
Advisory
Also known as: CVE-2026-53926
NocoDB: OAuth Tokens Persist Through Security Events
Summary
OAuth access and refresh tokens were not revoked when the user changed, reset, or
recovered their password, leaving an attacker-issued OAuth grant valid after the user
believed they had locked the attacker out.
DetailsrevokeAllOAuthTokensByUser in the users service was an empty stub being called frompasswordChange, passwordForgot, and passwordReset. It now delegates toOAuthToken.revokeAllByUser(userId), which deletes the rows and invalidates the
related auth caches. All three reset/recovery flows now consistently revoke refresh
tokens (GHSA-r989-7g3j-wjhw), OAuth tokens (this advisory), and rotatetoken_version.
Impact
Persistent unauthorized access through previously issued OAuth tokens after a
documented security event (password change, forgot, or reset).
Credit
This issue was reported by @bugbunny-research.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.05.1 (ecosystem)2026.05.1
2026.05.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0