CVE-2026-53926
NocoDB: OAuth Tokens Persist Through Security Events
Description
### 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. ### Details `revokeAllOAuthTokensByUser` in the users service was an empty stub being called from `passwordChange`, `passwordForgot`, and `passwordReset`. It now delegates to `OAuthToken.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 rotate `token_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](https://github.com/bugbunny-research).
How to fix CVE-2026-53926
To remediate CVE-2026-53926, upgrade the affected package to a fixed version below.
- —upgrade to 2026.05.1 or later
Is CVE-2026-53926 being exploited?
No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-53926.
Affected packages (1)
- from 0, < 2026.05.1
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 4.0 | — | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |