# CVE-2026-11922: Rate-limit Bypass in zenml-io/zenml

> Attackers can bypass rate limits on login endpoints by spoofing IP headers, enabling unthrottled credential guessing attacks against ZenML users.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-4vf6-f9c7-q6rp

## What is CVE-2026-11922?

CVE-2026-11922 is a medium-severity vulnerability in zenml-io/zenml, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in zenml-io/zenml versions 0.57.0 through 0.94.2 allows an attacker to bypass rate-limiting on the `POST /api/v1/login` and self password-change endpoints by rotating the `X-Forwarded-For` header. The rate limiter keys requests by `request.client.host`, which is derived from the `X-Forwarded-For` header when Uvicorn is launched with `--proxy-headers --forwarded-allow-ips *`. This configuration allows clients to control the value of `request.client.host`, effectively bypassing rate-limiting protections. This vulnerability leaves the affected endpoints open to unthrottled credential guessing attacks.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-11922 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11922 is a medium-severity vulnerability in zenml-io/zenml, published on 24 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-11922 exists.

Affected product: zenml-io/zenml. 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-11922/ (Markdown: https://insights.sbomify.com/CVE-2026-11922/index.md)
```

## Sources

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

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