NocoDB from 2026.07.0 before 2026.10.0 contains an sql injection vulnerability that allows users with Creator role to
Source GCVE Database
Not known to be exploited · CVSS 7.0 High : upgrade to 2026.10.0 soon.
Data as of 18 Nov 2026, 14:07 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.0 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.5 |
- Patch
- Available – fixed in 2026.10.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:L/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
Since this vulnerability requires the attacker to have Creator role privileges, restricting this role to trusted users reduces risk. Monitor vendor advisories for forthcoming patches and apply updates once available. Avoid granting Creator role unnecessarily and review formula inputs for unescaped characters as a temporary precaution.
Description
NocoDB versions from 2026.07.0 up to but not including 2026.10.0 contain an SQL injection vulnerability. This flaw allows users with the Creator role to inject SQL via unescaped backslashes in the DATETIME_FORMAT formula's format argument on MySQL-backed databases. Exploitation can lead to unauthorized reading of data accessible by the database user, including data outside the intended base.