dbcve.org
NocobaseApplication

CVE-2026-34156

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 2.0.28 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.28, NocoBase's Workflow Script Node executes user-supplied JavaScript inside a Node.js vm sandbox with a custom require allowlist (controlled by WORKFLOW_SCRIPT_MODULES env var). However, the console object passed into the sandbox context exposes host-realm WritableWorkerStdio stream objects via console._stdout and console._stderr. An authenticated attacker can traverse the prototype chain to escape the sandbox and achieve Remote Code Execution as root. This issue has been patched in version 2.0.28.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 4mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NocoBase's Workflow Script Node executes user-supplied JavaScript in a Node.js vm sandbox, but the console object exposed to the sandbox context contains host-realm WritableWorkerStdio stream objects via console._stdout and console._stderr. Authenticated attackers can escape the sandbox through prototype chain traversal to achieve root-level Remote Code Execution. Patched in version 2.0.28.

MitigationUpgrade to NocoBase version 2.0.28 or later. Until then, restrict Workflow Script Node access to trusted users only and consider network segmentation as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NocobaseApplication
Affected:< 2.0.28

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NocoBase version
    Check the installed NocoBase version by examining package.json, the admin interface version display, or the nocobase --version CLI output if available
    Affected if version is below 2.0.28 (any version < 2.0.28 is affected)
  2. Verify Workflow plugin is enabled
    Check if the Workflows plugin/module is active in the NocoBase installation, typically via admin settings or configuration files
    Affected if Workflows are enabled and the Script Node type exists in the workflow builder
  3. Confirm Script Node availability
    Access the workflow editor and verify that a Script Node or similar code execution node type can be added to a workflow
    Affected if users with workflow creation permissions can add and configure Script Nodes
  4. Check for authenticated user access
    Determine if low-privilege authenticated users have permission to create or modify workflows containing Script Nodes
    Affected if authenticated users (even with limited roles) can access the workflow designer and create Script Nodes

You are affected if NocoBase version is below 2.0.28 AND the Workflow feature with Script Node capability is enabled for authenticated users in your environment

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.28 or later
Fixed in 2.0.28
Vendor patch github.com →
Interim mitigation

Upgrade to NocoBase version 2.0.28 or later. Until then, restrict Workflow Script Node access to trusted users only and consider network segmentation as a defense-in-depth measure.

Recommended fix High confidence

2.0.28

  1. 1. Identify the current Nocobase installation method (Docker, npm, or direct binary)
  2. 2. For Docker deployments: Stop the current container, then pull and run the Nocobase image version 2.0.28 (e.g., docker pull nocobase/server:2.0.28)
  3. 3. For npm/node installations: Run the package manager update command to upgrade Nocobase to version 2.0.28 (e.g., npm update @nocobase/server or yarn upgrade @nocobase/server)
  4. 4. If using a deployment manager or Kubernetes, update the deployment configuration to specify version 2.0.28 and apply the changes
  5. 5. Verify the upgrade was successful by checking the Nocobase version in the admin UI or via CLI
  6. 6. Test the Workflow Script Node functionality to ensure the sandbox properly restricts access and the vulnerability is mitigated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nocobase Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34156 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34156 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data