CVE-2026-53926 NocoDB: OAuth Tokens Persist Through Security Events

Medium 6.3 Published Updated

Attackers retain valid OAuth access after users change or reset passwords because token revocation logic is missing, allowing persistent unauthorized access.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-53926?

CVE-2026-53926 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, revokeAllOAuthTokensByUser in the users service is an empty stub being called from passwordChange, passwordForgot, and passwordReset. 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. This vulnerability is fixed in 2026.05.1.

Weakness: CWE-613

Which versions are affected by CVE-2026-53926?

2 open source packages ship an affected version, including nocodb.

PackageAffectedFixed in
nocodb npmAll versions2026.05.1
nocodb npmAll versions2026.05.1

How do I fix CVE-2026-53926?

Upgrade nocodb to 2026.05.1 or later.

Is CVE-2026-53926 being exploited?

There is no known exploitation of CVE-2026-53926 in the wild and no public exploit code.

Sources

Also known as GHSA-g72g-r7m4-9x4g.

Is CVE-2026-53926 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free