CVE-2026-73602
Authenticated vm2 sandbox escape in Flowise allows arbitrary code execution on host.
Is CVE-2026-73602 being exploited?
Not confirmed. CVE-2026-73602 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.84% probability of exploitation in the next 30 days.
How severe is CVE-2026-73602?
CVE-2026-73602 is rated Critical with a CVSS score of 9.0. 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-73602?
Yes. A fix has been recorded for CVE-2026-73602. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73602 affect?
CVE-2026-73602 affects Flowise < 3.1.3, Self-hosted Flowise instances, vm2 JavaScript sandbox. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73602?
Upgrade Flowise to >=3.1.3, restrict UI access, audit logs and credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can escape vm2 sandbox, load/execute arbitrary JavaScript, access filesystem and run code on the host.
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.