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

Back
New CVE Detected

CVE-2026-9202 – Authentication Bypass Leading to RCE – 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-9202 is a critical authentication bypass and remote code execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0. Unauthenticated attackers can exploit an open user registration endpoint to create arbitrary accounts; when the documented deployment option NEW_USER_IS_ACTIVE=true is configured, those accounts become immediately active and can be used to authenticate and reach RCE endpoints — bypassing any requirement for AUTO_LOGIN. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: Missing authentication for a critical function (CWE-306) — the Langflow registration API endpoint imposes no access controls, allowing any unauthenticated caller to create unlimited user accounts.
  • Trigger conditions: The full exploitation chain — account creation followed by authenticated access to RCE endpoints — requires the NEW_USER_IS_ACTIVE=true deployment option to be enabled on the target instance. This is a documented, supported configuration option.
  • Attack vector: A remote, unauthenticated attacker sends HTTP requests to the Langflow registration API to create a user account. If NEW_USER_IS_ACTIVE=true is set, the account is immediately active. The attacker then authenticates with those credentials and accesses RCE-capable endpoints on the Langflow server.
  • Impact: Successful exploitation results in full remote code execution on the host server, with complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.0

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

Mitigation and recommended actions

  • Patch immediately: IBM strongly recommends upgrading to Langflow OSS version 1.10.1 or later, available on PyPI.
  • No workarounds available: IBM has confirmed that no workarounds exist for this vulnerability; upgrading to the patched version is the only remediation.
  • Organizations unable to patch immediately should assess whether NEW_USER_IS_ACTIVE=true is set in their deployment and consider restricting network access to the Langflow registration endpoint.

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