CVE-2026-126940: Zipline before 4.6.4 Rate Limit Bypass via Query String and Header
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: diced zipline 4.6.4.
Low priority for now. Upgrade to diced zipline 4.6.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Zipline before 4.6.4 contains a rate limit bypass vulnerability that allows remote attackers to evade request limits by varying query strings or supplying the x-zipline-p-filename header. Attackers can append differing query parameters to login and file or short-link password verification endpoints to perform credential guessing beyond the intended rate limits.
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- EPSS
- —
- CWE
- CWE-307
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
diced zipline
- 4.6.4not affected
- before 4.6.4affected · semver
Same product
diced: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-126945Zipline before 4.5.1 Stored XSS via HighlightCode Component37Monitor
- CVE-2026-126952Zipline through 4.4.0 WebAuthn Authentication Bypass via Passkey Login36Monitor
- CVE-2026-126937Zipline before 4.6.5 TOCTOU Race Condition via /api/setup36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-126938Nov 13, 2026 · Zipline before 4.6.4 Upload Quota Bypass via Forged Content-Range Headers28Monitor
- ← EarlierCVE-2026-126939Nov 13, 2026 · Zipline before 4.6.4 Unauthenticated File Listing via page Query Parameter27Monitor
- Later →CVE-2026-126941Nov 13, 2026 · Zipline through 4.6.2 Privilege Escalation via Missing Role Checks on User Endpoints32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| diced zipline | 4.6.4 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026same day
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- de3erve-hunterreporter
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-307 · Improper Restriction of Excessive Authentication AttemptsCVSS vector
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-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Dictionary-based Password AttackCAPEC-16likelihood: Medium · High
- Password Brute ForcingCAPEC-49likelihood: Medium · High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Password SprayingCAPEC-565likelihood: High · High
- Credential StuffingCAPEC-600likelihood: High · High
- Use of Known Kerberos CredentialsCAPEC-652likelihood: Medium · High
- Use of Known Operating System CredentialsCAPEC-653likelihood: High · High
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.