Quick answers
- Is CVE-2026-19286 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19286 being exploited in the wild.
- How severe is CVE-2026-19286?
- Critical severity, with a CVSS score of 9.8, published 28 August 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.11.1.
- Is there a fix for CVE-2026-19286?
- A patch was published on 2026-08-28: Version 1.11.2 addresses the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19286 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19286?
- Check whether you run IBM Langflow OSS or Langflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a code injection flaw (CWE-94) in the A2A public execution endpoint that fails to invoke the validate_public_flow_no_code_execution guard applied to other unauthenticated execution surfaces. The root cause is improper enforcement of security restrictions: the A2A path does not validate or block code execution when auth_type=none agent flows are published, allowing an unauthenticated network caller to execute arbitrary Python in the Langflow backend process. The attack requires only network access (no authentication or user interaction needed) and is trivial to exploit (CVSS 9.8: AV:N/AC:L/PR:N/UI:N). The vulnerability affects Langflow OSS versions 1.0.0 through 1.11.1; IBM recommends immediate upgrade to version 1.11.2 or later.
Affected products
- IBM Langflow OSS 1.0.0 through 1.11.1
Timeline
- 2026-08-24: disclosed: Initial Publication
- 2026-08-28: patched: Version 1.11.2 addresses the vulnerability