Skip to main content
Menu
CVEs

CVE

NocoDB authorization bypass in batch API for read-only sources

Affects NocoDB 2026.06.2 up to but not including 2026.08.0 when a base has a data-read-only source and a writable source on the same base. Fixed in 2026.08.0.

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

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.08.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. NocoDB versions 2026.06.2 up to but not including 2026.08.0 A data-read-only source must be configured in the base and the attacker needs a writable source table on the same envelope

Summary

NocoDB from 2026.06.2 before 2026.08.0 contains an authorization bypass vulnerability that allows authenticated base Editors to write to data-read-only sources by abusing the internal batch endpoint. Attackers can name a writable decoy table on the batch envelope and target a read-only source table in dataUpdate, dataInsert or dataDelete sub-operations to modify or destroy records.

Who should check

Teams running NocoDB 2026.06.2 up to 2026.08.0 that have base Editors and read-only data sources attached to bases

“Affected versions >= 2026.06.2, < 2026.08.0”

github.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • 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.

    NocoDB versions 2026.06.2 up to but not including 2026.08.0 A data-read-only source must be configured in the base and the attacker needs a writable source table on the same envelope
  • Upgrade to a fixed version: 2026.08.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-130721 (NocoDB 2026.06.2 before 2026.08.0 Read-Only Source Bypass via Internal Batch API), 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-130721 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: from 2026.06.2, fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions 2026.06.2 up to but not including 2026.08.0 (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-q742-6g25-cvm9)
- A data-read-only source must be configured in the base and the attacker needs a writable source table on the same envelope (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-q742-6g25-cvm9)
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-130721 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130721 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-q742-6g25-cvm9
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-130721
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-130721"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • nocodb nocodb

    From 2026.06.2 · fixed in 2026.08.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-q742-6g25-cvm9
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130721
RecordNVD · CVE-2026-130721

Corrections

None so far.

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

Questions about CVE-2026-130721

Is CVE-2026-130721 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?

An authenticated base Editor can insert, update, move or delete records in a source the base owner configured as data-read-only. This works by naming a table from a writable source inside a dataUpdate, dataInsert or dataDelete sub-operation of the internal batch API.Source: github.com

Which versions are affected by CVE-2026-130721?

nocodb: from 2026.06.2 before 2026.08.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions from 2026.06.2 up to but not including 2026.08.0 are in range, and the setup needs a base with a data-read-only source plus a writable source on the same base. To check, look at the NocoDB version in your installation and at whether any base has a source set to data-read-only.Source: github.com

How do I fix CVE-2026-130721?

Upgrade NocoDB to 2026.08.0 or later, which is the first version outside the affected range. The checked facts name no vendor patch ids or workaround.Source: github.com

More CVEs