Complete end-of-life dates, support windows, and security status for all Drush versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5 | 5.11.0 | Mar 23, 2012 | May 31, 2015 | 3996 days past EOL | EOL |
| 6 | 6.7.0 | Aug 16, 2013 | Dec 31, 2015 | 3782 days past EOL | EOL |
| 7 | 7.4.2 | May 20, 2015 | Jul 31, 2017 | 3204 days past EOL | EOL |
| 8 | 8.5.0 | Nov 19, 2015 | Jan 31, 2025 | 463 days past EOL | EOL |
| 9 | 9.7.3 | Jan 24, 2018 | May 31, 2020 | 2169 days past EOL | EOL |
| 10 | 10.6.2 | Oct 31, 2019 | Jan 31, 2022 | 1559 days past EOL | EOL |
| 11 | 11.6.0 | Jan 11, 2022 | Nov 30, 2023 | 891 days past EOL | EOL |
| 12 | 12.5.3 | Jun 3, 2023 | Already EOL | Supported | Active |
| 13 | 13.7.2 | Aug 2, 2024 | Already EOL | Supported | Active |
When a Drush 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 Drush 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 →