Langflow: security bypass flaw under attack

What is affected

Langflow is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Langflow contains an authorization bypass through user-controlled key vulnerability which allows an authenticated attacker to execute any flow belonging to another user by specifying the victim's flow ID in the request.

What an attacker can do

This is a security bypass flaw. It lets an attacker slip past a built-in protection, so warnings and checks that normally stop malicious content never appear.

How it is reached

Over the internet or network

Access the attacker needs

A basic user account

Does the victim have to do something?

No, works without the victim doing anything

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Langflow at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Vendor advisories and fixes

• github.comgithub.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on July 7, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by July 10, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 0.9% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 58% of all scored vulnerabilities.

Its CVSS severity score is 8.4 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.9.1, an Insecure Direct Object Reference (IDOR) vulnerability in /api/v1/responses endpoint allows an authenticated attacker to execute any flow belonging to another user by specifying the victim's flow ID in the request. This vulnerability is fixed in 1.9.1.