Skip to content
AI/ML

CVE-2026-73486

9.0
Critical
EPSS 0.68%Patch availableAug 13, 2026

Authenticated code injection in Flowise CSV Agent allows arbitrary Python execution.

common questions

Is CVE-2026-73486 being exploited?

Not confirmed. CVE-2026-73486 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.68% probability of exploitation in the next 30 days.

How severe is CVE-2026-73486?

CVE-2026-73486 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-73486?

Yes. A fix has been recorded for CVE-2026-73486. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73486 affect?

CVE-2026-73486 affects Flowise < 3.1.3, Flowise CSV Agent node (customReadCSV), pyodide environment (unsandboxed). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73486?

Upgrade to Flowise 3.1.3+, disable/remove untrusted CSV agents, audit deployments.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Flowise < 3.1.3Flowise CSV Agent node (customReadCSV)pyodide environment (unsandboxed)
impact

Authenticated code injection via CSV Agent customReadCSV lets attackers run arbitrary Python in unsandboxed pyodide, enabling full system access and data compromise.

action required

Immediate action required

affected versions
FlowiseAI Flowise
  • affected< 3.1.3
vendor says fixed in3.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free