Akeneo PIM 2.0 · Version Status

Akeneo PIM 2.0 End of Life Date

Akeneo PIM 2.0 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.

⚠ Akeneo PIM 2.0 is past end of life. This version no longer receives security patches. 2727 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 30, 2019
2727 days past EOL
Latest Release
2.0.52
Standard release
Release Date
Sep 28, 2017
Akeneo PIM 2.0 series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Akeneo PIM 2.0 was released on September 28, 2017 and support ended on April 30, 2019 — a supported lifespan of 1 year and 7 months, in line with the 1 year and 7 months median for Akeneo PIM releases. The last patch it will ever receive is 2.0.52, published April 23, 2019 — 7 days before support ended. It has been without security patches for 7 years and 6 months. 8 newer Akeneo PIM releases have shipped since.

← Akeneo PIM 1.7 All Akeneo PIM versions Akeneo PIM 3.0 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
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 →
Recommended upgrade path
Akeneo PIM 2026.4
Latest release: 2026.4 · EOL: Supported
View full Akeneo PIM timeline →
Extended Support
Extended Akeneo PIM 2.0 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Akeneo PIM Versions
VersionLatestEOL DateStatus
1.1 1.1.3 Jul 22, 2014 EOL
1.2 1.2.37 Aug 18, 2015 EOL
1.3 1.3.41 Sep 30, 2016 EOL
1.4 1.4.28 Mar 31, 2017 EOL
1.5 1.5.27 Sep 30, 2017 EOL
1.6 1.6.23 Mar 31, 2018 EOL
1.7 1.7.41 Apr 30, 2019 EOL
→ 2.0 2.0.52 Apr 30, 2019 EOL

What does Akeneo PIM 2.0 end of life mean?

When Akeneo PIM 2.0 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 Akeneo PIM 2.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Akeneo PIM 2026.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Akeneo PIM 2.0 reach end of life?
Akeneo PIM 2.0 reached end of life on April 30, 2019. This version is no longer receiving security patches.
Is Akeneo PIM 2.0 still supported?
No. Akeneo PIM 2.0 reached end of life on April 30, 2019 and is no longer receiving security patches.
What should I upgrade to from Akeneo PIM 2.0?
The recommended upgrade from Akeneo PIM 2.0 is Akeneo PIM 2026.4 — the latest actively supported version. Check the Akeneo PIM full timeline for all supported versions.
What are the security risks of running Akeneo PIM 2.0 past EOL?
When Akeneo PIM 2.0 reaches end of life, the maintainers stop issuing 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 Akeneo PIM should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →