# CVE-2026-9103: Unauthenticated Superuser Token Issuance via Auto-Login Endpoint

> Unauthenticated attackers can obtain superuser tokens via the auto-login endpoint, gaining full administrative access to the application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-88m4-9v35-3pc9

## What is CVE-2026-9103?

CVE-2026-9103 is a critical authentication bypass vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-9103?

It affects 1 product.


Products: Langflow Langflow.

## How do I fix CVE-2026-9103?

No fix has been published for CVE-2026-9103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9103 exists.

Public exploit code:

- Langflow OSS - Superuser Token Issuance (nuclei): http/cves/2026/CVE-2026-9103.yaml

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9103 and fix it if it is affected.

What it is: CVE-2026-9103 is a critical authentication bypass vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9103 exists.

Affected product: Langflow Langflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9103/ (Markdown: https://insights.sbomify.com/CVE-2026-9103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9103
- OSV: https://osv.dev/vulnerability/CVE-2026-9103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9103/
Summaries are generated and may contain mistakes; the official description above is the record.