Drush 6 · Version Status

Drush 6 End of Life Date

Drush 6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Drush 6 is past end of life. This version no longer receives security patches. 3782 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2015
3782 days past EOL
Latest Release
6.7.0
Standard release
Release Date
Aug 16, 2013
Drush 6 series
← Drush 5 All Drush versions Drush 7 →
Recommended upgrade path
Drush 13
Latest release: 13.7.2 · EOL: Supported
View full Drush timeline →
All Drush Versions
VersionLatestEOL DateStatus
5 5.11.0 May 31, 2015 EOL
6 6.7.0 Dec 31, 2015 EOL
7 7.4.2 Jul 31, 2017 EOL
8 8.5.0 Jan 31, 2025 EOL
9 9.7.3 May 31, 2020 EOL
10 10.6.2 Jan 31, 2022 EOL
11 11.6.0 Nov 30, 2023 EOL
12 12.5.3 EOL Active

What does Drush 6 end of life mean?

When Drush 6 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 Drush 6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Drush 13 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

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