Arangodb 2.8 · Version Status
Arangodb 2.8 End of Life Date
Arangodb 2.8 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Arangodb 2.8 is past end of life. This version no longer receives security patches. 2885 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 15, 2018
2885 days past EOL
Latest Release
2.8.11
Standard release
Release Date
Jan 25, 2016
Arangodb 2.8 series
| Version | Latest | EOL Date | Status |
|---|
| → 2.8 |
2.8.11 |
Jun 15, 2018 |
EOL |
| 3.0 |
3.0.12 |
Supported |
Active |
| 3.1 |
3.1.29 |
Supported |
Active |
| 3.2 |
3.2.18 |
Mar 31, 2019 |
EOL |
| 3.3 |
3.3.25 |
Feb 29, 2020 |
EOL |
| 3.4 |
3.4.11 |
Jun 21, 2020 |
EOL |
| 3.5 |
3.5.7 |
Dec 31, 2020 |
EOL |
| 3.6 |
3.6.16 |
Aug 31, 2021 |
EOL |
What does Arangodb 2.8 end of life mean?
When Arangodb 2.8 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Arangodb 2.8 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Arangodb 3.12 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Arangodb 2.8 reach end of life?
Arangodb 2.8 reached end of life on June 15, 2018. This version is no longer receiving security patches.
Is Arangodb 2.8 still supported?
No. Arangodb 2.8 reached end of life on June 15, 2018 and is no longer receiving security patches.
What should I upgrade to from Arangodb 2.8?
The recommended upgrade from Arangodb 2.8 is
Arangodb 3.12 — the latest actively supported version. Check the
Arangodb full timeline for all supported versions.
What are the security risks of running Arangodb 2.8 past EOL?
When Arangodb 2.8 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Arangodb should migrate immediately or implement compensating controls.