Skip to content
Fencer Intel
high 8.6

CVE-2026-130700 json

NocoDB before 2026.10.1 Consent Phishing via Unrestricted OAuth Client Registration

published 16d ago modified 13m ago also EUVD-2026-128772 , GHSA-hpmf-p392-q5j5

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository nocodb/nocodb. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
8.6
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

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.

Patch / fix

  • nocodb nocodb 2026.10.1

Is CVE-2026-130700 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
56m ago

CVSS scores

assigned by version score vector
CNA 4.0 8.6 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Inferred packages

No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.

ecosystem package repository affected
npm nocodb nocodb/nocodb
< 2026.10.1

Affected products

  • nocodb nocodb

Classification

Weakness
  • CWE-451 User Interface (UI) Misrepresentation of Critical Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of nocodb/nocodb published their own advisory on GitHub. Reviewed sources take precedence over it.