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

Back
New CVE Detected

CVE-2026-7663 – Unauthenticated Authorization Bypass in MCP Transport – IBM Langflow OSS 1.0.0–1.9.6

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-7663 is a critical improper authorization vulnerability (CWE-285) in IBM Langflow OSS affecting versions 1.0.0 through 1.9.6. The flaw resides in the Streamable MCP transport endpoint, where missing project ownership controls allow completely unauthenticated, remote attackers to access protected MCP project resources and execute MCP operations belonging to any user. It carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The Streamable MCP transport endpoint (/api/v1/mcp/project/{project_id}/streamable), introduced in Langflow 1.7, fails to properly enforce authorization checks. Project ownership controls are bypassed entirely, without requiring any credentials.
  • Trigger conditions: Network access to a Langflow instance with MCP Composer enabled is sufficient. IBM’s security bulletin notes that projects using OAuth or non-API-key authentication are particularly exposed. No user interaction is required.
  • Attack vector: Fully remote, unauthenticated, over HTTP/HTTPS. The endpoint is part of Langflow’s public-facing API surface and is reachable from the internet on exposed instances.
  • Impact: An attacker can enumerate MCP tool metadata, read project files, access superuser-level files, and execute MCP tools with elevated privileges — all without a valid credential. This results in high confidentiality and high integrity impact across affected projects.

Affected software

  • IBM Langflow OSS version 1.0.0 through 1.9.6 (inclusive)

Severity

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

Mitigation and recommended actions

  • Immediate action — patch: Upgrade IBM Langflow OSS to version 1.10.0, which contains the vendor-provided fix.
  • No workarounds available: IBM’s security bulletin explicitly states that no mitigations or workarounds exist short of upgrading. Organizations unable to patch immediately should consider isolating Langflow instances behind strict network access controls or a firewall to prevent unauthenticated internet access to the MCP transport 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