← ← Back to all products
All badges & lifecycle API →
Akeneo PIMEnd of Life (EOL) Dates & Support Status
Active
CMS & ContentLatest Version: 7.0.87Latest Release: Sep 25, 2026
Akeneo PIM is an open-source Product Information Management system for centralizing product data.
Support summary
Akeneo PIM 7.0 reaches EOL in 3 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Sep 30, 2026
Akeneo PIM 7.0 · 3 days left
Supported cycles
2
0 lts
Versions
17
Latest Version
7.0.87
Active Support
2
EOL
15
Lifecycle Timeline
Sep 28, 2017As of Sep 27, 2026
2026.4Active · Date not announced
2026.3EOL · Aug 28, 2026
7.0Active · Sep 30, 2026
6.0EOL · Sep 30, 2023
5.0EOL · Sep 30, 2022
4.0EOL · Aug 31, 2021
3.2EOL · May 31, 2021
3.1EOL · Jul 20, 2019
3.0EOL · Aug 31, 2020
2.0EOL · Apr 30, 2019
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2026.4 | Aug 28, 2026 | Maintained | Date not announced | 2026.4 | No | Active |
| 2026.3 | Mar 30, 2026 | Ended | Aug 28, 2026 | 2026.3 | No | EOL |
| 7.0Sahara hare | Mar 8, 2023 | Maintained | Sep 30, 2026 | 7.0.87 | No | Active |
| 6.0Buccaneer Bunny | Mar 15, 2022 | Ended | Sep 30, 2023 | 6.0.113 | No | EOL |
| 5.0Bully for Bugs | Mar 9, 2021 | Ended | Sep 30, 2022 | 5.0.120 | No | EOL |
| 4.0Hare Tonic | Feb 6, 2020 | Ended | Aug 31, 2021 | 4.0.126 | No | EOL |
| 3.2Rabbit Transit | Jul 31, 2019 | Ended | May 31, 2021 | 3.2.84 | No | EOL |
| 3.1Slick Hare | May 2, 2019 | Ended | Jul 20, 2019 | 3.1.18 | No | EOL |
| 3.0Super-Rabbit | Jan 31, 2019 | Ended | Aug 31, 2020 | 3.0.84 | No | EOL |
| 2.0Rebel Rabbit | Sep 28, 2017 | Ended | Apr 30, 2019 | 2.0.52 | No | EOL |
| 1.7The Old Grey Hare | Mar 14, 2017 | Ended | Apr 30, 2019 | 1.7.41 | No | EOL |
| 1.6Wackiki Wabbit | Sep 15, 2016 | Ended | Mar 31, 2018 | 1.6.23 | No | EOL |
| 1.5Fresh Hare | Mar 15, 2016 | Ended | Sep 30, 2017 | 1.5.27 | No | EOL |
| 1.4Rhapsody Rabbit | Sep 15, 2015 | Ended | Mar 31, 2017 | 1.4.28 | No | EOL |
| 1.3Hare Force | Feb 15, 2015 | Ended | Sep 30, 2016 | 1.3.41 | No | EOL |
| 1.2Acrobatty Bunny | Aug 28, 2014 | Ended | Aug 18, 2015 | 1.2.37 | No | EOL |
| 1.1Rabbit Punch | Apr 16, 2014 | Ended | Jul 22, 2014 | 1.1.3 | No | EOL |
Data sources
Embed this badge
Show Akeneo PIM's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/akeneo-pim/)HTML
<a href="https://eol.wiki/akeneo-pim/"><img src="https://eol.wiki/badge/akeneo-pim.svg" alt="Akeneo PIM end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Akeneo PIM have reached end of life?
The following Akeneo PIM versions have reached end of life and no longer receive security updates: 2026.3, 6.0, 5.0, 4.0, 3.2, 3.1, 3.0, 2.0 (and 7 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Akeneo PIM 2026.3?
Akeneo PIM 2026.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Akeneo PIM?
The latest version of Akeneo PIM is 7.0.87, released in the 7.0 release cycle.
How many versions of Akeneo PIM are currently supported?
Akeneo PIM currently has 2 actively supported version(s): 2026.4, 7.0.
When does Akeneo PIM 2026.4 reach end of life?
Akeneo PIM 2026.4 does not have a specific end-of-life date announced yet.
What should I do when Akeneo PIM reaches end of life?
When a Akeneo PIM version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.