CVE-2026-34825

NocoBase Has SQL Injection via template variable substitution in workflow SQL node

Full database read/write access through SQL injection. An attacker who can trigger a workflow with a SQL node containing template variables from user-controlled data can extract credentials, modify records, or drop tables. The severity depends on the database user's privileges (full superuser access in the default Docker deployment).

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-34825 has a CVSS score of 6.5 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.30); upgrading removes the vulnerable code path.

Kodem intelligence

Use parameterized queries. Replace direct string substitution with Sequelize bind parameters:

// SQLInstruction.ts
- const sql = processor.getParsedValue(node.config.sql || '', node.id).trim();
+ const { sql, bind } = processor.getParsedValueAsParams(node.config.sql || '', node.id);
  const [result] = await collectionManager.db.sequelize.query(sql, {
+   bind,
    transaction: ...
  });

1. What is CVE-2026-34825? CVE-2026-34825 is a high-severity SQL injection vulnerability in @nocobase/plugin-workflow-sql (npm), affecting versions <= 2.0.29. It is fixed in 2.0.30. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-34825? CVE-2026-34825 has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @nocobase/plugin-workflow-sql are affected by CVE-2026-34825? @nocobase/plugin-workflow-sql (npm) versions <= 2.0.29 is affected.
4. Is there a fix for CVE-2026-34825? Yes. CVE-2026-34825 is fixed in 2.0.30. Upgrade to this version or later.
5. Is CVE-2026-34825 exploitable, and should I be worried? Whether CVE-2026-34825 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-34825 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-34825? Upgrade @nocobase/plugin-workflow-sql to 2.0.30 or later.