CVE-2026-69263
Flowise <3.1.3 allows npx auto-install leading to arbitrary code execution.
Is CVE-2026-69263 being exploited?
Not confirmed. CVE-2026-69263 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-69263?
CVE-2026-69263 is rated High with a CVSS score of 8.7. 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-69263?
Yes. A fix has been recorded for CVE-2026-69263. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69263 affect?
CVE-2026-69263 affects Flowise < 3.1.3, Node.js environments running Flowise, Custom MCP server feature. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69263?
Upgrade Flowise to v3.1.3 and audit npm_config_* env vars.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution: npx can auto-install and run attacker-controlled packages when a Custom MCP server launches, enabling remote code execution and supply-chain compromise.
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.