Skip to main content
VulnerabilityPublished Updated

CVE-2026-28361: NocoDB Missing Ownership Validation

Affects nocodbSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.301.3 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.301.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade nocodb to 0.301.3.

Affected software

ProductAffectedFixed in
npmnocodbAffected
  • <0.301.3
Fixed in
  • 0.301.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade NocoDB to version 0.301.3 or later, where this vulnerability is fixed. No additional mitigation is required as the patch fully addresses the issue.

Description

NocoDB versions prior to 0.301.3 contain a vulnerability in the MCP token service where token ownership is not validated. This allows a user with the Creator role within the same base to read, regenerate, or delete another user's MCP tokens if they know the token ID. The issue affects the McpTokenService methods get(), regenerateToken(), and delete(), which do not filter by user ID, unlike the ApiTokensService. The primary impact is limited to denial of service by invalidating tokens and scoped token disclosure. A fix is available in version 0.301.3.

References

Community reviews

Loading reviews…