NPM · SEPTEMBER 2026 · CONFIRMED

Langflow npm Package Critical Vulnerability: CVE-2026-0768 Exploited

Severity
HIGH
Affected component
langflow (npm)
Affected versions
>= 1.4.2-NA, <= 1.4.2-NA or >= 1.4.2, <= 1.4.2
Patched version
Not yet available
CVE-2026-0768

The Langflow npm package has a critical security defect that allows unauthenticated attackers to execute arbitrary Python code remotely. This vulnerability, tracked as CVE-2026-0768, is being actively exploited.

What happened

The Langflow npm package, versions >= 1.4.2-NA, <= 1.4.2-NA or >= 1.4.2, <= 1.4.2, contains a critical security defect. This defect allows unauthenticated attackers to execute arbitrary Python code remotely. The vulnerability, tracked as CVE-2026-0768, has been confirmed to be actively exploited in the wild. Attackers are using this flaw to conduct reconnaissance and harvest administrative credentials or superuser authentication keys.

Threat intelligence company VulnCheck detected the activity on its honeypots in the U.K. that were targeted in at least 50 exploitation attempts over the weekend, with attack traffic originating primarily from Russia. The total number of observed attacks increased to 360 as of today.

What to do about it

How 0Day would have caught 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.

Frequently asked questions

Am I affected?

You are affected if you are using Langflow npm package versions >= 1.4.2-NA, <= 1.4.2-NA or >= 1.4.2, <= 1.4.2.

What should I do right now?

Investigate the use of Langflow in your projects and consider alternative solutions until a patch is available.

Has this been exploited in the wild?

Yes, CVE-2026-0768 is being actively exploited.

Sources

Join the 0Day waitlist →

← Back to all threats