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

Back
New CVE Detected

CVE-2026-9103 – Authentication Bypass – IBM Langflow OSS 1.0.0 through 1.10.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-9103 is a critical authentication bypass vulnerability (CVSS 9.8) in IBM Langflow OSS versions 1.0.0 through 1.10.0. The flaw resides in the /api/v1/login/auto_login endpoint, which issues long-lived superuser bearer tokens to any unauthenticated network caller when the AUTO_LOGIN configuration is enabled — a setting that is on by default. Classified under CWE-306 (Missing Authentication for Critical Function), this vulnerability enables unauthenticated remote attackers to gain full administrative control over any affected Langflow instance without any credentials or user interaction.

Technical details

  • Root cause: The /api/v1/login/auto_login endpoint issues 365-day superuser bearer tokens without performing any authentication check when AUTO_LOGIN is set to True. Because AUTO_LOGIN defaults to True, the vast majority of deployed instances are affected out-of-the-box.
  • Trigger conditions: No credentials, privileges, or user interaction required. Any network-reachable Langflow instance running an affected version with default configuration is exploitable.
  • Attack vector: Remote, unauthenticated HTTP request to the /api/v1/login/auto_login endpoint over the network (AV:N, AC:L, PR:N, UI:N).
  • Compounding factor: Permissive CORS settings configured with wildcard origins may expose issued tokens to unintended third-party origins, further broadening the attack surface.
  • Impact: An attacker who obtains the superuser bearer token gains full administrative access to the Langflow instance — 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 (Windows, Linux, macOS)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade IBM Langflow OSS to version 1.10.1 via PyPI. This is the sole remediation documented in IBM’s advisory; no interim workarounds have been published.
  • If immediate patching is not possible: Restrict network access to the Langflow instance at the firewall or reverse-proxy level to prevent unauthenticated external access. Additionally, review and tighten CORS configuration to permit only explicitly trusted origins.

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