CVE
NocoDB SQL injection in formula parsed tree operator
Affects NocoDB before 2026.10.0, with greater impact on single-container installs that keep metadata in SQLite. The vendor gives no separate rating, and the fix is 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. NocoDB versions before 2026.10.0 Attacker must hold the Creator role on a base, needed to create a table or add a formula column Greater impact when metadata is held in SQLite on a single-container install
Summary
NocoDB before 2026.10.0 contains an sql injection vulnerability that allows authenticated users with the Creator role to inject SQL by supplying a crafted formula parsed_tree during table creation. Attackers can set a malicious binary-expression operator that is interpolated into a knex.raw fragment, reading user and token tables and escalating to super administrator on SQLite installs.
Who should check
Teams running NocoDB before 2026.10.0, especially those with Creator-role users or single-container installs using SQLite metadata; also any stack using NocoDB data 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
- Severity9.7/10CVSS 8.7, 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.
NocoDB versions before 2026.10.0 Attacker must hold the Creator role on a base, needed to create a table or add a formula column Greater impact when metadata is held in SQLite on a single-container installUpgrade 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-130689 (NocoDB before 2026.10.0 SQL Injection via Formula Parsed Tree Operator), 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-130689 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.0
Fixed versions: 2026.10.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.10.0 (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-f33g-c5jc-jvr3)
- Attacker must hold the Creator role on a base, needed to create a table or add a formula column (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-f33g-c5jc-jvr3)
- Greater impact when metadata is held in SQLite on a single-container install (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-f33g-c5jc-jvr3)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130689 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130689 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-f33g-c5jc-jvr3
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-130689
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-130689"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.10.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-f33g-c5jc-jvr3 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130689 |
| Record | NVD · CVE-2026-130689 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130689
Is CVE-2026-130689 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 the Creator role can inject SQL through a formula column's parsed tree operator. The injected SQL runs with the privileges of the base's data-source connection, so it can read and modify connected data. On installs whose metadata is held in SQLite, it can also expose every user record and token and grant the super administrator role.Source: github.com
Which versions are affected by CVE-2026-130689?
nocodb: before 2026.10.0.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.10.0 are affected. The attacker needs an account with the Creator role on a base, which is required to create a table or add a formula column. Impact is greater on a single-container install whose metadata is in the same SQLite database; check the installed version and where metadata is stored to see which case applies.Source: github.com
How do I fix CVE-2026-130689?
Upgrade NocoDB to 2026.10.0 or later, which is the fixed version listed for this vulnerability.Source: github.com