Skip to main content
Menu
CVEs

CVE

NocoDB account takeover via shared invitation token

Only affects NocoDB versions before 2026.05.3 where users were invited in the same batch invitation. Fixed in 2026.05.3.

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

7.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.05.3
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Target account was created in the same batch invitation as the attacker's invite (organisation, base or workspace invite).

Summary

NocoDB before 2026.05.3 contains an account takeover vulnerability that allows invited users to complete other invitees' signups because batch invitations share one token across all recipients. Attackers holding a valid batch invite can submit another invitee's email with the shared non-expiring token to set its password and take over that account, including higher-role ones.

Who should check

Teams running NocoDB before 2026.05.3 that send batch invitations to organisations, bases or workspaces, including enterprise deployments.

“Affected versions < 2026.05.3”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 7.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Target account was created in the same batch invitation as the attacker's invite (organisation, base or workspace invite).
  • Upgrade to a fixed version: 2026.05.3.

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-130731 (NocoDB before 2026.05.3 Account Takeover via Shared Invitation Token), 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-130731 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.05.3
Fixed versions: 2026.05.3.
Conditions (all must be true for the bug to be hit):
- Target account was created in the same batch invitation as the attacker's invite (organisation, base or workspace invite). (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-cx2g-25mq-67cf)
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-130731 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130731 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-cx2g-25mq-67cf
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-130731
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-130731"}.

Timeline

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

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

  4. Record last updated

Affected versions

  • nocodb nocodb

    fixed in 2026.05.3

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-cx2g-25mq-67cf
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130731
RecordNVD · CVE-2026-130731

Corrections

None so far.

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

Questions about CVE-2026-130731

Is CVE-2026-130731 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 who received one invitation could take over the pending account of another user invited in the same batch, including higher-role accounts, by completing signup and setting its password.Source: github.com

Which versions are affected by CVE-2026-130731?

nocodb: before 2026.05.3.Source: cve.now feed data

Am I affected, and how do I check?

NocoDB versions before 2026.05.3 are affected, but only where the target account was created in the same batch invitation as the other invite (organisation, base or workspace invite). To check, look at the NocoDB version in use and whether any accounts were invited together in one batch.Source: github.com

How do I fix CVE-2026-130731?

Upgrade NocoDB to 2026.05.3 or later, which is the listed fixed version.Source: github.com

More CVEs