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 | 2885 days past EOL | EOL |
| 3.0 | 3.0.12 | Jun 22, 2016 | Supported indefinitely | Supported | Active |
| 3.1 | 3.1.29 | Nov 2, 2016 | Supported indefinitely | Supported | Active |
| 3.2 | 3.2.18 | Jul 19, 2017 | Mar 31, 2019 | 2596 days past EOL | EOL |
| 3.3 | 3.3.25 | Dec 14, 2017 | Feb 29, 2020 | 2261 days past EOL | EOL |
| 3.4 | 3.4.11 | Dec 5, 2018 | Jun 21, 2020 | 2148 days past EOL | EOL |
| 3.5 | 3.5.7 | Aug 14, 2019 | Dec 31, 2020 | 1955 days past EOL | EOL |
| 3.6 | 3.6.16 | Dec 30, 2019 | Aug 31, 2021 | 1712 days past EOL | EOL |
| 3.7 | 3.7.18 | Apr 10, 2020 | May 31, 2022 | 1439 days past EOL | EOL |
| 3.8 | 3.8.9 | Jul 14, 2021 | Apr 30, 2023 | 1105 days past EOL | EOL |
| 3.9 | 3.9.12 | Feb 7, 2022 | Sep 15, 2023 | 967 days past EOL | EOL |
| 3.10 | 3.10.14 | Sep 29, 2022 | Apr 15, 2024 | 754 days past EOL | EOL |
| 3.11 | 3.11.14.4 | May 23, 2023 | Already EOL | Supported | Active |
| 3.12 | 3.12.9.1 | Mar 21, 2024 | Already EOL | Supported | Active |
When a Arangodb 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 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →