CVE
NocoDB consent phishing via open OAuth client registration
Affects NocoDB before 2026.10.1. Dynamic client registration exists only in the enterprise and cloud editions, not the community edition. Fixed in 2026.10.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.10.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected NocoDB versions before 2026.10.1. Dynamic client registration exists only in the enterprise and cloud editions; the community edition has no registration route.
Summary
NocoDB before 2026.10.1 contains a consent phishing vulnerability that allows unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs through the unauthenticated dynamic client registration endpoint. Attackers can impersonate trusted applications on a consent screen lacking unverified-client warnings or redirect host display, obtaining tokens to read and write victim tables and records.
Who should check
Teams running self-hosted or enterprise/cloud NocoDB before 2026.10.1 that expose OAuth dynamic client registration, including workspace owners who approve OAuth consent screens.
“Affected versions < 2026.10.1”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Affected NocoDB versions before 2026.10.1. Dynamic client registration exists only in the enterprise and cloud editions; the community edition has no registration route.Upgrade to a fixed version: 2026.10.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130700 (NocoDB before 2026.10.1 Consent Phishing via Unrestricted OAuth Client Registration), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130700 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.1
Fixed versions: 2026.10.1.
Conditions (all must be true for the bug to be hit):
- Affected NocoDB versions before 2026.10.1. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hpmf-p392-q5j5)
- Dynamic client registration exists only in the enterprise and cloud editions; the community edition has no registration route. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hpmf-p392-q5j5)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-130700 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130700 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-hpmf-p392-q5j5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130700
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130700"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.10.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-hpmf-p392-q5j5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130700 |
| Record | NVD · CVE-2026-130700 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130700
Is CVE-2026-130700 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
NocoDB's OAuth flow lets an attacker obtain an authorization code through a single consent click. That grants persistent access to read and write the victim's tables and records, webhook and automation configuration, and to enumerate workspaces, bases and collaborators.Source: github.com
Which versions are affected by CVE-2026-130700?
nocodb: before 2026.10.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are NocoDB releases before 2026.10.1. Dynamic client registration exists only in the enterprise and cloud editions; the community edition's OAuth controller has no registration route. Check the installed version and edition in the instance's version information.Source: github.com
How do I fix CVE-2026-130700?
Upgrade NocoDB to 2026.10.1 or later.Source: github.com