ZIPLINE · CVE-2026-126934 · Other
NO FIX YET · SEE WHAT TO DO
Zipline is a self-hosted file-sharing server. When core.trustProxy is enabled, an unauthenticated attacker can rotate the X-Forwarded-For header per request to get fresh rate-limit buckets, allowing unlimited guessing of login passwords, TOTP codes, and file or URL passwords.
first public Sep 27, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that self-host Zipline 4.3.2 through 4.8.0 behind a reverse proxy with core.trustProxy enabled are exposed, because the rate limiter then trusts client-supplied X-Forwarded-For values. Instances with trustProxy disabled, or deployments that do not run Zipline 4.3.2 to 4.8.0, are not affected by this flaw.
Not affected if trustproxy-disabled, version-outside-range
Who cares reverse-proxy, self-hosted, zipline
core.trustProxy is enabled in the Zipline configuration4.3.2 up to but not including 4.8.04.8.0 or laterZipline 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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.