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

Back
New CVE Detected

CVE-2026-9198 – Unauthenticated RCE – IBM Langflow OSS 1.0.0–1.10.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-9198 is a critical unauthenticated remote code execution (RCE) vulnerability affecting IBM Langflow OSS versions 1.0.0 through 1.10.0. By chaining two API endpoints — an authentication bypass in /api/v1/auto_login and arbitrary Python code execution in /api/v1/validate/code — an unauthenticated network attacker can achieve full RCE on any default-configured Langflow deployment. IBM has assigned a CVSS v3.1 base score of 9.8 (Critical) and recommends immediate upgrade to version 1.10.1.

Technical details

  • Root cause: Two combined flaws enable the exploit chain. First, the /api/v1/auto_login endpoint, when AUTO_LOGIN is enabled (the default configuration), issues long-lived SUPERUSER bearer tokens to any unauthenticated network caller with no credential check. Second, the /api/v1/validate/code endpoint passes user-supplied Python code directly to Python’s exec() without sandboxing or input restrictions, including executing decorators and default argument expressions at function-definition time.
  • Trigger conditions: Default Langflow deployment with AUTO_LOGIN=true (enabled out of the box); no authentication or special configuration required on the part of the attacker.
  • Attack vector: A two-step, fully unauthenticated network attack — (1) call /api/v1/auto_login to obtain a SUPERUSER bearer token; (2) use that token to submit a malicious Python payload to /api/v1/validate/code, triggering arbitrary code execution on the server.
  • Impact: Full remote code execution as the Langflow process user, with complete loss of confidentiality, integrity, and availability on the affected host.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.0 (inclusive)

Severity

CVSS v3.1 base score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE: CWE-94 (Improper Control of Generation of Code – Code Injection)

Mitigation and recommended actions

  • Immediate: Upgrade to Langflow OSS version 1.10.1, available on PyPI. IBM strongly recommends addressing this vulnerability immediately by upgrading to 1.10.1.
  • IBM’s official security advisory documents no workarounds for this vulnerability; upgrading to version 1.10.1 is the only supported remediation.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge