Secuno
ENNL
Book demo

CVE-2026-19297

Langflow vulnerability

9.1 CRITICALEPSS 0.61%
  1. Published13 Aug 2026

Description

IBM Langflow OSS 1.0.0 through 1.9.6 could allow a remote attacker to obtain unauthorized access to user accounts due to improper restriction of excessive authentication attempts.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Langflow≥ 1.0.0 < 1.10.0

Remediation

Fixed in
Langflow≥ 1.10.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1081099.1
PHPNuxBill through 2025.3.20 contains an account takeover vulnerability in the customer…
CVE-2026-1056389.1
Plane is an open-source project management tool. Prior to 1.4.0, Plane's magic-code…
CVE-2026-857349.1
LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.5, the…
CVE-2026-62239.4
Improper restriction of excessive authentication attempts vulnerability in Bahçelievler…
CVE-2026-852378.1
A vulnerability in MISP's email-based one-time password (OTP) authentication flow…
CVE-2026-786559.1
Punk::Plugin::TOTP versions before 0.05 for Perl allow the second-factor attempt limit…

Frequently asked

Is CVE-2026-19297 being actively exploited?

CVE-2026-19297 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.61%.

How severe is CVE-2026-19297?

CVE-2026-19297 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.61% probability of exploitation.

Which products are affected by CVE-2026-19297?

Affected products include Langflow.

How do I fix CVE-2026-19297?

Upgrade affected software to a fixed version, for example Langflow 1.10.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-19297 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.