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

Back
New CVE Detected

CVE-2026-19286 – Unauthenticated RCE – Langflow OSS 1.0.0 through 1.11.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-19286 is a critical remote code execution vulnerability in IBM Langflow OSS, caused by improper enforcement of security restrictions on the platform’s A2A (Agent-to-Agent) public endpoint. The flaw allows a remote, unauthenticated attacker to execute arbitrary code on affected instances. It carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: Langflow’s A2A public endpoint does not properly enforce security restrictions, permitting attacker-supplied input to be processed in a way that results in code generation/execution (CWE-94: Improper Control of Generation of Code).
  • Trigger conditions: The A2A endpoint is reachable without authentication; no special preconditions or user interaction are required to exploit it.
  • Attack vector: Network — an attacker sends requests directly to the exposed A2A endpoint over HTTP(S).
  • Impact: Successful exploitation results in arbitrary code execution on the host running Langflow, with full compromise of confidentiality, integrity, and availability of the affected system.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.11.1 (inclusive)

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

  • Immediate: Upgrade Langflow OSS to version 1.11.2 or later, available via PyPI.
  • If immediate patching is not possible: Restrict network access to the Langflow instance and its A2A endpoint to trusted internal networks only, and place the application behind an authenticating reverse proxy or VPN until the upgrade can be applied. Continuously monitor exposed Langflow deployments for unexpected process execution or outbound connections.

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: a page titled Langflow followed by a script tag loading ./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