Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-10561 – Unauthenticated RCE – IBM Langflow OSS 1.0.0–1.9.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-10561 is a critical unauthenticated remote code execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.9.3, assigned a maximum CVSS v3.1 base score of 10.0. The flaw combines improper isolation of Python execution in the PythonREPLComponent with an authentication bypass stemming from the platform’s default auto-login configuration, enabling any unauthenticated network attacker to execute arbitrary code on the host system and achieve complete system compromise.

Technical details

  • Root cause (code injection): The PythonREPLComponent‘s get_globals() method constructs a restricted globals dictionary for sandboxed Python execution but does not explicitly set globals_["builtins"] = {}. When builtins are absent, Python’s exec() function automatically injects the full builtins module, defeating the intended whitelist and exposing unrestricted access to import statements, file I/O, and other dangerous built-in functions (CWE-94: Improper Control of Generation of Code).
  • Root cause (authentication bypass): Langflow OSS ships with LANGFLOW_AUTO_LOGIN=true as a default configuration value, which causes the platform to issue superuser-level JWT tokens without requiring credentials. This grants any unauthenticated request the privileges needed to reach the Python execution component.
  • Trigger conditions: No authentication, prior account, or user interaction is required. An attacker need only send a crafted network request to the Langflow API endpoint backed by the PythonREPLComponent.
  • Attack vector: Network-accessible; Langflow exposes an HTTP/HTTPS API and web interface that is routinely deployed facing the public internet.
  • Impact: Arbitrary OS command execution at the privilege level of the Langflow backend process, credential and secret exfiltration, persistent system compromise, flow and data tampering.

Affected software

  • IBM Langflow OSS 1.0.0 through 1.9.3 (all versions in this range are affected)

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    • Attack Vector: Network | Attack Complexity: Low | Privileges Required: None | User Interaction: None | Scope: Changed | Confidentiality/Integrity/Availability: High

Mitigation and recommended actions

  • Immediate action — patch: IBM strongly recommends upgrading to Langflow OSS 1.9.4, which addresses both the Python execution isolation flaw and the authentication bypass.
  • If immediate patching is not possible:
    • Set LANGFLOW_AUTO_LOGIN=false in your Langflow environment configuration to disable unauthenticated token issuance and require explicit credential-based authentication.
    • Restrict network access to Langflow API and UI endpoints via firewall rules or a reverse proxy, preventing exposure to untrusted networks until the patch can be applied.
    • Monitor Langflow process activity for unexpected child process spawning or outbound network connections indicative of post-exploitation behavior.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge