Loading vulnerability…
CVE-2025-26319 is a pre-authentication arbitrary file upload vulnerability in Flowise v2.2.6 affecting the unauthenticated attachments or knowledge upload functionality exposed at /api/v1/attachments. According to the provided reporting, the route /api/v1/attachments/:chatflowId/:chatId is whitelisted from authentication and accepts file uploads via Multer before passing attacker-controlled chatflowId and chatId values into attachment handling logic. In the vulnerable path, createFileAttachment reads chatflowId and chatId directly from request parameters and addArrayFilesToStorage uses those values in filesystem path construction without sufficient validation. Because these parameters are not validated as safe identifiers before being joined with the storage path, an attacker can use path traversal sequences in chatflowId or chatId and combine that with file upload to write attacker-controlled files to arbitrary locations on disk when Flowise is configured to use local storage. The supplied material specifically states that a proof of concept used a manipulated chatId to traverse directories and overwrite /root/.flowise/api.json.
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.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Python exploit script (CVE-2025-26319_exp.py) and a README.md for CVE-2025-26319, a pre-auth arbitrary file upload vulnerability in Flowise. The exploit leverages the /api/v1/attachments endpoint, which is accessible without authentication, and abuses the 'chatId' parameter for path traversal, allowing files to be uploaded to arbitrary locations on the server. The script can upload any file, overwrite sensitive configuration files (such as /root/.flowise/api.json), or generate and upload webshells (PHP or Node.js) for remote code execution. The exploit is operational, providing both file upload and webshell deployment capabilities. The README provides usage examples and explains the attack mechanism. The main entry point is the Python script, which is well-structured and automates the exploitation process.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Flowise-related vulnerability that the content says is being actively exploited and is included in VulnCheck's Known Exploited Vulnerabilities catalog, but no technical details are provided.
An arbitrary file upload vulnerability in Flowise that was flagged for active exploitation by VulnCheck's Canary network.
A previously disclosed Flowise vulnerability referenced as one of the earlier Flowise flaws actively exploited in the wild.
A Flowise arbitrary file upload vulnerability that the content states has seen in-the-wild exploitation.
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.