CVE
NocoDB authorization bypass in ACL middleware
Affects NocoDB before 2026.10.1, with the Community Edition takeover path tied to releases 0.202.6 to 0.301.3, where organization Creators got user management permissions. 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. NocoDB Community Edition releases 0.202.6 to 0.301.3 granted the organization Creator role user management permissions. NocoDB Enterprise table granted the organization SSO client list to organization Creators. On NocoDB Cloud, workspace Creators could reach workspace SSO client routes declared for workspace Owners.
Summary
NocoDB before 2026.10.1 contains an incorrect authorization vulnerability that allows organization Creators to reach routes restricted to other roles because the aclFn middleware never enforced allowedRoles. Attackers can generate a super admin password reset link via org-users endpoints to take over the instance, or read and modify SSO client secrets.
Who should check
Teams running NocoDB Community Edition 0.202.6 to 0.301.3, NocoDB Enterprise, or NocoDB Cloud where users hold organization or workspace Creator roles.
“Community Edition releases from 0.202.6 to 0.301.3 granted the organization Creator role the user management permissions”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB Community Edition releases 0.202.6 to 0.301.3 granted the organization Creator role user management permissions. NocoDB Enterprise table granted the organization SSO client list to organization Creators. On NocoDB Cloud, workspace Creators could reach workspace SSO client routes declared for workspace Owners.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-130690 (NocoDB before 2026.10.1 Incorrect Authorization via Unenforced allowedRoles in Acl), 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-130690 (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):
- NocoDB Community Edition releases 0.202.6 to 0.301.3 granted the organization Creator role user management permissions. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4rrc-r66w-5v7f)
- NocoDB Enterprise table granted the organization SSO client list to organization Creators. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4rrc-r66w-5v7f)
- On NocoDB Cloud, workspace Creators could reach workspace SSO client routes declared for workspace Owners. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4rrc-r66w-5v7f)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130690 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130690 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-4rrc-r66w-5v7f
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-130690
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-130690"}.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-4rrc-r66w-5v7f |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130690 |
| Record | NVD · CVE-2026-130690 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130690
Is CVE-2026-130690 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?
A user with the organization Creator role could generate a password reset link for the super admin, set a new password, and sign in as super admin, taking control of a Community Edition instance. In Enterprise, the same role could read organization SSO client secrets, and on NocoDB Cloud a workspace Creator could change workspace SSO clients.Source: github.com
Which versions are affected by CVE-2026-130690?
nocodb: before 2026.10.1.Source: cve.now feed data
Am I affected, and how do I check?
Community Edition releases 0.202.6 to 0.301.3 granted the organization Creator role user management permissions. Enterprise granted the organization SSO client list to organization Creators, and on NocoDB Cloud workspace Creators could reach workspace SSO client routes declared for workspace Owners. Compare your installed version with the 0.202.6 to 0.301.3 range and check which edition and roles are in use.Source: github.com
How do I fix CVE-2026-130690?
Upgrade NocoDB to 2026.10.1, the fixed version listed for this vulnerability.Source: github.com