Complete end-of-life dates, support windows, and security status for all Redmine versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.0 | 4.0.9 | Dec 9, 2018 | Apr 26, 2021 | 1839 days past EOL | EOL |
| 4.1 | 4.1.7 | Dec 20, 2019 | Mar 28, 2022 | 1503 days past EOL | EOL |
| 4.2 | 4.2.11 | Mar 28, 2021 | Oct 31, 2023 | 921 days past EOL | EOL |
| 5.0 | 5.0.14 | Mar 28, 2022 | Sep 21, 2025 | 230 days past EOL | EOL |
| 5.1 | 5.1.12 | Oct 31, 2023 | Already EOL | Supported | Active |
| 6.0 | 6.0.9 | Nov 10, 2024 | Already EOL | Supported | Active |
| 6.1 | 6.1.2 | Sep 21, 2025 | Already EOL | Supported | Active |
When a Redmine 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 Redmine 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 →