CVE-2026-73483

Description

Flowise (packages flowise and flowise-components) in versions <= 3.1.2 contain a sandbox escape in the vm2/@flowiseai/nodevm JavaScript sandbox. An authenticated user with access to the /api/v1/node-custom-function endpoint can escape the sandbox by supplying attacker-controlled executablePath and args parameters to puppeteer.launch(), which internally invokes child_process.spawn() outside the sandbox boundary. This allows execution of arbitrary OS commands as the Flowise process user (root in the official Docker image) and arbitrary host file disclosure via Chromium's file:// URL handling. In versions 3.0.8–3.1.2 exploitation requires ALLOW_BUILTIN_DEP=true; earlier versions are exploitable by default. Fixed in 3.1.3.

Severity
HIGH
CVSS v3
8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · source nvd
CVSS v4
9.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · source cna
Exploit chance (EPSS)
0.621%
chance of exploitation in the next 30 days
higher than 50.4% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableyes
Technical impacttotal
Scored2026-08-14

Timeline

  1. 2026-08-13Published by the CNA11:28 UTC
  2. 2026-08-14CISA SSVC decision recorded1 day after publication
  3. 2026-10-07GitHub advisory published (GHSA-9gvv-qjj3-2p6g)55 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-9gvv-qjj3-2p6g, affected packages:

PackageVulnerable versionsFixed in
npm flowisebefore 3.1.33.1.3
npm flowise-componentsbefore 3.1.33.1.3

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
flowiseai flowisebefore 3.1.3fixed in 3.1.3through 3.1.2no fix listed3.1.3not listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources