Loading vulnerability…
CVE-2024-36420 affects Flowise version 1.4.3, a drag-and-drop interface for building customized large language model flows. The vulnerability is in the /api/v1/openai-assistants-file endpoint implemented in index.ts, where the fileName body parameter is not properly sanitized. An attacker can supply a crafted filename or path traversal sequence to cause the application to read arbitrary files from the underlying filesystem.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
/api/v1/openai-assistants-file endpoint where possible, place Flowise behind strong authentication and network access controls, run the service with least-privilege filesystem permissions, avoid storing sensitive material on the same host or in readable paths, and monitor for suspicious requests containing traversal patterns or unexpected filenames.Patch, then assume compromise.
fileName parameter, restrict access to an allowlisted directory, and reject path traversal sequences and absolute paths.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.