Drush · Lifecycle Status

Drush End of Life (EOL) Dates & Support Timeline

Q: What is the latest supported version of Drush?

The latest active version of Drush is 13.7.3. Always verify against the table above as support windows can change.

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.

Latest Active

13.7.3

13 series

Next EOL

—

None upcoming

Active Versions

of 9 total

EOL Versions

no longer patched

Medium Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

35/40

Attack Surface

10/30 Medium tier

CISA KEV Exposure

0/20 Not in KEV

Extended Support

0/10 Available

EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
5	5.11.0	Mar 23, 2012	May 31, 2015	4041 days past EOL	EOL
6	6.7.0	Aug 16, 2013	Dec 31, 2015	3827 days past EOL	EOL
7	7.4.2	May 20, 2015	Jul 31, 2017	3249 days past EOL	EOL
8	8.5.0	Nov 19, 2015	Jan 31, 2025	508 days past EOL	EOL
9	9.7.3	Jan 24, 2018	May 31, 2020	2214 days past EOL	EOL
10	10.6.2	Oct 31, 2019	Jan 31, 2022	1604 days past EOL	EOL
11	11.6.0	Jan 11, 2022	Nov 30, 2023	936 days past EOL	EOL
12	12.5.3	Jun 3, 2023	TBD	Supported	Active
13	13.7.3	Aug 2, 2024	TBD	Supported	Active

What does Drush end of life mean for your organization?

When a version of Drush 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.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Drush versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai

Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Frequently Asked Questions

What is the end-of-life date for Drush?

See the full table above for all Drush version EOL dates.

When is the Drush support end date?

Each Drush version has its own support end date — see the table above for every version's date.

What is the latest supported version of Drush?

The latest active version of Drush is 13.7.3. Always verify against the table above as support windows can change.

What happens when Drush reaches end of life?

When Drush reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of Drush?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL Drush versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →