NocoDB before 2026.10.1 contains a consent phishing vulnerability that allows unauthenticated attackers to register
Source GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 2026.10.1 soon.
Data as of 18 Nov 2026, 14:07 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.6 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.1 |
- Patch
- Available – fixed in 2026.10.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/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.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nocodbnocodb | Affected
| Fixed in
|
AI-suggested
A fix is available in NocoDB version 2026.10.1. Users should upgrade to this version or later to remediate the vulnerability. Since no vendor advisory or patch links were provided, confirm patch availability and remediation details from official NocoDB sources before applying updates.
Description
NocoDB versions before 2026.10.1 have a consent phishing vulnerability that permits unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs via an unauthenticated dynamic client registration endpoint. This flaw allows attackers to impersonate trusted applications on the consent screen without unverified-client warnings or redirect host display, enabling them to obtain tokens that can read and write victim tables and records.