Vulnerabilities for products matching "langflow"
Found 2 matching products. Filters apply to all results.
You can search for specific versions with /product/langflow/1.2.3
langflow / langflow
64 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
Critical | May 27, 2026 5/27/26 |
>= 1.0.0 <= 1.9.1
|
|
|
|
High | May 27, 2026 5/27/26 |
>= 1.0.0 <= 1.9.0
|
|
|
|
Critical | May 12, 2026 5/12/26 |
< 1.9.0
|
|
|
|
Medium | April 30, 2026 4/30/26 |
>= 1.0.0 < 1.9.0
|
|
|
|
High | April 8, 2026 4/8/26 |
>= 1.6.0 < 1.8.3
|
|
|
|
High | March 27, 2026 3/27/26 |
< 1.5.0
== 1.5.0-dev0
== 1.5.0-dev1
|
|
|
|
Critical | March 26, 2026 3/26/26 |
< 1.9.0
|
|
|
|
Critical | March 24, 2026 3/24/26 |
< 1.9.0
|
|
|
|
High | March 20, 2026 3/20/26 |
< 1.7.1
|
|
|
|
High | March 20, 2026 3/20/26 |
>= 1.0.0 < 1.9.0
|
|
|
|
Critical | March 19, 2026 3/19/26 |
>= 1.2.0 < 1.9.0
|
|
|
|
High | March 18, 2026 3/18/26 |
< 1.9.0
|
|
|
|
Critical | March 17, 2026 3/17/26 |
< 1.8.2
|
|
|
|
Critical | February 27, 2026 2/27/26 |
< 1.8.0
|
|
|
|
High | January 23, 2026 1/23/26 |
== 1.4.2
|
|
|
|
Unknown | January 23, 2026 1/23/26 |
== 1.4.2
|
|
|
|
Unknown | January 23, 2026 1/23/26 |
== 1.5.0-dev2
|
|
|
|
Unknown | January 23, 2026 1/23/26 |
== 1.4.2
|
|
|
|
Unknown | January 23, 2026 1/23/26 |
== 1.3.2
|
|
|
|
High | January 2, 2026 1/2/26 |
< 1.7.1
|
|
|
|
High | December 19, 2025 12/19/25 |
< 1.7.0
|
|
|
|
High | December 19, 2025 12/19/25 |
< 1.7.0
|
|
|
|
High | December 5, 2025 12/5/25 |
<= 1.6.9
|
|
|
|
High | August 25, 2025 8/25/25 |
< 1.5.0
== 1.5.0-dev0
== 1.5.0-dev1
== 1.5.0-dev10
== 1.5.0-dev11
== 1.5.0-dev12
== 1.5.0-dev13
== 1.5.0-dev14
== 1.5.0-dev15
== 1.5.0-dev16
== 1.5.0-dev17
== 1.5.0-dev18
== 1.5.0-dev19
== 1.5.0-dev2
== 1.5.0-dev20
== 1.5.0-dev21
== 1.5.0-dev22
== 1.5.0-dev23
== 1.5.0-dev24
== 1.5.0-dev25
== 1.5.0-dev26
== 1.5.0-dev27
== 1.5.0-dev28
== 1.5.0-dev29
== 1.5.0-dev3
== 1.5.0-dev30
== 1.5.0-dev31
== 1.5.0-dev4
== 1.5.0-dev5
== 1.5.0-dev6
== 1.5.0-dev7
== 1.5.0-dev8
== 1.5.0-dev9
|
|
|
|
Critical | April 7, 2025 4/7/25 |
< 1.3.0
|
|
|
|
Critical | November 4, 2024 11/4/24 |
<= 1.0.18
|
|
|
|
Critical | October 31, 2024 10/31/24 |
== 1.0.12
|
|
|
|
Low | September 27, 2024 9/27/24 |
<= 1.0.18
|
|
|
|
High | July 30, 2024 7/30/24 |
< 1.0.13
|
|
|
|
Critical | June 10, 2024 6/10/24 |
<= 0.6.19
|
langflow
17 vulnerabilities found| Title | Severity | Exploit | Date | Affected Version |
|---|---|---|---|---|
|
|
Critical | May 12, 2026 5/12/26 |
< 1.9.0
|
|
|
|
Low | April 20, 2026 4/20/26 |
< 1.9.1
|
|
|
|
Low | April 20, 2026 4/20/26 |
<= 1.8.3
|
|
|
|
Low | April 20, 2026 4/20/26 |
<= 1.8.3
|
|
|
|
High | March 27, 2026 3/27/26 |
< 1.5.1
|
|
|
|
Critical | March 26, 2026 3/26/26 |
< 1.9.0
|
|
|
|
High | March 20, 2026 3/20/26 |
< 1.7.1
|
|
|
|
High | March 20, 2026 3/20/26 |
>= 1.0.0 <= 1.8.1
|
|
|
|
Critical | March 19, 2026 3/19/26 |
>= 1.2.0 < 1.9.0
|
|
|
|
High | March 18, 2026 3/18/26 |
< 1.7.2
|
|
|
|
Critical | March 17, 2026 3/17/26 |
<= 1.8.2
|
|
|
|
Critical | February 27, 2026 2/27/26 |
<= 1.8.0rc2
|
|
|
|
High | January 23, 2026 1/23/26 |
<= 1.7.3
|
|
|
|
High | January 2, 2026 1/2/26 |
< 1.7.1
|
|
|
|
High | August 25, 2025 8/25/25 |
< 1.5.1
|
|
|
|
Critical | April 7, 2025 4/7/25 |
< 1.3.0
|
|
|
|
Critical | June 10, 2024 6/10/24 |
<= 0.6.19
|
Showing vulnerabilities for 2 products matching "langflow". Each product has independent pagination.
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.