Redmine 3.3 · Version Status
Redmine 3.3 End of Life Date
Redmine 3.3 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Redmine 3.3 is past end of life. This version no longer receives security patches. 2546 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 18, 2019
2546 days past EOL
Latest Release
3.3.10
Standard release
Release Date
Jun 19, 2016
Redmine 3.3 series
Where these dates come from
End of lifeNov 18, 2019endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJun 19, 2016endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Redmine 3.3 was released on June 19, 2016 and support ended on November 18, 2019 — a supported lifespan of 3 years and 5 months, longer than the 2 years and 8 months median for Redmine releases. Its latest release on record is 3.3.10, published November 18, 2019 — on the day support ended. It has been past its end-of-life date for 7 years. 7 newer Redmine releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Redmine 3.3 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| → 3.3 |
3.3.10 |
Nov 18, 2019 |
EOL |
| 3.4 |
3.4.13 |
Apr 6, 2020 |
EOL |
| 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.13 |
Jun 30, 2026 |
EOL |
| 6.0 |
6.0.12 |
EOL |
Active |
What does Redmine 3.3 end of life mean?
When Redmine 3.3 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Redmine 3.3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Redmine 7.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Redmine 3.3 reach end of life?
Redmine 3.3 reached end of life on November 18, 2019. This version is no longer receiving security patches.
Is Redmine 3.3 still supported?
No. Redmine 3.3 reached end of life on November 18, 2019 and is no longer receiving security patches.
What should I upgrade to from Redmine 3.3?
The recommended upgrade from Redmine 3.3 is
Redmine 7.0 — the latest actively supported version. Check the
Redmine full timeline for all supported versions.
What are the security risks of running Redmine 3.3 past EOL?
Since Redmine 3.3 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Redmine should migrate immediately or implement compensating controls.