Loading vulnerability…
CVE-2026-12944 is an incomplete dangerous-imports blocklist vulnerability in the IBM Langflow OSS code-security scanner affecting versions 1.0.0 through 1.10.0. The flow validator permits authenticated users to submit custom components with unblocked Python networking-library imports. Module-level network operations in those components execute during server-side validation even though the scanner reports the component as validated. This permits arbitrary Python execution as UID 0 in the Langflow container and enables server-side request forgery.
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.
This small standalone repository contains an MIT license, a usage-oriented README, and one Python 3 exploit script using only the standard library. It targets CVE-2026-12944 in Langflow OSS through an incomplete custom-component import denylist: urllib.request and socket are described as omitted from the scanner's prohibited modules. The script supports a non-invasive --test mode that requests the public version API and checks whether the reported version falls within 1.0.0–1.10.0. Its --read and --fetch modes authenticate via AUTO_LOGIN or optional form-based credentials, then post generated component code to the custom_component API. The resulting server-process execution is used for file:// reads or arbitrary URL retrieval from the target's network position. It preserves cookies, bearer tokens, HTTP-to-HTTPS redirects, compressed responses, and provides optional TLS-verification bypass. The README states that Langflow 1.10.1 fixes the issue by adding the affected modules to dangerous-import/submodule controls.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vulnerabilidad crítica de validación incompleta de generación de código en el validador de flujos de IBM Langflow OSS. Un usuario autenticado puede eludir el escáner de seguridad mediante componentes personalizados con importaciones de bibliotecas y ejecutar código Python arbitrario como root dentro del contenedor, exponiendo credenciales de entorno y servicios internos.
A critical arbitrary Python code-execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0. Crafted components using socket or urllib imports can execute with root privileges on the Langflow server, allowing cloud credential theft, container filesystem exfiltration, and pivoting to internal Docker-network services. The affected scanner may misleadingly report these components as validated.
An authenticated, network-accessible arbitrary Python code-execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0. Successful exploitation executes code as root on the Langflow server and can enable AWS credential theft through IMDSv1 SSRF, container filesystem exfiltration, and lateral movement to internal Docker-network services. The component scanner may incorrectly return "validated": true, creating a false security signal.
A critical Langflow OSS code-security-scanner blocklist bypass that permits authenticated users to cause server-side execution of network operations and arbitrary Python code as root. The incomplete blocklist omits socket and urllib modules, enabling SSRF against cloud metadata services, file exfiltration, reverse-shell connections, and lateral movement to internal Docker-network services.
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.