# CVE-2026-41640: NocoBase Vulnerable to SQL Injection via String Concatenation in Recursive Eager Loading

> Attackers can inject arbitrary SQL via malicious primary keys in NocoBase, potentially leading to code execution or data theft.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-4948-f92q-f432

## What is CVE-2026-41640?

CVE-2026-41640 is a high-severity SQL injection vulnerability in nocobase, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the queryParentSQL() function in the core database package constructs a recursive CTE query by joining nodeIds with string concatenation instead of using parameterized queries. The nodeIds array contains primary key values read from database rows. An attacker who can create a record with a malicious string primary key can inject arbitrary SQL when any subsequent request triggers recursive eager loading on that collection. This issue has been patched in version 2.0.39.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-41640?

2 open source packages ship an affected version, including @nocobase/database. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nocobase/database` | npm | All versions | 2.0.39 |
| `@nocobase/database` | npm | All versions | 2.0.39 |

Products: Nocobase Nocobase.

## How do I fix CVE-2026-41640?

Upgrade @nocobase/database to 2.0.39 or later.

## Is CVE-2026-41640 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41640 exists.

Public exploit code:

- NocoBase - SQL Injection (nuclei): http/cves/2026/CVE-2026-41640.yaml

## Other vulnerabilities in nocobase

- [CVE-2026-34156](https://insights.sbomify.com/CVE-2026-34156/): NocoBase Affected by Sandbox Escape to RCE via console._stdout Prototype Chain Traversal in Workflow Script Node (critical 10.0)
- [CVE-2026-34825](https://insights.sbomify.com/CVE-2026-34825/): NocoBase Has SQL Injection via template variable substitution in workflow SQL node (high 8.5)
- [CVE-2026-41641](https://insights.sbomify.com/CVE-2026-41641/): NocoBase Vulnerable to SQL Validation Bypass via `sqlCollection:update` Missing `checkSQL` Call (high 7.2)
- [CVE-2026-40346](https://insights.sbomify.com/CVE-2026-40346/): NocoBase has SSRF in Workflow HTTP Request and Custom Request Plugins (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41640 and fix it if it is affected.

What it is: CVE-2026-41640 is a high-severity SQL injection vulnerability in nocobase, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41640 exists.

Affected packages and fixed versions:
- @nocobase/database (npm): affected all versions; fixed in 2.0.39
- @nocobase/database (npm): affected all versions; fixed in 2.0.39

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41640/ (Markdown: https://insights.sbomify.com/CVE-2026-41640/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41640
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41640
- OSV: https://osv.dev/vulnerability/CVE-2026-41640

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41640/
Summaries are generated and may contain mistakes; the official description above is the record.