SQL Injection in @nocobase/database (CVE-2026-41640)
Summary
SQL injection in @nocobase/database (CVE-2026-41640). Successful exploitation can lead to full system takeover. Exploitable via nodeIds. Mitigation: upgrade to 2.0.39 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41640 has been found in @nocobase/database.
Attackers can target a specific entry point like nodeIds over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade @nocobase/database to 2.0.39 or later.
If unsure, ask your IT team or search "@nocobase/database CVE-2026-41640" on the vendor's site.
CVE-2026-41640 (@nocobase/database) — CWE-89 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: nodeIds / BelongsTo / WHERE / nocobase
Patched: 2.0.39 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in @nocobase/database. Attackers reach the vulnerable code path via nodeIds.
Check the vendor advisory for the affected versions of @nocobase/database. Attack surface: nodeIds / BelongsTo / WHERE / nocobase.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 2.0.39.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@nocobase/database' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@nocobase/database' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@nocobase/databaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @nocobase/database to 2.0.39ステージング環境で 2.0.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com