NocoDB before 2026.10.0 contains an insecure direct object reference vulnerability that allows authenticated users to
Source GCVE Database
Not known to be exploited · CVSS 6.0 Medium : upgrade to 2026.10.0 when convenient.
Data as of 18 Nov 2026, 14:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.0 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 2026.10.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Upgrade nocodb to 2026.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nocodbnocodb | Affected
| Fixed in
|
AI-suggested
A fix is available in NocoDB version 2026.10.0 and later. Users should upgrade to version 2026.10.0 or newer to remediate this vulnerability. No vendor advisory or patch links were provided, so verify the upgrade from official NocoDB sources.
Description
NocoDB versions before 2026.10.0 have an insecure direct object reference (IDOR) vulnerability. Authenticated users with write access to attachment columns can exploit this flaw to obtain signed download URLs for attachments belonging to other bases by inserting foreign attachment paths into their own data rows. This allows reading of cross-base files even when secure attachment mode is enabled.