CVE-2026-28396
Prior to version 0.301.3, the password reset flow did not revoke existing refresh tokens, allowing an attacker with a previously stolen refresh token to continue minting valid JWTs after the victim resets their password.
Does this matter?
Lower severity and a low EPSS score (0.18%). Track it; it rarely justifies an emergency change on its own.
Description
NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, the password reset flow did not revoke existing refresh tokens, allowing an attacker with a previously stolen refresh token to continue minting valid JWTs after the victim resets their password. This issue has been patched in version 0.301.3.
- CVSS 4.0
- 4.9 MEDIUMCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.18% probability · 8th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-613
- Affected
- nocodb/nocodb
- Source
- security-advisories@github.com
References
- https://github.com/nocodb/nocodb/releases/tag/0.301.3Product, Release Notes
- https://github.com/nocodb/nocodb/security/advisories/GHSA-x4vh-j75g-268gVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.