NocoDB before 2026.08.0 contains a server-side request forgery vulnerability that allows authenticated base Editors to
Source GCVE Database
Not known to be exploited · CVSS 8.4 High : upgrade to 2026.08.0 soon.
Data as of 18 Nov 2026, 14:04 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.4 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.5 |
- Patch
- Available – fixed in 2026.08.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/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 fixed version 2026.08.0 is indicated by the version cutoff, so upgrading to version 2026.08.0 or later is recommended to remediate this vulnerability. Restricting base Editor privileges and monitoring for unusual backend requests may reduce risk until the upgrade is applied.
Description
NocoDB versions prior to 2026.08.0 have a server-side request forgery (SSRF) vulnerability that allows authenticated users with base Editor privileges to make arbitrary backend HTTP requests. This flaw enables attackers to control HTTP method, headers, and body to access internal APIs, loopback services, and cloud metadata endpoints, potentially exposing sensitive decrypted integration secrets.