NPM · MAY 2026 · EARLY WARNING

Flowise npm Package RCE Vulnerability Under Investigation

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-9RVC-VF7M-PGM2Severity: CRITICAL

An early warning has been issued regarding a critical vulnerability in the Flowise npm package, which reportedly allows authenticated users to execute arbitrary JavaScript, leading to potential remote code execution on the server host.

What happened

The vulnerability, tracked as GHSA-9RVC-VF7M-PGM2, appears to enable authenticated users to submit arbitrary JavaScript through the POST /api/v1/node-custom-function endpoint. This can lead to remote code execution on the server host due to an escape of the NodeVM sandbox, allowing system command execution.

Professional software engineers using Flowise are advised to upgrade to the latest version that patches this vulnerability. Additionally, it is recommended to review any custom JavaScript executions within their applications to assess potential exposure.

The primary source for this vulnerability is the GitHub Advisory Database, which provides further details on the reported authenticated host RCE and NodeVM sandbox escape. For the most accurate and up-to-date information, consult the primary sources directly.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If flowise is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats