Skip to content
Fencer Intel
medium 5.1

CVE-2026-130693 json

NocoDB from 0.253.0 before 2026.09.1 Incorrect Authorization via Base Member Removal

published 16d ago modified 2h ago also GHSA-jmgj-cq6g-6hr2 , EUVD-2026-128767

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
5.1
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 from 0.253.0 before 2026.09.1 contains an incorrect authorization vulnerability in baseUserDelete that allows base Creators to remove higher-privileged Owners due to a broken role power comparison. Attackers holding the Creator role can remove other Owners of a base, since getProjectRolePower returns -1 for the target and never refuses the request.

Patch / fix

  • nocodb nocodb 2026.09.1

Is CVE-2026-130693 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

CVSS scores

assigned by version score vector
CNA 4.0 5.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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
>= 0.253.0, < 2026.09.1

Affected products

  • nocodb nocodb

Classification

Weakness

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.