CVE-2026-73483

COMPONENT VERSION RANGE

NewScan fingerprints Flowise from its response and reports this CVE when the detected version falls inside the affected range below.

ONE row for the whole 2026-08-13 Flowise batch, same call as the Bouncy Castle row: every id here is closed by upgrading once, so nine rows would mean nine findings that all read 'upgrade to 3.1.4'. CVE-2026-73483 (9.4) names it - a vm2/@flowiseai/nodevm sandbox escape reachable by any user who can edit a flow. Also covers, all fixed in 3.1.3: CVE-2026-73485 and CVE-2026-73487 (9.0, UNAUTHENTICATED Python code execution through the Airtable/CSV Agent nodes, 73487 by defeating the regex validator via prompt injection), CVE-2026-73486 (9.0, CSV Agent customReadCSV), CVE-2026-73601 (9.0, Custom MCP node with CUSTOM_MCP_PROTOCOL=stdio), CVE-2026-73602 (9.0, second vm2 escape via moment locale values), CVE-2026-73604 (7.1, GET /api/v1/credentials/:id returns decrypted secrets), CVE-2026-73488 (6.0, IDOR on /api/v1/organization/customer-default-source); and CVE-2026-73603 (6.3, unauthenticated text-to-speech endpoint abusing private-chatflow TTS credentials), which is the one that needs 3.1.4 rather than 3.1.3 and is why the gate is lt 3.1.4. No `ge`: the vm2 sandbox and the agent nodes predate every release in range. VERSION SOURCE is the tech_signatures Flowise row's version_from - the <title>Flowise - Low-code LLM apps builder</title> proves the product, then /api/v1/version answers a bare version document - and it was re-measured 2026-08-13 against flowiseai/flowise:2.2.7 on loopback: title matched, /api/v1/version -> 2.2.7, and 2.2.7 < 3.1.4 -> this row fires with the real number as evidence. The negative case is matcher-level only (version_in_range 3.1.4 -> no hit): flowiseai/flowise:3.1.4 does not boot in this environment at all, with or without a data volume - its enterprise session middleware throws 'TypeError: this.db.exec is not a function' out of connect-sqlite3 before the HTTP listener opens - so no live patched build could be probed. NOT an interfaces row either, and that was measured too: a stock 2.2.7 with no credentials configured answers 401 Unauthorized Access on /api/v1/chatflows, /api/v1/credentials, /api/v1/nodes, /api/v1/variables and /api/v1/settings. Only /api/v1/version and /api/v1/ping are anonymous, so an 'unauthenticated Flowise console' row would have nothing to fire on - the version gate is the whole reachable claim.