# CVE-2026-126934: Zipline 4.3.2 before 4.8.0 Rate Limit Bypass via Spoofed X-Forwarded-For

> Unauthenticated attackers can spoof X-Forwarded-For to bypass Zipline rate limits and brute-force passwords and codes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-rc68-98hh-j2v4, GHSA-v938-v8wg-9497

## What is CVE-2026-126934?

CVE-2026-126934 is a medium-severity security feature bypass vulnerability in diced zipline, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zipline 4.3.2 before 4.8.0 contains a rate limit bypass vulnerability that allows unauthenticated attackers to evade throttling by spoofing X-Forwarded-For headers when core.trustProxy is enabled. Attackers can send a different X-Forwarded-For value per request to obtain fresh rate-limit buckets, enabling unlimited guessing of login passwords, TOTP codes, and file and URL passwords.

Weakness: CWE-348 (Use of Less Trusted Source)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-126934 being exploited?

There is no known exploitation of CVE-2026-126934 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126934 is a medium-severity security feature bypass vulnerability in diced zipline, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126934 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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

## Sources

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

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