← Back
CVE-2026-41640
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SQL injection** (CWE-89) exists in @nocobase/database. Attackers reach the vulnerable code path via ``nodeIds`` without authentication.
📍 Affected scope
@nocobase/database — . Attack surface: `nodeIds` / `BelongsTo` / `WHERE` / `nocobase`.
🔥 Severity
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.0.39**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @nocobase/database to 2.0.39ステージング環境で 2.0.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@nocobase/database
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.39"}]}]