Skip to main content
Menu
CVEs

CVE

NocoDB invitation token disclosure in workspace member list

Affects NocoDB community edition from 0.301.4 before 2026.10.0 when a higher-role pending invitation exists in a workspace. Fixed in 2026.10.0.

CVE-2026-130697Published Updated Summary written by a model

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.10.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects NocoDB versions >= 0.301.4 and < 2026.10.0. Community edition is affected; enterprise edition is not. An unexpired pending invitation for a higher role must exist in the workspace.

Summary

NocoDB from 0.301.4 before 2026.10.0 contains an information disclosure vulnerability that allows authenticated workspace viewers to read pending invitation tokens through the workspace member list. Attackers can redeem an exposed higher-privileged invitation token at signup to claim the invited account and escalate to roles such as workspace owner.

Who should check

Teams running self-hosted NocoDB community edition from 0.301.4 before 2026.10.0 that have workspace members and pending invitations.

“>= 0.301.4, < 2026.10.0”

github.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affects NocoDB versions >= 0.301.4 and < 2026.10.0. Community edition is affected; enterprise edition is not. An unexpired pending invitation for a higher role must exist in the workspace.
  • Upgrade to a fixed version: 2026.10.0.

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-130697 (NocoDB from 0.301.4 before 2026.10.0 Invitation Token Disclosure via Workspace Member List), 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-130697 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: from 0.301.4, fixed in 2026.10.0
Fixed versions: 2026.10.0.
Conditions (all must be true for the bug to be hit):
- Affects NocoDB versions >= 0.301.4 and < 2026.10.0. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hm8p-622v-9c6j)
- Community edition is affected; enterprise edition is not. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hm8p-622v-9c6j)
- An unexpired pending invitation for a higher role must exist in the workspace. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hm8p-622v-9c6j)
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-130697 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130697 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-hm8p-622v-9c6j
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-130697
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-130697"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • nocodb nocodb

    From 0.301.4 · fixed in 2026.10.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-hm8p-622v-9c6j
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130697
RecordNVD · CVE-2026-130697

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130697

Is CVE-2026-130697 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 workspace viewer can read pending invitation tokens from the workspace member list. The viewer can then redeem a higher-privileged invitation at signup and claim that account and role, including workspace owner. The bug is a privilege escalation that also exposes a secret.Source: github.com

Which versions are affected by CVE-2026-130697?

nocodb: from 0.301.4 before 2026.10.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions from 0.301.4 before 2026.10.0 are affected, and only the community edition; the enterprise edition is not. The setup also needs an unexpired pending invitation for a higher role in the workspace. Check the installed NocoDB version and edition to see which group the installation falls into.Source: github.com

How do I fix CVE-2026-130697?

Upgrade NocoDB to 2026.10.0 or later, which is the fixed version in the affected range.Source: github.com

More CVEs