Loading story…
IBM disclosed CVE-2026-10561, a critical unauthenticated remote code execution flaw in Langflow OSS affecting versions 1.0.0 through 1.9.3. The vulnerability is rooted in improper isolation in the PythonREPLComponent: CPython's exec() restores full builtins access when the globals dictionary does not explicitly clear __builtins__, allowing attackers to bypass the intended import restrictions. IBM and downstream advisories rate the issue CVSS 3.1 10.0, noting it is remotely exploitable with low attack complexity, requires no privileges, and needs no user interaction.
The flaw can be chained with Langflow's default LANGFLOW_AUTO_LOGIN=true behavior, which exposes the /api/v1/auto_login endpoint and can issue a superuser JWT without credentials, enabling unauthenticated code execution on the host. Successful exploitation could lead to arbitrary OS command execution, theft of LLM provider keys, flow definitions and vector store credentials, and persistent compromise of affected systems. IBM recommends upgrading to Langflow OSS 1.9.4 immediately; no workaround was listed, and defenders are advised to apply vendor updates, harden access controls, and monitor for unauthorized activity.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
IBM published a security bulletin describing CVE-2026-10561, a critical unauthenticated remote code execution vulnerability affecting Langflow OSS versions 1.0.0 through 1.9.3. The bulletin says the flaw combines PythonREPLComponent builtins injection with Langflow's default auto-login behavior and recommends upgrading to version 1.9.4.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourceibm.com
Open sourcefirst.org
Open sourcefirst.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
IBM disclosed multiple severe vulnerabilities in **Langflow OSS** affecting versions `1.0.0` through `1.10.1`, including remote code execution, denial of service, path traversal, unauthorized file and vector store access, build job information disclosure, and exposed credentials through unauthenticated or insufficiently authorized API endpoints. The most prominent issue, **`CVE-2026-13446`**, is a hard-coded credentials flaw classified as **CWE-798** and scored **CVSS 9.8**, creating a network-exploitable path to compromise confidentiality, integrity, and availability. According to IBM's bulletin, the vulnerable endpoints could let attackers execute code, read arbitrary files, access secrets, modify other users' data, and cancel active builds without proper authorization. IBM advised users to upgrade Langflow OSS to **`1.10.2`** to remediate the issues, as the affected releases expose both application internals and connected external components to critical compromise.
Jul 18, 2026
IBM disclosed five high-severity vulnerabilities in **Langflow OSS** affecting versions `1.0.0` through `1.10.0`, including multiple paths to **remote code execution**, privilege escalation, and arbitrary file write. The issues are tracked as `CVE-2026-9135`, `CVE-2026-8476`, `CVE-2026-8481`, `CVE-2026-8635`, and `CVE-2026-8859`. Reported weaknesses include code injection through unvalidated dynamic `CodeInput` fields in the Policies component, unsafe `pickle.loads()` deserialization in the disk cache, direct execution of user-supplied Python in the `/api/v1/validate/code` endpoint, database manipulation that can elevate an authenticated user to superuser, and path traversal in the APIRequest component's **Save to File** feature via crafted `Content-Disposition` filenames. Several of the flaws require only authenticated access and can lead to arbitrary Python or system command execution with the privileges of the Langflow server process, creating a path to full host compromise in some deployments. IBM released **Langflow OSS `1.10.1`** to address all five vulnerabilities and advised organizations to upgrade immediately; additional mitigation guidance includes reviewing file-system permissions and sanitizing or removing cached data where possible. Public reporting said no active exploitation had been confirmed at publication time.
Jul 19, 2026
Threat actors rapidly exploited **CVE-2026-33017**, a critical unauthenticated remote code execution flaw in Langflow’s public flow build endpoint, allowing arbitrary Python code to reach an unsandboxed `exec()` path with a single crafted request. The bug affects Langflow versions prior to **1.9.0** and stems from the `POST /api/v1/build_public_tmp/{flow_id}/flow` endpoint accepting attacker-controlled flow data through an optional parameter. Researchers and vendor advisories said the issue is distinct from **CVE-2025-3248** because the vulnerable endpoint is intentionally public, meaning the fix required removing attacker-supplied flow data from that execution path rather than simply adding authentication. Sysdig and other researchers reported exploitation beginning within about **20 hours** of disclosure, with attackers scanning for exposed instances, validating code execution, reading files such as `.env`, `.db`, and `/etc/passwd`, stealing credentials, API keys, and database secrets, and attempting follow-on payload delivery from infrastructure including `173.212.205[.]251:8443`. The severity prompted **CISA** to add the flaw to its **Known Exploited Vulnerabilities** catalog and order federal agencies to remediate by **April 8, 2026** or discontinue use if they could not secure affected systems. Security guidance across the reports urged organizations to upgrade to **Langflow 1.9.0 or later**, restrict or remove internet exposure of the vulnerable endpoint, monitor outbound connections, and rotate secrets if compromise is suspected.
Jul 2, 2026