Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
NocoDB versions before 0.301.3 are affected. A user who previously obtained a refresh token can keep minting valid access tokens after the victim resets their password, until that refresh token expires. Upgrade to NocoDB 0.301.3 or later. No workaround is given in the source.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.9 | Medium | 4.0 | CVSS: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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0021, the 11th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 2 Mar 2026, 19:53 UTC Confirmed by GitHub Advisory Database
- 5 Nov 2026, 23:00 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-x4vh-j75g-268g
- OSV: GHSA-x4vh-j75g-268g
- github.com/nocodb/nocodb/security/advisories/GHSA-x4vh-j75g-268g
- nvd.nist.gov/vuln/detail/CVE-2026-28396
- github.com/nocodb/nocodb/commit/dfbe836577354ba780563a5cf8cb50bfc61a203e
- github.com/nocodb/nocodb
- github.com/nocodb/nocodb/releases/tag/0.301.3