CVE-2026-53505: Thumbor proportion filter allows unbounded post-transform resize leading to remote DoS
Summary Thumbor's filters:proportion( ) filter does not enforce an upper bound on and runs in the post-transform phase. An attacker can trigger extremely large resizes (CPU/memory exhaustion) and cause denial of service. Details - Filter implementation: thumbor/filters/proportion.py - value is parsed as a float (BaseFilter.DecimalNumber) with no maximum.
Published Jul 31, 2026
Affected packages
thumbor
- Ecosystem
- PyPI
- Affected
- <= 7.7.7
- Fixed in
- 7.8.0
- Check
pip show thumbor
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Thumbor's filters:proportion(<value>) filter does not enforce an upper bound on <value> and runs in the post-transform phase. An attacker can trigger extremely large resizes (CPU/memory exhaustion) and cause denial of service.
Details
- Filter implementation:
thumbor/filters/proportion.py valueis parsed as a float (BaseFilter.DecimalNumber) with no maximum.- The filter computes
new_width = source_width * valueandnew_height = source_height * valueand then callsengine.resize(new_width, new_height). - Execution phase:
proportionruns in the default POST_TRANSFORM phase (after the main transform pipeline). This means it can effectively bypass request-level size clamping that happens earlier in the request lifecycle (e.g.,MAX_WIDTH/MAX_HEIGHTapplied toreq.width/req.height).
Documentation states the percentage argument should be 0.0 to 1.0 (docs/proportion.rst), but the implementation does not enforce this constraint.
PoC
Preconditions
- The
proportionfilter is enabled (it is enabled by default viaBUILTIN_FILTERS). - Either:
/unsafe/URLs are allowed (ALLOW_UNSAFE_URL=True, common default in some deployments), OR/unsafe/is disabled, and the attacker has a valid signed URL (i.e., the attacker is an authorized user/partner, or otherwise can obtain signed URLs issued by a trusted signing service).
Example request 1 (signed URL)
The following request was used to reproduce the issue and causes severe resource exhaustion:
http://<host>:<port>/<url-sign>/100x100/filters:proportion(10000)/example.jpg
Example request 2 (/unsafe/)
If /unsafe/ is enabled:
http://<host>:<port>/unsafe/100x100/filters:proportion(10000)/example.jpg
Impact
- Remote Denial of Service via CPU and/or memory exhaustion (and potentially process crash / OOM kill).
- Exploitability depends on deployment:
- If
/unsafe/is enabled: unauthenticated remote DoS. - If
/unsafe/is disabled: the attacker needs a valid signed URL (i.e., the attacker can legitimately request signed URLs, or has access to signed URLs issued for other users/partners). If signed URLs are not exposed to untrusted parties, exploitability is reduced but the risk still applies to any party who can generate/use signed URLs.
Suggested remediation
- Enforce a strict bound on the
proportionparameter (e.g.,0.0 < value <= 1.0as documented), or define a safe maximum based on intended semantics.
Credited to m01e-40x.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-53500
Thumbor treats ALLOWED_SOURCES string patterns as unescaped regex, allowing hostname bypass via wildcard dot
high8.2Jul 31, 2026CVE-2026-53501
Thumbor has HMAC validation bypass via multiple .replace() calls when removing URL signature
high8.2Jul 31, 2026CVE-2026-53502
Thumbor has path traversal via post-validation URL decoding bypass in file_loader
high8.7Jul 31, 2026CVE-2026-53503
Thumbor convolution filter allows divide-by-zero in C extension leading to remote DoS
high7.5Jul 31, 2026CVE-2026-53504
Thumbor has Regex Denial of Service (ReDoS) in `convolution` filter
high7.5Jul 31, 2026
