Quick answers
- Is CVE-2024-9277 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-9277 being exploited in the wild.
- How severe is CVE-2024-9277?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- Langflow up to 1.0.18; langflow (PyPI) ECOSYSTEM:introduced=0,last_affected=1.0.18.
- Is there a fix for CVE-2024-9277?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-9277 attacked?
- It is attacked from the adjacent network or over the network, in a software library.
- Am I affected by CVE-2024-9277?
- Check whether you run Langflow or langflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the HTTP POST Request Handler component (src/backend/base/langflow/interface/utils.py) and is classified as an inefficient regular expression complexity issue (CWE-1333, also known as ReDoS—Regular Expression Denial of Service). The flaw is triggered through manipulation of the remaining_text argument passed to a regex function. An authenticated attacker can craft malicious input that causes the regex engine to perform exponential backtracking, consuming significant CPU resources and degrading service availability. The vulnerability affects Langflow versions up to and including 1.0.18. No vendor patch information has been disclosed.
Affected products
- Langflow Langflow up to 1.0.18
Identifiers
- CVE-2024-9277
- GHSA-355v-2rjx-fpx7
- PYSEC-2026-1521
Timeline
- 2024-09-27: disclosed
- 2024-10-01: advisory