Loading vulnerability…
CVE-2026-33309 is an arbitrary file write vulnerability in Langflow affecting versions 1.2.0 through 1.8.1. The issue is described as a bypass of the prior fix for CVE-2025-68478, leaving the underlying architectural flaw in LocalStorageService unresolved. The storage layer does not enforce canonical path boundary containment checks and instead relies on HTTP-layer validation via the ValidatedFileName dependency. As a result, the POST /api/v2/files/ endpoint can be abused through a crafted multipart upload filename that bypasses the path-parameter guard, allowing an authenticated attacker to write files outside the intended storage directory and potentially anywhere on the host system. The arbitrary file write condition can be leveraged for remote code execution.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously disclosed Langflow arbitrary file write vulnerability via the v2 API, mentioned as part of the recurring architectural weakness.
An arbitrary file write vulnerability in Langflow caused by an incomplete fix, allowing authenticated attackers to write files anywhere on the host via the POST /api/v2/files/ endpoint, potentially leading to remote code execution.
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.