Electron End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Electron versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2 | 2.0.18 | May 1, 2018 | Apr 23, 2019 | 2665 days past EOL | EOL |
| 3 | 3.1.13 | Sep 18, 2018 | Jul 30, 2019 | 2567 days past EOL | EOL |
| 4 | 4.2.12 | Dec 20, 2018 | Oct 22, 2019 | 2483 days past EOL | EOL |
| 5 | 5.0.13 | Apr 23, 2019 | Feb 4, 2020 | 2378 days past EOL | EOL |
| 6 | 6.1.12 | Jul 30, 2019 | May 19, 2020 | 2273 days past EOL | EOL |
| 7 | 7.3.3 | Oct 22, 2019 | Aug 25, 2020 | 2175 days past EOL | EOL |
| 8 | 8.5.5 | Feb 4, 2020 | Nov 17, 2020 | 2091 days past EOL | EOL |
| 9 | 9.4.4 | May 19, 2020 | Mar 2, 2021 | 1986 days past EOL | EOL |
| 10 | 10.4.7 | Aug 25, 2020 | May 25, 2021 | 1902 days past EOL | EOL |
| 11 | 11.5.0 | Nov 17, 2020 | Aug 31, 2021 | 1804 days past EOL | EOL |
| 12 | 12.2.3 | Mar 2, 2021 | Nov 16, 2021 | 1727 days past EOL | EOL |
| 13 | 13.6.9 | May 25, 2021 | Feb 1, 2022 | 1650 days past EOL | EOL |
| 14 | 14.2.9 | Aug 31, 2021 | Mar 29, 2022 | 1594 days past EOL | EOL |
| 15 | 15.5.7 | Sep 21, 2021 | May 24, 2022 | 1538 days past EOL | EOL |
| 16 | 16.2.8 | Nov 16, 2021 | May 24, 2022 | 1538 days past EOL | EOL |
| 17 | 17.4.11 | Feb 1, 2022 | Aug 2, 2022 | 1468 days past EOL | EOL |
| 18 | 18.3.15 | Mar 29, 2022 | Sep 27, 2022 | 1412 days past EOL | EOL |
| 19 | 19.1.9 | May 24, 2022 | Nov 29, 2022 | 1349 days past EOL | EOL |
| 20 | 20.3.12 | Aug 2, 2022 | Feb 7, 2023 | 1279 days past EOL | EOL |
| 21 | 21.4.4 | Sep 27, 2022 | Apr 4, 2023 | 1223 days past EOL | EOL |
| 22 | 22.3.27 | Nov 29, 2022 | Oct 10, 2023 | 1034 days past EOL | EOL |
| 23 | 23.3.13 | Feb 7, 2023 | Aug 15, 2023 | 1090 days past EOL | EOL |
| 24 | 24.8.8 | Apr 4, 2023 | Oct 10, 2023 | 1034 days past EOL | EOL |
| 25 | 25.9.8 | May 30, 2023 | Dec 5, 2023 | 978 days past EOL | EOL |
| 26 | 26.6.10 | Aug 15, 2023 | Feb 20, 2024 | 901 days past EOL | EOL |
| 27 | 27.3.11 | Oct 10, 2023 | Apr 16, 2024 | 845 days past EOL | EOL |
| 28 | 28.3.3 | Dec 5, 2023 | Jun 11, 2024 | 789 days past EOL | EOL |
| 29 | 29.4.6 | Feb 20, 2024 | Aug 20, 2024 | 719 days past EOL | EOL |
| 30 | 30.5.1 | Apr 16, 2024 | Oct 15, 2024 | 663 days past EOL | EOL |
| 31 | 31.7.7 | Jun 11, 2024 | Jan 14, 2025 | 572 days past EOL | EOL |
| 32 | 32.3.3 | Aug 20, 2024 | Mar 4, 2025 | 523 days past EOL | EOL |
| 33 | 33.4.11 | Oct 15, 2024 | Apr 29, 2025 | 467 days past EOL | EOL |
| 34 | 34.5.8 | Jan 14, 2025 | Jun 24, 2025 | 411 days past EOL | EOL |
| 35 | 35.7.5 | Mar 4, 2025 | Sep 2, 2025 | 341 days past EOL | EOL |
| 36 | 36.9.5 | Apr 29, 2025 | Oct 28, 2025 | 285 days past EOL | EOL |
| 37 | 37.10.3 | Jun 24, 2025 | Jan 13, 2026 | 208 days past EOL | EOL |
| 38 | 38.8.6 | Sep 2, 2025 | Mar 10, 2026 | 152 days past EOL | EOL |
| 39 | 39.8.10 | Oct 28, 2025 | May 5, 2026 | 96 days past EOL | EOL |
| 40 | 40.10.6 | Jan 13, 2026 | Jun 30, 2026 | 40 days past EOL | EOL |
| 41 | 41.10.4 | Mar 10, 2026 | Aug 25, 2026 | 16 days remaining | Warning |
| 42 | 42.8.1 | May 5, 2026 | Oct 20, 2026 | 72 days remaining | Warning |
| 43 | 43.3.0 | Jun 30, 2026 | Jan 5, 2027 | 149 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/electron)
What does Electron end of life mean for your organization?
When a version of Electron 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 Electron 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 Electron 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 |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Electron versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Electron has 39 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Electron exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.