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

Back
New CVE Detected

CVE-2026-8446 – Authentication Bypass – IBM Langflow OSS 1.0.0 through 1.10.3

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-8446 is an authentication bypass vulnerability (CWE-306, Missing Authentication for Critical Function) in IBM Langflow OSS. It affects versions 1.0.0 through 1.10.3 and carries a HIGH severity rating (CVSS 7.5). A remote, unauthenticated attacker can access the Model Context Protocol (MCP) composer endpoint, leading to disclosure of sensitive information.

Technical details

  • Root cause: The authentication mechanism fails to validate requests to the MCP composer endpoint under a specific configuration.
  • Trigger conditions: The endpoint is exposed when mcp_composer_enabled=true (the default) and projects are configured with auth_type=oauth.
  • Attack vector: Network (AV:N); low attack complexity, no privileges, and no user interaction required.
  • Impact: High confidentiality impact — an unauthenticated attacker can reach the MCP composer endpoint without proper credential verification, potentially accessing sensitive data. No integrity or availability impact.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.3.

Severity

  • CVSS v3.1 base score: 7.5 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Langflow 1.11.0 or later.
  • If no patch can be applied: Where feasible, disable the MCP composer (mcp_composer_enabled=false) and review the use of auth_type=oauth for affected projects. Restrict network access to the Langflow instance so the MCP composer endpoint is not reachable from untrusted networks.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <title>Langflow</title>, ./assets/index-….js

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