Complete end-of-life dates, support windows, and security status for all Akeneo Pim versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.1 | 1.1.3 | Apr 16, 2014 | Jul 22, 2014 | 4309 days past EOL | EOL |
| 1.2 | 1.2.37 | Aug 28, 2014 | Aug 18, 2015 | 3917 days past EOL | EOL |
| 1.3 | 1.3.41 | Feb 15, 2015 | Sep 30, 2016 | 3508 days past EOL | EOL |
| 1.4 | 1.4.28 | Sep 15, 2015 | Mar 31, 2017 | 3326 days past EOL | EOL |
| 1.5 | 1.5.27 | Mar 15, 2016 | Sep 30, 2017 | 3143 days past EOL | EOL |
| 1.6 | 1.6.23 | Sep 15, 2016 | Mar 31, 2018 | 2961 days past EOL | EOL |
| 1.7 | 1.7.41 | Mar 14, 2017 | Apr 30, 2019 | 2566 days past EOL | EOL |
| 2.0 | 2.0.52 | Sep 28, 2017 | Apr 30, 2019 | 2566 days past EOL | EOL |
| 3.0 | 3.0.84 | Jan 31, 2019 | Aug 31, 2020 | 2077 days past EOL | EOL |
| 3.1 | 3.1.18 | May 2, 2019 | Jul 20, 2019 | 2485 days past EOL | EOL |
| 3.2 | 3.2.84 | Jul 31, 2019 | May 31, 2021 | 1804 days past EOL | EOL |
| 4.0 | 4.0.126 | Feb 6, 2020 | Aug 31, 2021 | 1712 days past EOL | EOL |
| 5.0 | 5.0.120 | Mar 9, 2021 | Sep 30, 2022 | 1317 days past EOL | EOL |
| 6.0 | 6.0.113 | Mar 15, 2022 | Sep 30, 2023 | 952 days past EOL | EOL |
| 7.0 | 7.0.84 | Mar 8, 2023 | Sep 30, 2026 | 144 days remaining | Warning |
| 2026.3 | 2026.3 | Mar 30, 2026 | Already EOL | Supported | Active |
When a Akeneo Pim 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 Akeneo Pim 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 →