Skip to main content
Menu
CVEs

CVE

NocoDB account takeover via base invitation resend

Affects NocoDB before 2026.10.0 where a user holds the base creator role in a shared base and email authentication is enabled, the default. Fixed in 2026.10.0.

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

8.7HighCNA
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. Attacker must hold the base creator role in a shared base Email authentication is enabled (the default); deployments without a mail plugin still commit the token but the call errors

Summary

NocoDB before 2026.10.0 contains an account takeover vulnerability that allows users with the base creator role to hijack other accounts by resending base invitations. Attackers can trigger baseUserInviteResend to mint a new invite_token, read it from the base member list, and reset the victim's password through signup, taking over owner or super admin accounts.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • 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.

    Attacker must hold the base creator role in a shared base Email authentication is enabled (the default); deployments without a mail plugin still commit the token but the call errors
  • 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-130702 (NocoDB before 2026.10.0 Account Takeover via Base Invitation Resend), 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-130702 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.0
Fixed versions: 2026.10.0.
Conditions (all must be true for the bug to be hit):
- Attacker must hold the base creator role in a shared base (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-mf7h-mwxr-38r5)
- Email authentication is enabled (the default); deployments without a mail plugin still commit the token but the call errors (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-mf7h-mwxr-38r5)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130702 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130702 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-mf7h-mwxr-38r5
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-130702
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-130702"}.

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.10.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-mf7h-mwxr-38r5
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130702
RecordNVD · CVE-2026-130702

Corrections

None so far.

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

Questions about CVE-2026-130702

Is CVE-2026-130702 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 base creator role in a shared base can take over another member's global NocoDB account by abusing base invitation resend. The victim's password is replaced, so they are locked out. Targeting a base owner, workspace owner or super admin gives broad administrative, data-export, membership and deletion authority.Source: github.com

Which versions are affected by CVE-2026-130702?

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

Am I affected, and how do I check?

NocoDB versions before 2026.10.0 are affected. The exposed setup requires email authentication, which is enabled by default, and a user holding the base creator role in a shared base. Deployments without a mail plugin still commit the token, but the call errors. To check, compare the NocoDB version in use with 2026.10.0 and review the email authentication setting.Source: github.com

How do I fix CVE-2026-130702?

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

More CVEs