CVE-2026-130706 is a critical SQL injection flaw in NocoDB versions before 2026.09.0. An authenticated Creator or Owner user can use it to inject raw SQL, escalate to super administrator, or run OS commands on external PostgreSQL hosts.
What Is It
The flaw is in how NocoDB handles formula parsed_tree data. An authenticated user with the Creator or Owner role can save a crafted formula parsed_tree. NocoDB later reuses that tree without validating it again, which lets raw SQL reach the database.
The NVD description also says attackers can get past the SQLite metadata path guard by using an alias to plant the malicious tree. The weakness is classified as CWE-89 (SQL Injection). The CVE was published on November 18, 2026, by VulnCheck as the CNA. NVD lists its status as "Received."
Why It Matters
VulnCheck rates the flaw 9.1 CRITICAL under CVSS 3.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) and 9.4 CRITICAL under CVSS 4.0. The attack works over the network, is low in complexity, and needs no user interaction. The CVSS 3.1 scope is "Changed," so the impact reaches beyond NocoDB itself.
The attack requires high privileges (Creator or Owner), but the possible outcomes are severe:
- Escalation to super administrator inside NocoDB
- Execution of OS commands on external PostgreSQL hosts that NocoDB connects to
CISA's SSVC assessment rates the technical impact as total. It records exploitation as none and automatable as no.
CVE-2026-130706 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. The supplied data shows no confirmed active exploitation and no KEV-mandated required action or due date.
What's Vulnerable
- Vendor: nocodb
- Product: nocodb
- Affected: all versions before 2026.09.0
- Not affected: 2026.09.0
The risk is highest where many users hold Creator or Owner roles, and where NocoDB connects to external PostgreSQL databases, since that is where OS command execution becomes possible.
Patch Status
The affected-version data lists NocoDB 2026.09.0 as not affected. Upgrade to 2026.09.0 or later. NocoDB's GitHub security advisory (GHSA-frqc-xh5h-rrcw) is the vendor reference for this issue.
Until you can patch, check which accounts hold Creator or Owner roles. In this case those roles are effectively a path to super administrator.