CVE-2026-9103

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.8
EG Score
9.8(medium)
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 computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
86%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Sep 19, 2026
No patch confirmed yet.
generic

Security Bulletin: Unauthenticated Superuser Token Issuance via Auto-Login Endpoint

https://www.ibm.com/support/pages/node/7278926

Vendor 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 12× in last 7d / 97× 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.

Showing the most recent 100 of 315 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 09:55 UTCGHSA enrichment
  4. 2026-09-18 04:32 UTCEG score recompute
  5. 2026-09-18 04:32 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 10:15 UTCEG score recompute
  8. 2026-09-17 10:15 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 03:12 UTCEPSS rescore
  12. 2026-09-14 12:18 UTCGHSA enrichment
  13. 2026-09-14 07:48 UTCGHSA enrichment
  14. 2026-09-14 03:23 UTCGHSA enrichment
  15. 2026-09-13 23:01 UTCGHSA enrichment
  16. 2026-09-13 18:30 UTCGHSA enrichment
  17. 2026-09-13 13:53 UTCGHSA enrichment
  18. 2026-09-13 09:31 UTCGHSA enrichment
  19. 2026-09-13 05:08 UTCGHSA enrichment
  20. 2026-09-12 17:00 UTCEG score recompute
  21. 2026-09-12 17:00 UTCGHSA enrichment
  22. 2026-09-12 15:02 UTCEPSS rescore
  23. 2026-09-12 12:36 UTCGHSA enrichment
  24. 2026-09-12 07:23 UTCGHSA enrichment
  25. 2026-09-12 01:28 UTCGHSA enrichment
Show 75 more
  1. 2026-09-11 21:06 UTCEG score recompute
  2. 2026-09-11 21:06 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:38 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-08 00:00 UTCEG score recompute
  8. 2026-09-07 23:59 UTCGHSA enrichment
  9. 2026-09-06 17:44 UTCEG score recompute
  10. 2026-09-06 17:44 UTCGHSA enrichment
  11. 2026-09-06 13:48 UTCEPSS rescore
  12. 2026-09-06 13:21 UTCGHSA enrichment
  13. 2026-09-06 05:51 UTCGHSA enrichment
  14. 2026-09-06 01:29 UTCGHSA enrichment
  15. 2026-09-05 20:26 UTCEG score recompute
  16. 2026-09-05 20:26 UTCGHSA enrichment
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-08-31 05:49 UTCGHSA enrichment
  23. 2026-08-31 01:26 UTCGHSA enrichment
  24. 2026-08-30 21:02 UTCEG score recompute
  25. 2026-08-30 21:02 UTCGHSA enrichment
  26. 2026-08-30 19:18 UTCEPSS rescore
  27. 2026-08-30 16:39 UTCGHSA enrichment
  28. 2026-08-30 12:17 UTCGHSA enrichment
  29. 2026-08-30 07:38 UTCGHSA enrichment
  30. 2026-08-30 03:16 UTCEG score recompute
  31. 2026-08-30 03:16 UTCGHSA enrichment
  32. 2026-08-30 01:22 UTCEPSS rescore
  33. 2026-08-28 21:42 UTCEPSS rescore
  34. 2026-08-28 01:48 UTCGHSA enrichment
  35. 2026-08-27 21:25 UTCEG score recompute
  36. 2026-08-27 21:25 UTCGHSA enrichment
  37. 2026-08-27 14:25 UTCEPSS rescore
  38. 2026-08-27 12:13 UTCGHSA enrichment
  39. 2026-08-27 02:58 UTCGHSA enrichment
  40. 2026-08-26 22:36 UTCEG score recompute
  41. 2026-08-26 22:35 UTCGHSA enrichment
  42. 2026-08-26 14:47 UTCEPSS rescore
  43. 2026-08-26 13:42 UTCGHSA enrichment
  44. 2026-08-26 09:02 UTCGHSA enrichment
  45. 2026-08-26 04:33 UTCGHSA enrichment
  46. 2026-08-25 23:48 UTCGHSA enrichment
  47. 2026-08-25 18:52 UTCEG score recompute
  48. 2026-08-25 18:52 UTCGHSA enrichment
  49. 2026-08-25 13:49 UTCEPSS rescore
  50. 2026-08-25 13:10 UTCGHSA enrichment
  51. 2026-08-25 08:43 UTCGHSA enrichment
  52. 2026-08-25 03:59 UTCGHSA enrichment
  53. 2026-08-24 23:37 UTCGHSA enrichment
  54. 2026-08-24 19:15 UTCEG score recompute
  55. 2026-08-24 19:15 UTCGHSA enrichment
  56. 2026-08-24 14:18 UTCEPSS rescore
  57. 2026-08-24 13:34 UTCEG score recompute
  58. 2026-08-24 13:34 UTCGHSA enrichment
  59. 2026-08-24 09:08 UTCGHSA enrichment
  60. 2026-08-24 04:26 UTCGHSA enrichment
  61. 2026-08-24 00:03 UTCGHSA enrichment
  62. 2026-08-23 19:41 UTCGHSA enrichment
  63. 2026-08-23 15:18 UTCGHSA enrichment
  64. 2026-08-23 10:55 UTCGHSA enrichment
  65. 2026-08-23 06:32 UTCGHSA enrichment
  66. 2026-08-23 02:10 UTCEG score recompute
  67. 2026-08-23 02:10 UTCGHSA enrichment
  68. 2026-08-23 00:19 UTCEPSS rescore
  69. 2026-08-22 21:47 UTCGHSA enrichment
  70. 2026-08-22 17:24 UTCGHSA enrichment
  71. 2026-08-22 13:01 UTCGHSA enrichment
  72. 2026-08-22 08:38 UTCGHSA enrichment
  73. 2026-08-22 04:15 UTCGHSA enrichment
  74. 2026-08-21 23:51 UTCEG score recompute
  75. 2026-08-21 23:51 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-9103.yaml
    First seen Jan 1, 2026

    Langflow OSS - Superuser Token Issuance

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9103?
CVE-2026-9103 is a critical vulnerability published on July 17, 2026. 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/autologin endpoint. The endpoint issues long-lived superuser bearer tokens without requiring authentication when the AUTOLOGIN configuration is enabled…
When was CVE-2026-9103 disclosed?
CVE-2026-9103 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9103 actively exploited?
CVE-2026-9103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 14.0% of all scored CVEs.
What is the CVSS score of CVE-2026-9103?
CVE-2026-9103 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-9103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9103, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9103

Explore →

Is Your Infrastructure Affected by CVE-2026-9103?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs