CVE
NocoDB remote code execution via SQL injection in formula parser
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected NocoDB versions before 2026.10.0 (advisory lists patched version 2026.10.0). Attacker needs an account with the Creator or Owner role on a base. A base connected to a SQLite source that can open NocoDB's own metadata file, as on a default single-container install; the path guard bypass uses a filesystem alias. For operating-system command execution, a base backed by external PostgreSQL whose role may run server programs.
Summary
NocoDB before 2026.09.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to inject raw SQL by persisting a crafted formula parsed_tree reused without revalidation. Attackers can bypass the SQLite metadata path guard with an alias to plant the tree, escalating to super administrator or executing OS commands on external PostgreSQL hosts.
Who should check
Teams running NocoDB before 2026.10.0, especially those with Creator or Owner base roles, SQLite single-container installs, or external PostgreSQL sources.
“Affected versions < 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
- Severity10/10CVSS 9.4, 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.
Affected NocoDB versions before 2026.10.0 (advisory lists patched version 2026.10.0). Attacker needs an account with the Creator or Owner role on a base. A base connected to a SQLite source that can open NocoDB's own metadata file, as on a default single-container install; the path guard bypass uses a filesystem alias. For operating-system command execution, a base backed by external PostgreSQL whose role may run server programs.Upgrade to a fixed version: 2026.09.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-130706 (NocoDB before 2026.09.0 SQL Injection RCE via Formula Parsed Tree), 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-130706 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.09.0
Fixed versions: 2026.09.0.
Conditions (all must be true for the bug to be hit):
- Affected NocoDB versions before 2026.10.0 (advisory lists patched version 2026.10.0). (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-frqc-xh5h-rrcw)
- Attacker needs an account with the Creator or Owner role on a base. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-frqc-xh5h-rrcw)
- A base connected to a SQLite source that can open NocoDB's own metadata file, as on a default single-container install; the path guard bypass uses a filesystem alias. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-frqc-xh5h-rrcw)
- For operating-system command execution, a base backed by external PostgreSQL whose role may run server programs. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-frqc-xh5h-rrcw)
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-130706 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130706 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-frqc-xh5h-rrcw
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-130706
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-130706"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.09.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-frqc-xh5h-rrcw |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130706 |
| Record | NVD · CVE-2026-130706 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130706
Is CVE-2026-130706 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 flaw in NocoDB's formula parsed-tree handling allows SQL injection that can lead to remote code execution. Users with Creator or Owner rights on a base can read all user records, password hashes, API tokens and stored data-source credentials, and can make their own account instance super administrator on SQLite installs. On external PostgreSQL servers that allow server programs, they can run operating-system commands on the database host.Source: github.com
Which versions are affected by CVE-2026-130706?
nocodb: before 2026.09.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory says affected versions are those before 2026.10.0. The product record instead gives 2026.09.0 as the fixed version, so the exact boundary is unclear from the sources. The risk applies to bases where the attacker has a Creator or Owner role, especially default single-container installs that store metadata in SQLite, and to bases connected to external PostgreSQL where the role may run server programs. Check your NocoDB version in the admin settings or the image tag, and check the PostgreSQL role's server-program privileges.Source: github.com
How do I fix CVE-2026-130706?
Upgrade to NocoDB 2026.10.0, the patched version the advisory names. Because the product record lists 2026.09.0, confirm the fixed version with the vendor's advisory before relying on either number.Source: github.com