Thumbor is an open-source photo thumbnail service by globo.com. Prior to 7.8.0, the ALLOWED_SOURCES configuration passes plain strings to re.match() without escaping dots, so a hostname differing at dot positions can match the allowlist. This issue is fixed in 7.8.0.
CVE-2026-53500
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 68(Attend)EG Risk 68/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
August 1, 2026
Advisory Details (3)
Auto-updated Jul 31, 2026Release 7.8.0
Patch available: thumbor/thumbor 7.8.0
https://github.com/thumbor/thumbor/releases/tag/7.8.0commit 68876715350c (thumbor/thumbor)
Patch available: thumbor/thumbor 7.8.0 (contains commit 68876715350c)
https://github.com/thumbor/thumbor/commit/68876715350c6c8f49c324e5515e64908830aed7ALLOWED_SOURCES string patterns treated as unescaped regex, allowing hostname bypass via wildcard dot · Advisory · thumbor/thumbor · GitHub
https://github.com/thumbor/thumbor/security/advisories/GHSA-6x26-6r6f-m537Vendor Advisories for CVE-2026-53500(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| thumbor | 6.3.2-3 ... 7.7.7-6 (16 versions) | 7.8.0-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| thumbor | 4.1.3 ... 7.7.7 (118 versions) | 7.8.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 23:26 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 21:36 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 19:11 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 17:17 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 15:25 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:30 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 13:35 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:47 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:56 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 19:06 UTCEG score recompute
- 2026-08-11 06:08 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 15:22 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:28 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
Show 15 moreShow fewer
- 2026-08-08 00:38 UTCEG score recompute
- 2026-08-06 22:48 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 20:57 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 19:06 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-02 15:18 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 00:33 UTCEG score recompute
- 2026-07-31 23:40 UTCEG score recompute
- 2026-07-31 19:23 UTCEG score recompute
- 2026-07-31 18:43 UTCEG score recompute
- 2026-07-31 18:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-53500?
When was CVE-2026-53500 disclosed?
Is CVE-2026-53500 actively exploited?
What is the CVSS score of CVE-2026-53500?
How do I remediate CVE-2026-53500?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53500
Is Your Infrastructure Affected by CVE-2026-53500?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.