# CVE-2024-9277: Langflow HTTP POST Request utils.py redos

> Attackers can cause denial of service in Langflow via inefficient regular expression complexity in the HTTP POST request handler.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-355v-2rjx-fpx7, PYSEC-2026-1521

## What is CVE-2024-9277?

CVE-2024-9277 is a medium-severity denial of service vulnerability in Langflow Langflow, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2024-9277?

3 open source packages ship an affected version, including langflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions to 1.0.18 | None |
| `langflow` | PyPI | All versions to 1.0.18 | None |
| `langflow` | PyPI | All versions to 1.0.18 | None |

Products: Langflow Langflow.

## How do I fix CVE-2024-9277?

No fix has been published for CVE-2024-9277 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-9277 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9277 exists.

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9277 and fix it if it is affected.

What it is: CVE-2024-9277 is a medium-severity denial of service vulnerability in Langflow Langflow, published on 27 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9277 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions up to 1.0.18; no fix listed
- langflow (PyPI): affected all versions up to 1.0.18; no fix listed
- langflow (PyPI): affected all versions up to 1.0.18; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-9277/ (Markdown: https://insights.sbomify.com/CVE-2024-9277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9277
- OSV: https://osv.dev/vulnerability/CVE-2024-9277

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-9277/
Summaries are generated and may contain mistakes; the official description above is the record.