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 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.
Credit
This issue was reported by @bugbunny-research.
Impact
Persistent unauthorized access through previously issued OAuth tokens after a
documented security event (password change, forgot, or reset).
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-53926? CVE-2026-53926 is a medium-severity security vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1.
- Which versions of nocodb are affected by CVE-2026-53926? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-53926? Yes. CVE-2026-53926 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-53926 exploitable, and should I be worried? Whether CVE-2026-53926 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-53926 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-53926? Upgrade
nocodbto 2026.05.1 or later.