Advisory

GHSA-r989-7g3j-wjhw

Also known as: CVE-2026-53928

Summary

NocoDB: Refresh Tokens Persist Through Password Recovery

Details

Summary
A stolen refresh token survived a password-forgot flow and could be used to mint fresh
JWTs even after the user reset their password.

Details
passwordChange and passwordReset deleted the user's refresh tokens, but
passwordForgot only rotated token_version and revoked OAuth tokens — it did not
call UserRefreshToken.deleteAllUserToken(user.id). An attacker holding a captured
refresh cookie could still exchange it for a new access token after the victim
triggered the recovery flow.

Impact
Persistent unauthorized access after password recovery. Once a refresh token leaks, the
documented "Forgot password" recovery flow did not in fact revoke the attacker's
session.

Credit
This issue was reported by @bugbunny-research.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-17 14:07 UTC
Modified
2026-07-20 21:30 UTC

Affected packages and fixes

nocodb

npm · All systems

Affected

  • introduced 0, last affected 0.301.3 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences