ArangoDB End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all ArangoDB versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.8 | 2.8.11 | Jan 25, 2016 | Jun 15, 2018 | 2930 days past EOL | EOL |
| 3.0 | 3.0.12 | Jun 22, 2016 | No EOL date | Supported | Active |
| 3.1 | 3.1.29 | Nov 2, 2016 | No EOL date | Supported | Active |
| 3.2 | 3.2.18 | Jul 19, 2017 | Mar 31, 2019 | 2641 days past EOL | EOL |
| 3.3 | 3.3.25 | Dec 14, 2017 | Feb 29, 2020 | 2306 days past EOL | EOL |
| 3.4 | 3.4.11 | Dec 5, 2018 | Jun 21, 2020 | 2193 days past EOL | EOL |
| 3.5 | 3.5.7 | Aug 14, 2019 | Dec 31, 2020 | 2000 days past EOL | EOL |
| 3.6 | 3.6.16 | Dec 30, 2019 | Aug 31, 2021 | 1757 days past EOL | EOL |
| 3.7 | 3.7.18 | Apr 10, 2020 | May 31, 2022 | 1484 days past EOL | EOL |
| 3.8 | 3.8.9 | Jul 14, 2021 | Apr 30, 2023 | 1150 days past EOL | EOL |
| 3.9 | 3.9.12 | Feb 7, 2022 | Sep 15, 2023 | 1012 days past EOL | EOL |
| 3.10 | 3.10.14 | Sep 29, 2022 | Apr 15, 2024 | 799 days past EOL | EOL |
| 3.11 | 3.11.14.4 | May 23, 2023 | TBD | Supported | Active |
| 3.12 | 3.12.9.3 | Mar 21, 2024 | TBD | Supported | Active |
What does ArangoDB end of life mean for your organization?
When a version of ArangoDB 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 ArangoDB 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL ArangoDB versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →