Redmine 6.0 · Version Status
Redmine 6.0 End of Life Date
Redmine 6.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Redmine 6.0 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
6.0.9
Standard release
Release Date
Nov 10, 2024
Redmine 6.0 series
| Version | Latest | EOL Date | Status |
|---|
| 4.0 |
4.0.9 |
Apr 26, 2021 |
EOL |
| 4.1 |
4.1.7 |
Mar 28, 2022 |
EOL |
| 4.2 |
4.2.11 |
Oct 31, 2023 |
EOL |
| 5.0 |
5.0.14 |
Sep 21, 2025 |
EOL |
| 5.1 |
5.1.12 |
EOL |
Active |
| → 6.0 |
6.0.9 |
EOL |
Active |
| 6.1 |
6.1.2 |
EOL |
Active |
What does Redmine 6.0 end of life mean?
When Redmine 6.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Redmine 6.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Redmine 6.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Redmine 6.0 reach end of life?
Redmine 6.0 has already reached end of life.
Is Redmine 6.0 still supported?
Yes, Redmine 6.0 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Redmine 6.0?
The recommended upgrade from Redmine 6.0 is
Redmine 6.1 — the latest actively supported version. Check the
Redmine full timeline for all supported versions.
What are the security risks of running Redmine 6.0 past EOL?
When Redmine 6.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Redmine should migrate immediately or implement compensating controls.