CVE-2026-8476 is a critical remote code execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0. The flaw resides in the disk-based caching mechanism, where the AsyncDiskCache class deserializes cached objects from disk using Python's pickle.loads() without validation, integrity verification, or authentication. Because pickle deserialization can execute attacker-controlled code during object reconstruction, any malicious payload that reaches the cache can be executed by the Langflow server. The issue is classified as CWE-502 and affects deployments in which an attacker can influence cached data through workflow inputs, custom components, API manipulation, or file-system-level access to cache contents.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical unsafe deserialization vulnerability in Langflow OSS AsyncDiskCache that can allow arbitrary code execution via malicious pickle data.
A critical remote code execution vulnerability in IBM Langflow OSS caused by unsafe pickle deserialization in the disk-based cache mechanism.
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.