NocoDB before 2026.08.0 contains an authorization bypass in shared-view relation endpoints because parent-record
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.08.0 when convenient.
Data as of 18 Nov 2026, 14:05 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 2026.08.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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.08.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nocodbnocodb | Affected
| Fixed in
|
AI-suggested
A fix is available in NocoDB version 2026.08.0 and later. Users should upgrade to version 2026.08.0 or newer to remediate this authorization bypass vulnerability. No other mitigation or temporary workaround is indicated in the provided data.
Description
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability in shared-view relation endpoints. This occurs because parent-record lookups rely solely on the primary key without applying the view's row filter. As a result, anonymous users with share links can enumerate auto-increment primary keys through various relation routes to access linked records that should be filtered out.