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

New CVE Detected

CVE-2026-10134 – Unauthenticated RCE – IBM Langflow OSS 1.0.0 through 1.9.3

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

Summary

CVE-2026-10134 is a critical, unauthenticated server-side Remote Code Execution (RCE) vulnerability in IBM Langflow OSS versions 1.0.0 through 1.9.3. The flaw stems from an insecure exec() call in the PythonCodeStructuredTool component that processes fully attacker-controlled Python code, and is exploitable without any credentials once a public flow exists on the target instance. It carries a perfect CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting complete network-accessible compromise with no prerequisites beyond a reachable Langflow instance.

Technical details

  • Root cause: The PythonCodeStructuredTool component executes user-supplied code via exec(self.tool_code, globals(), local_namespace) with no sandboxing. The tool_code field is fully attacker-controlled.
  • Unauthenticated attack path: When any legitimate user marks a flow as PUBLIC — a standard, supported Langflow feature — the endpoint POST /api/v1/build_public_tmp/{flow_id}/flow becomes accessible without an Authorization header. An unauthenticated attacker who knows or discovers the public flow’s UUID can trigger server-side Python execution immediately.
  • Persistence mechanism: An attacker can modify a public flow’s tool_code so that all subsequent legitimate POST /api/v1/build/... calls by any authenticated user silently re-execute the attacker’s payload, establishing a durable server-side backdoor.
  • Attack vector: Network (AV:N); no authentication required (PR:N); no user interaction (UI:N); scope change (S:C).
  • Impact: Full arbitrary code execution on the Langflow server. Confirmed post-exploitation capabilities include: exfiltration of all secrets accessible to the Langflow process; read and write access to every flow, conversation, message, file upload, and saved component in the Langflow database; Server-Side Request Forgery (SSRF) to internal services and cloud metadata endpoints; lateral movement to other tenants on the same Langflow instance; and persistent backdoor implantation.

Affected software

  • IBM Langflow OSS 1.0.0 through 1.9.3 (inclusive)

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

Mitigation and recommended actions

  • Immediate — upgrade: Upgrade IBM Langflow OSS to version 1.10.0 or later, as recommended in the IBM Security Bulletin. Version 1.10.0 contains the vendor-provided fix for this vulnerability.
  • If immediate patching is not feasible:
    • Audit all existing flows and disable or restrict any flow marked as PUBLIC until the patch can be applied.
    • Restrict network access to the Langflow instance so that the /api/v1/build_public_tmp/ endpoint is not reachable from untrusted networks.
    • Review server-side process secrets and rotate any credentials accessible to the Langflow process.

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