Quick answers
- Is CVE-2026-76059 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76059 being exploited in the wild.
- How severe is CVE-2026-76059?
- High severity, with a CVSS score of 8.8, published 10 September 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.11.5.
- Is there a fix for CVE-2026-76059?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-76059 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-76059?
- 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 logic error in IBM Langflow's static security scanner used to validate custom component source code. An attacker can craft an annotated class-body assignment that resolves to a dangerous callable through alias tracking, but because the resolved value is never checked against the blocklist, the dangerous function passes validation. If the malicious component is deployed and executed, arbitrary OS commands execute on the server in-process with service privileges. This affects Langflow OSS versions 1.0.0 through 1.11.5; the attack requires the ability to submit custom components, which may be restricted to authenticated users depending on configuration.
Affected products
- IBM Langflow OSS 1.0.0 through 1.11.5
Timeline
- 2026-09-10: disclosed