On this page

Atomicorp WAF Research Note: CVE-2026-73483

Flowise before 3.1.3 Sandbox Escape via Puppeteer

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-73483
  • Name: Flowise before 3.1.3 Sandbox Escape via Puppeteer
  • Severity: Critical
  • CVSS: 9.4 (v4.0) (Critical)
  • CVSS version: 4.0
  • CVSS source: VulnCheck CNA
  • CVSS vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    • Attack vector: Network
    • Attack complexity: Low
    • Attack requirements: None
    • Privileges required: Low
    • User interaction: None
    • Vulnerable-system confidentiality: High
    • Vulnerable-system integrity: High
    • Vulnerable-system availability: High
    • Subsequent-system confidentiality: High
    • Subsequent-system integrity: High
    • Subsequent-system availability: High
    • Scope: X
  • CWE: CWE-78 — Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-108 (opens in a new tab) , CAPEC-15 (opens in a new tab) , CAPEC-43 (opens in a new tab) , CAPEC-6 (opens in a new tab) , CAPEC-88 (opens in a new tab)
  • Vendor: flowiseai
  • Vulnerable product: flowise
  • CVE published: 2026-08-13
  • CVE last modified: 2026-09-03
  • Affected versions (NVD configurations):
    • flowise: <= 3.1.2
  • EPSS: 0.0062; 47.8th percentile (FIRST (opens in a new tab) )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
  • Matching rules: 10; rules with blocking actions: 10
  • Would-block Rule IDs: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data
Technical CPE data

This section lists vulnerable CPE matches retained from the NVD configurations. It supplements the readable affected-product information above.

  • cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
    • Version end (inclusive): 3.1.2
    • NVD match criteria ID: 4161D3F2-D78A-4305-A85F-2851D7704224

Vulnerability 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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: FlowiseAI Flowise versions earlier than 3.1.3.
    • Versions reported unaffected: FlowiseAI Flowise version 3.1.3.
    • Recommended upgrade: Upgrade FlowiseAI Flowise to 3.1.3 or later.
    • The CVE record does not include written upgrade or workaround instructions, but it does publish the following patch or mitigation reference:
  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .