Loading vulnerability…
CVE-2026-19286 is an improper code-generation control vulnerability in IBM Langflow OSS versions 1.0.0 through 1.11.1. The Agent-to-Agent (A2A) public execution path fails to invoke the guard that validates public flows cannot execute code. Consequently, a published A2A agent flow configured with no authentication can be used to cause Python execution in the Langflow backend process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
The repository contains a short README and a single Python proof-of-concept, poc.py, for a claimed authenticated Langflow remote-code-execution issue, CVE-2026-19286. The script accepts a target URL, valid account credentials, and an arbitrary Bash command. It first queries the Langflow version API and requires version 1.10.0, logs in to obtain a Bearer token, creates a crafted flow, and triggers a flow build while polling job events for output. The crafted flow embeds Python code in a custom component and uses an empty inner node type as the stated validation-bypass condition. Its payload executes the supplied command with shell=True, captures combined output, and intentionally raises an exception containing that output for in-band exfiltration. The visible code explicitly calls the version and login API paths; additional create/build/event API paths are referenced by helper functions but are not available in the provided truncated source, so they are not enumerated as exact endpoints. This is an active exploitation tool rather than a detection-only script, and it requires authentication.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code-execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.11.1 caused by improper enforcement of security restrictions on the A2A public endpoint.
A critical, remotely exploitable remote-code-execution vulnerability in IBM Langflow OSS versions 1.0.0 through 1.11.1. Improper enforcement of security restrictions on the A2A public endpoint can permit unauthenticated arbitrary code execution.
A critical unauthenticated remote code-execution vulnerability in Langflow OSS's Agent-to-Agent public execution path. When A2A is enabled and an auth_type=none agent flow is published, a network caller can execute Python in the Langflow backend process because the public-flow code-execution validation guard is not invoked.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.