NPM · AUGUST 2026 · CONFIRMED

Langflow Code Injection Vulnerability Actively Exploited

CVE-2026-9198Severity: CRITICAL

CISA has confirmed that a critical code injection vulnerability in Langflow (CVE-2026-9198) is being actively exploited, allowing unauthenticated remote code execution on default deployments.

What happened

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-9198 to its Known Exploited Vulnerabilities catalog, indicating active exploitation. This vulnerability in Langflow enables unauthenticated attackers to achieve full remote code execution on default deployments. Multiple proof-of-concept exploits have been publicly released, providing detailed instructions on how to leverage the vulnerability. To mitigate this threat, it is recommended to pin to a non-vulnerable version of Langflow or upgrade to a patched version if available. Additionally, review default deployments for potential exploitation. For more details, consult the primary sources listed.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If langflow is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats