CVE-2026-41640
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 1.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.9% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.9% · EPSS, next 30 days
- Weakness
- CWE-89 · SQL injection
- Record status
- Analyzed
Affected
- Nocobase < 2.0.39
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-41640.md and follow it. Check whether this project is affected by CVE-2026-41640. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/nocobase/nocobase/commit/202e2b8efe44ba90adbf1087f6f70881ff947604
- https://github.com/nocobase/nocobase/pull/9133
- https://github.com/nocobase/nocobase/releases/tag/v2.0.39
- https://github.com/nocobase/nocobase/security/advisories/GHSA-4948-f92q-f432
- https://github.com/nocobase/nocobase/security/advisories/GHSA-4948-f92q-f432
References
- https://github.com/nocobase/nocobase/commit/202e2b8efe44ba90adbf1087f6f70881ff947604
- https://github.com/nocobase/nocobase/pull/9133
- https://github.com/nocobase/nocobase/releases/tag/v2.0.39
- https://github.com/nocobase/nocobase/security/advisories/GHSA-4948-f92q-f432
- https://github.com/nocobase/nocobase/security/advisories/GHSA-4948-f92q-f432