Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Unrated

Unauthenticated RCE in Langflow OSS PythonREPLComponent via Builtins Injection

IdentifiersCVE-2026-10561CWE-94

CVE-2026-10561 is a critical unauthenticated remote code execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.9.3. The flaw is in the PythonREPLComponent ("Python Interpreter"), where the get_globals() logic attempts to restrict Python execution using a global_imports whitelist, but does not explicitly set globals_["builtins"] = {}. As a result, CPython exec() automatically inserts the full builtins module when builtins is absent from the globals dictionary, defeating the intended isolation and making functions such as import, open, eval, and other builtins available to attacker-controlled code. IBM states this execution-isolation flaw can be combined with the default LANGFLOW_AUTO_LOGIN=true behavior, which issues a superuser JWT via GET /api/v1/auto_login without credentials, producing an unauthenticated path to arbitrary code execution on the host system.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary OS command execution with the privileges of the Langflow backend process. IBM indicates this can result in complete compromise of the affected host, including theft of LLM provider API keys from environment variables or the database, theft or tampering of flow definitions, exposure of vector store credentials such as Chroma, Pinecone, and Weaviate, and persistent compromise through cron jobs, backdoored files, or database modification. In default Docker deployments where the backend may run as root, impact can extend to full root-level host compromise. Confidentiality, integrity, and availability impacts are all high.

Mitigation

If you can’t patch tonight, do this now.

The provided content states IBM listed no workaround for CVE-2026-10561. Where immediate patching is not possible, reduce exposure by disabling or restricting access to Langflow instances, especially public network access; disable automatic login behavior if operationally possible; place the service behind strong authentication and network controls; and monitor for unauthorized access to /api/v1/auto_login, suspicious PythonREPLComponent use, unexpected process execution, file changes, cron entries, and secret access. These are compensating controls only and do not fully remediate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade IBM Langflow OSS to version 1.9.4 or later. Apply the vendor security update promptly across all affected deployments running versions 1.0.0 through 1.9.3. After patching, rotate potentially exposed secrets, including LLM provider keys and vector store credentials, review flow definitions and database contents for tampering, and inspect hosts and containers for persistence mechanisms or unauthorized modifications.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.