Fairphone End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Fairphone versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Fairphone 1 | — | Dec 1, 2013 | Jul 13, 2017 | 3314 days past EOL | EOL |
| Fairphone 2 | — | Dec 21, 2015 | Mar 7, 2023 | 1251 days past EOL | EOL |
| Fairphone 3 | — | Sep 30, 2019 | Sep 30, 2026 | 52 days remaining | Warning |
| Fairphone 3+ | — | Sep 30, 2020 | Sep 30, 2026 | 52 days remaining | Warning |
| Fairphone 4 | — | Sep 30, 2021 | Sep 1, 2028 | 754 days remaining | Active |
| Fairphone 5 | — | Sep 14, 2023 | Sep 14, 2031 | 1862 days remaining | Active |
| Fairphone 6 | — | Jun 25, 2025 | Jun 25, 2033 | 2512 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fairphone)
What does Fairphone end of life mean for your organization?
When a version of Fairphone 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 Fairphone 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.
Your options when Fairphone reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Fairphone from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →