CVE-2026-53505 json
Thumbor proportion filter allows unbounded post-transform resize leading to remote DoS
published 2026-07-31 3 mo ago modified 2026-09-08 2 mo ago also GHSA-phj3-59pf-cp83 , PYSEC-2026-3621 , EUVD-2026-51611
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
Thumbor is an open-source photo thumbnail service by globo.com. Prior to 7.8.0, 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. This issue is fixed in 7.8.0.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | thumbor | <7.8.0 |
7.8.0 |
Affected products
- thumbor thumbor
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/thumbor/thumbor/commit/2c716119de986cfc68c7071af52a98187e006023
web
-
github.com
/thumbor/thumbor/security/advisories/GHSA-phj3-59pf-cp83
web
-
github.com
/thumbor/thumbor/releases/tag/7.8.0
web
-
github.com
/thumbor/thumbor
package
-
pypi.org
/project/thumbor
package
-
github.com
/advisories/GHSA-phj3-59pf-cp83
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-53505
advisory
Sources
- CVE List CVE-2026-53505
- GitHub Advisory GHSA-phj3-59pf-cp83
- NVD CVE-2026-53505
- OSV PYSEC-2026-3621
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.