CVE
NocoDB SQL injection in DATETIME_FORMAT formula
Affects NocoDB 2026.07.0 before 2026.10.0 on bases whose MySQL or MariaDB data source uses the DATETIME_FORMAT formula. The vendor gives no separate rating, and CVSS scores it High. Fixed in 2026.10.0.
- 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. Affected versions are 2026.07.0 up to but not including 2026.10.0. The base's data source is MySQL or MariaDB, using the DATETIME_FORMAT formula function. MySQL servers running with NO_BACKSLASH_ESCAPES are not affected.
Summary
NocoDB from 2026.07.0 before 2026.10.0 contains an sql injection vulnerability that allows users with Creator role to inject SQL through unescaped backslashes in the DATETIME_FORMAT formula format argument on MySQL-backed bases. Attackers can place a backslash before a quote to terminate the DATE_FORMAT string literal and read any data reachable by the data source's database user, including tables outside the base.
Who should check
Teams running NocoDB 2026.07.0 through 2026.9.x with bases backed by MySQL or MariaDB, where users can add or edit formula fields (Creator role).
“Affected versions >= 2026.07.0, < 2026.10.0”
cve.now Index
- Exploitation0/40No signal
- 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.
Affected versions are 2026.07.0 up to but not including 2026.10.0. The base's data source is MySQL or MariaDB, using the DATETIME_FORMAT formula function. MySQL servers running with NO_BACKSLASH_ESCAPES are not affected.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-130694 (NocoDB 2026.07.0 before 2026.10.0 SQL Injection via DATETIME_FORMAT Formula), 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-130694 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: from 2026.07.0, fixed in 2026.10.0
Fixed versions: 2026.10.0.
Conditions (all must be true for the bug to be hit):
- Affected versions are 2026.07.0 up to but not including 2026.10.0. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-2ggp-wwhj-f84q)
- The base's data source is MySQL or MariaDB, using the DATETIME_FORMAT formula function. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-2ggp-wwhj-f84q)
- MySQL servers running with NO_BACKSLASH_ESCAPES are not affected. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-2ggp-wwhj-f84q)
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-130694 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130694 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-2ggp-wwhj-f84q
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-130694
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-130694"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nocodb nocodb
From 2026.07.0 · fixed in 2026.10.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-2ggp-wwhj-f84q |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130694 |
| Record | NVD · CVE-2026-130694 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130694
Is CVE-2026-130694 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 add or edit fields on a base can insert SQL through the DATETIME_FORMAT formula. That SQL runs as the data source's database user, so it can read any data that user can reach, including tables outside the base, and can slow the database server.Source: github.com
Which versions are affected by CVE-2026-130694?
nocodb: from 2026.07.0 before 2026.10.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 2026.07.0 up to but not including 2026.10.0 are affected, and only when the base's data source is MySQL or MariaDB and the DATETIME_FORMAT formula is used. MySQL servers running with NO_BACKSLASH_ESCAPES were not affected. To check, look at the NocoDB version and the data source type of the base, and for MySQL the sql_mode setting for NO_BACKSLASH_ESCAPES.Source: github.com
How do I fix CVE-2026-130694?
Upgrade NocoDB to 2026.10.0, the first fixed version, or later.Source: github.com