Complete end-of-life dates, support windows, and security status for all Thumbor versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.0 | 7.0.12 | Feb 27, 2020 | Jul 27, 2022 | 1382 days past EOL | EOL |
| 7.1 | 7.1.2 | Jul 27, 2022 | Oct 20, 2022 | 1297 days past EOL | EOL |
| 7.2 | 7.2.1 | Oct 20, 2022 | Nov 1, 2022 | 1285 days past EOL | EOL |
| 7.3 | 7.3.2 | Nov 1, 2022 | Dec 22, 2022 | 1234 days past EOL | EOL |
| 7.4 | 7.4.7 | Dec 20, 2022 | May 29, 2023 | 1076 days past EOL | EOL |
| 7.5 | 7.5.2 | May 29, 2023 | Oct 9, 2023 | 943 days past EOL | EOL |
| 7.6 | 7.6.0 | Oct 9, 2023 | Oct 31, 2023 | 921 days past EOL | EOL |
| 7.7 | 7.7.7 | Oct 31, 2023 | Already EOL | Supported | Active |
When a Thumbor version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Thumbor should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →