Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
NocoDB versions before 0.301.3 do not check ownership of MCP tokens, so a user with the Creator role in the same base can read, regenerate, or delete another user's MCP token if they know its token ID. The main impacts are invalidating others' tokens and disclosing scoped token data. Upgrade the nocodb npm package to 0.301.3 or later.
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.0019, the 8th 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, 22:45 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-p9x3-w98f-7j3q
- OSV: GHSA-p9x3-w98f-7j3q
- github.com/nocodb/nocodb/security/advisories/GHSA-p9x3-w98f-7j3q
- nvd.nist.gov/vuln/detail/CVE-2026-28361
- github.com/nocodb/nocodb/commit/4e736ee40951c7b4f9760f372780e0712c44b9dd
- github.com/nocodb/nocodb
- github.com/nocodb/nocodb/releases/tag/0.301.3