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.
CVE-2026-9103
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 23, 2026
Advisory Details (1)
Auto-updated Jul 25, 2026Security Bulletin: Unauthenticated Superuser Token Issuance via Auto-Login Endpoint
https://www.ibm.com/support/pages/node/7278926Vendor Advisories for CVE-2026-9103(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 33× in last 7d / 44× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:07 UTCGHSA enrichment
- 2026-07-29 20:41 UTCGHSA enrichment
- 2026-07-29 16:07 UTCGHSA enrichment
- 2026-07-29 11:44 UTCGHSA enrichment
- 2026-07-29 07:21 UTCGHSA enrichment
- 2026-07-29 02:52 UTCGHSA enrichment
- 2026-07-28 22:28 UTCGHSA enrichment
- 2026-07-28 18:06 UTCEG score recompute
- 2026-07-28 18:06 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 13:41 UTCGHSA enrichment
- 2026-07-28 09:12 UTCGHSA enrichment
- 2026-07-28 04:48 UTCGHSA enrichment
- 2026-07-28 00:24 UTCGHSA enrichment
- 2026-07-27 19:41 UTCGHSA enrichment
- 2026-07-27 15:15 UTCEG score recompute
- 2026-07-27 15:15 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 09:22 UTCGHSA enrichment
- 2026-07-27 04:59 UTCGHSA enrichment
- 2026-07-27 00:29 UTCGHSA enrichment
- 2026-07-26 20:06 UTCGHSA enrichment
- 2026-07-26 15:40 UTCEG score recompute
- 2026-07-26 15:40 UTCGHSA enrichment
Show 19 moreShow fewer
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:18 UTCEG score recompute
- 2026-07-26 11:18 UTCGHSA enrichment
- 2026-07-26 04:36 UTCEG score recompute
- 2026-07-26 04:35 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:23 UTCEG score recompute
- 2026-07-23 00:15 UTCEG score recompute
- 2026-07-23 00:15 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 20:01 UTCEG score recompute
- 2026-07-17 18:55 UTCEG score recompute
- 2026-07-17 18:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS p91CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS p97CRITICAL
- CVE-2007-0956EG 10.0EPSS p98HIGH
- CVE-2017-12822EG 9.9CRITICAL
- CVE-2016-8355EG 9.9CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-9103?
When was CVE-2026-9103 disclosed?
Is CVE-2026-9103 actively exploited?
What is the CVSS score of CVE-2026-9103?
How do I remediate CVE-2026-9103?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9103
Is Your Infrastructure Affected by CVE-2026-9103?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.