NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Langflow

CVE-2024-9277: Inefficient Regular Expression Complexity in langflow

mediumCVSS 4.0 5.1 · 3.1 3.5GHSA-355v-2rjx-fpx7

Langflow 1.0.18 and earlier contains a regular expression denial of service in src/backend/base/langflow/interface/utils.py. A crafted remaining_text value sent to the HTTP POST handler makes the regex burn CPU. The advisory lists no patched version, and the exploit is public.

Published Sep 27, 2024 · Updated Oct 1, 2024 · Analysis Nov 1, 2026

What an attacker can do

The flaw sits in a regular expression in interface/utils.py that processes the remaining_text argument. A crafted string triggers heavy backtracking (CWE-1333), so one request can hold a worker at full CPU. Repeated requests can make the Langflow service slow or unresponsive.

The impact is availability only. The CVSS vector shows adjacent network access, low privileges and no user interaction, with no confidentiality or integrity loss. That fits a Langflow instance on an internal network used by several people. The advisory says the exploit is public and the vendor did not respond to the disclosure.

For teams that run Langflow next to AI agents, the risk is a stalled flow-building service that agents or pipelines depend on. It does not give code execution or data access.

Who is affected

The pip package langflow, versions up to and including 1.0.18. Check the installed version:

pip show langflow

Any instance reachable by authenticated users who can send requests to the affected handler is exposed.

langflow

Ecosystem
PyPI
Affected
<= 1.0.18
Fixed in
No patched version yet
Check
pip show langflow

How to fix it

The advisory lists no patched version, and the vendor did not respond to the reporter. Check the Langflow releases for a newer version than 1.0.18 and test whether the remaining_text handling in interface/utils.py still uses the unbounded regex before relying on it.

Until then, keep Langflow off untrusted networks, require authentication, and put request rate limits and timeouts in front of it. These are general mitigations, not advisory instructions.

How to tell if you were hit

Look for Langflow worker processes pinned at high CPU with few active requests, and for POST requests that take unusually long or time out. Check access logs for very long or repetitive payloads from a single client, and restart the service if a worker hangs.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

A vulnerability classified as problematic was found in Langflow up to 1.0.18. Affected by this vulnerability is an unknown functionality of the file \src\backend\base\langflow\interface\utils.py of the component HTTP POST Request Handler. The manipulation of the argument remaining_text leads to inefficient regular expression complexity. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Credited to m3t3kh4n.

Questions

Is there a patch for CVE-2024-9277?

None is listed in the advisory. It marks versions up to 1.0.18 as affected and says the vendor did not reply to the disclosure.

Can it lead to code execution?

No source says so. It is a denial of service through regex backtracking. The CVSS vector shows only an availability impact.

Is a public exploit available?

The advisory says the exploit has been disclosed publicly. It is not in CISA's KEV catalog, and no source reports attacks in the wild.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Langflow vulnerabilities

All Langflow entries