Drush 11 · Version Status

Drush 11 End of Life Date

Drush 11 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

⚠ Drush 11 is past end of life. This version no longer receives security patches. 1073 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 30, 2023
1073 days past EOL
Latest Release
11.6.0
Standard release
Release Date
Jan 11, 2022
Drush 11 series
Where these dates come from
End of lifeNov 30, 2023endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
ReleaseJan 11, 2022endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Drush 11 was released on January 11, 2022 and support ended on November 30, 2023 — a supported lifespan of 1 year and 11 months, shorter than the 2 years and 4 months median for Drush releases. Its latest release on record is 11.6.0, published June 6, 2023 — 6 months before support ended. It has been past its end-of-life date for 2 years and 11 months. 1 newer Drush release has shipped since.

← Drush 10 All Drush versions Drush 12 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/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 →  ·  View score card →
Recommended upgrade path
Drush 13
Latest release: 13.8.0 · EOL: Supported
View full Drush timeline →
Extended Support
Extended Drush 11 support options

Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.

Compare Options →
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 11 end of life mean?

When Drush 11 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Drush 11 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does Drush 11 reach end of life?
Drush 11 reached end of life on November 30, 2023. This version is no longer receiving security patches.
Is Drush 11 still supported?
No. Drush 11 reached end of life on November 30, 2023 and is no longer receiving security patches.
What should I upgrade to from Drush 11?
The recommended upgrade from Drush 11 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 11 past EOL?
Since Drush 11 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Drush should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →