CVE
NocoDB SQL injection in select field option titles
Affects NocoDB sources running MySQL or MariaDB before 2026.10.1, where a base creator or owner can append SQL clauses to schema edits. Fixed in 2026.10.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.10.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB sources running MySQL or MariaDB; the advisory says PostgreSQL, SQLite and SQL Server are not affected. Affects the MySQL default sql_mode, where a backslash escapes the following character.
Summary
NocoDB before 2026.10.1 contains an SQL injection vulnerability because select-field option titles are embedded into MySQL or MariaDB enum/set column definitions with only single-quote doubling, leaving backslashes unescaped. A base creator or owner can end an option title with a backslash to escape the literal and append ALTER TABLE clauses, adding, dropping or renaming columns and altering indexes in the connected database.
Who should check
Teams running NocoDB before 2026.10.1 with MySQL or MariaDB sources; base creators and owners with schema-edit rights.
“On MySQL and MariaDB sources, select-field option titles are embedded into enum / set column”
cve.now Index
- 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 sources running MySQL or MariaDB; the advisory says PostgreSQL, SQLite and SQL Server are not affected. Affects the MySQL default sql_mode, where a backslash escapes the following character.Upgrade to a fixed version: 2026.10.1.
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-130701 (NocoDB before 2026.10.1 SQL Injection via Select Field Option Titles), 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-130701 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.1
Fixed versions: 2026.10.1.
Conditions (all must be true for the bug to be hit):
- NocoDB sources running MySQL or MariaDB; the advisory says PostgreSQL, SQLite and SQL Server are not affected. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-fx53-qf4h-cx38)
- Affects the MySQL default sql_mode, where a backslash escapes the following character. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-fx53-qf4h-cx38)
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-130701 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130701 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-fx53-qf4h-cx38
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-130701
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-130701"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.10.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-fx53-qf4h-cx38 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130701 |
| Record | NVD · CVE-2026-130701 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130701
Is CVE-2026-130701 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 schema-edit rights on a base, such as a base creator or owner, can append arbitrary SQL clauses to the ALTER TABLE statement NocoDB generates for the connected MySQL or MariaDB database. These clauses can add, drop or rename columns and alter indexes.Source: github.com
Which versions are affected by CVE-2026-130701?
nocodb: before 2026.10.1.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.10.1 with MySQL or MariaDB sources are affected, according to the advisory. The advisory says PostgreSQL, SQLite and SQL Server are not affected, and the issue arises under MySQL's default sql_mode, where a backslash escapes the following character. To check a setup, look at the database type of the NocoDB source and the MySQL sql_mode setting.Source: github.com
How do I fix CVE-2026-130701?
Upgrade NocoDB to 2026.10.1 or later, which is the fixed version in the product range data.Source: github.com