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

Back
New CVE Detected

CVE-2026-7803 – Unauthenticated RCE – 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-7803 is a critical unauthenticated remote code execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0, caused by improper validation of flow nodes that have missing or empty component type fields (CWE-20). An unauthenticated, network-accessible attacker can exploit this flaw to execute arbitrary code on the server, resulting in full compromise of confidentiality, integrity, and availability. IBM has rated this CVSS 9.8 (Critical) and has released a patch in version 1.10.1.

Technical details

  • Root cause: The flow node validator fails to reject nodes whose component type field is absent or empty. Instead of blocking such nodes, the validator silently skips them. This means that even in configurations where custom components are restricted, attacker-supplied component code embedded in a malicious flow definition can still be executed at build time if the type field is omitted or blank.
  • Trigger conditions: An attacker submits a crafted flow payload containing a node with a missing or empty component type field. No authentication, user interaction, or special privileges are required.
  • Attack vector: Network-accessible; exploitable remotely over HTTP against an exposed Langflow instance.
  • Impact: Arbitrary code execution on the host server with the privileges of the Langflow process — full compromise of confidentiality, integrity, and availability.

Affected software

  • IBM Langflow OSS 1.0.0 through 1.10.0 (inclusive)

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 action — patch now: Upgrade to Langflow OSS 1.10.1 or later, available via PyPI. The fix ensures that nodes containing executable code with a missing or empty type field are now correctly treated as blocked components.
  • No workarounds available: IBM has confirmed that no workarounds exist for this vulnerability. Patching to version 1.10.1 is the only effective remediation.
  • Network-level hardening: Until patching is complete, restrict inbound access to Langflow instances to trusted networks and block public internet exposure at the perimeter where operationally feasible.

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