CVE-2026-126932 · Package
NO FIX YET · SEE WHAT TO DO
Zipline 4.6.2 before 4.8.0 lets a logged-in user change a file's Content-Type through the file metadata API, even when the administrator has disabled that type. The attacker uploads a permitted file, then sets a disabled type such as text/html so the raw file endpoint serves it under that type.
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.6.2 or later before 4.8.0 and let users upload files. Exposure depends on administrators having disabled MIME types for security reasons; a deployment with a permissive MIME policy gains little from the bypass. Instances on 4.8.0 or later, or with no user accounts, can skip it.
Not affected if no-user-uploads, version-4.8.0-or-later
Who cares self-hosted, zipline
4.8.0.4.8.0 or later.Zipline 4.6.2 before 4.8.0 contains a policy bypass vulnerability that allows authenticated users to evade administrator-disabled MIME types by editing file metadata. Attackers can upload a permitted file, then set a disabled type such as text/html through PATCH /api/user/files/:id so /raw/:id serves that Content-Type.
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:L/UI:N/VC:N/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.