CVE-2026-41640: nocobase · SQL Injection
Affects nocobaseSource GCVE Database
Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 2.0.39 soon.
Data as of 27 Oct 2026, 02:46 UTC
- Patch
- Available – fixed in 2.0.39
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 May 2026
Detectable: evidence found.
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade nocobase to 2.0.39.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nocobase nocobase | Affected
| Fixed in
|
AI-suggested
Upgrade NocoBase to version 2.0.39 or later, where the vulnerability is fixed by using parameterized queries in the queryParentSQL() function. No other mitigations are indicated by the vendor advisory.
Description
NocoBase versions prior to 2.0.39 contain a SQL injection vulnerability in the queryParentSQL() function due to unsafe string concatenation of primary key values in recursive CTE queries. This allows an attacker who can create a record with a malicious string primary key to inject arbitrary SQL during recursive eager loading. The issue is fixed in version 2.0.39.
References
- github.com/nocobase/nocobase/security/advisories/GHSA-4948-f92q-f432 (opens in a new tab)
- github.com/nocobase/nocobase/pull/9133 (opens in a new tab)
- github.com/nocobase/nocobase/commit/202e2b8efe44ba90adbf1087f6f70881ff947604 (opens in a new tab)
- github.com/nocobase/nocobase/releases/tag/v2.0.39 (opens in a new tab)