CVE-2026-9103
Auth bypass issues issue long-lived superuser tokens via /api/v1/login/auto_login (default enabled).
Is CVE-2026-9103 being exploited?
Not confirmed. CVE-2026-9103 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-9103?
CVE-2026-9103 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-9103?
Yes. A fix has been recorded for CVE-2026-9103. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-9103 affect?
CVE-2026-9103 affects IBM Langflow OSS 1.0.0 - 1.10.0, Instances with AUTO_LOGIN enabled (default), /api/v1/login/auto_login endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-9103?
Disable AUTO_LOGIN, restrict CORS, revoke/rotate tokens, restrict access, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can obtain long-lived superuser bearer tokens, gaining full administrative access, data theft, and service control.
Immediate action required
- affected>= 1.0.0 and <= 1.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.