CVE-2026-73483
Sandbox escape in Flowise allows OS command execution as the Flowise process user.
Is CVE-2026-73483 being exploited?
Not confirmed. CVE-2026-73483 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-73483?
CVE-2026-73483 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73483?
Yes. A fix has been recorded for CVE-2026-73483. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73483 affect?
CVE-2026-73483 affects Flowise <= 3.1.2, flowise package, flowise-components, vm2/@flowiseai/nodevm, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73483?
Upgrade to Flowise 3.1.3 immediately; if unable, block /api/v1/node-custom-function and set ALLOW_BUILTIN_DEP=false.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can escape vm2 sandbox via puppeteer.launch to execute arbitrary OS commands (RCE) and read host files; official Docker runs as root.
Immediate action required
- affected< 3.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.