CVE-2026-9103
Langflow authentication bypass
- Published17 Jul 2026
Description
IBM Langflow OSS 1.0.0 through 1.10.0 could allow a remote attacker to gain unauthorized access due to improper authentication in the /api/v1/login/auto_login endpoint. The endpoint issues long-lived superuser bearer tokens without requiring authentication when the AUTO_LOGIN configuration is enabled (enabled by default), which may allow an unauthenticated network attacker to obtain full administrative access. Additionally, permissive cross-origin resource sharing (CORS) settings may allow tokens to be exposed to unintended origins, increasing the risk of unauthorized access.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-9103 being actively exploited?
CVE-2026-9103 is not in the CISA KEV catalog. Its EPSS exploit probability is 3.21%.
How severe is CVE-2026-9103?
CVE-2026-9103 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 3.21% probability of exploitation.
Which products are affected by CVE-2026-9103?
Affected products include Langflow.
How do I fix CVE-2026-9103?
Upgrade affected software to a fixed version, for example Langflow 1.10.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-9103 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.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.