This page was not yet optimized for use on mobile devices.
CVE-2026-9135
Data
| Vulnerability ID | CVE-2026-9135 |
|---|---|
| Published on | 17.07.2026 19:17 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:langflow:langflow:1.0.0:alpha11:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha12:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha13:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha14:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha15:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha17:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha18:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha19:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha20:*:*:*:*:*:*,
cpe:2.3:a:langflow:langflow:1.0.0:alpha21:*:*:*:*:*:*,
…
running on/with
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.