Skip to main content
Menu
CVEs

CVE

NocoDB SQL injection in MySQL and SQLite column precision

Affects NocoDB before 2026.07.0 where the base data source uses the MySQL or SQLite client and the attacker holds the Creator or Owner base role. Fixed in 2026.07.0.

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

7.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.07.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Base data source uses the MySQL or SQLite client Attacker holds the Creator or Owner base role

Summary

NocoDB before 2026.07.0 contains an SQL injection vulnerability in its MySQL and SQLite clients that inserts the column precision value into generated data-definition statements without numeric validation. Authenticated users with the Creator or Owner base role can supply a crafted precision value when creating or updating a column to close the type declaration and execute arbitrary SQL against the base's data source.

Who should check

Teams running NocoDB before 2026.07.0 with MySQL or SQLite base data sources, where users hold the Creator or Owner base role.

“On the MySQL and SQLite clients”

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/10CVSS 7.0
  • 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.

    Base data source uses the MySQL or SQLite client Attacker holds the Creator or Owner base role
  • Upgrade to a fixed version: 2026.07.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-130726 (NocoDB before 2026.07.0 SQL Injection via Column Precision Value), 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-130726 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.07.0
Fixed versions: 2026.07.0.
Conditions (all must be true for the bug to be hit):
- Base data source uses the MySQL or SQLite client (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xj66-9p6m-wr56)
- Attacker holds the Creator or Owner base role (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xj66-9p6m-wr56)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130726 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130726 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-xj66-9p6m-wr56
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-130726
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-130726"}.

Timeline

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

Affected versions

  • nocodb nocodb

    fixed in 2026.07.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-xj66-9p6m-wr56
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130726
RecordNVD · CVE-2026-130726

Corrections

None so far.

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

Questions about CVE-2026-130726

Is CVE-2026-130726 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 can change a table's schema can inject SQL through a column precision value. That can run arbitrary statements against the base's data source, including data-definition and data-manipulation statements, well beyond the column change the API exposes.Source: github.com

Which versions are affected by CVE-2026-130726?

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

Am I affected, and how do I check?

NocoDB versions before 2026.07.0 are affected, but only where the base's data source uses the MySQL or SQLite client and the user holds the Creator or Owner base role. To check, compare the NocoDB version you run with 2026.07.0 and look at the client type of the base's data source.Source: github.com

How do I fix CVE-2026-130726?

Upgrade NocoDB to 2026.07.0 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs