Vue · Lifecycle Status

Vue End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Vue versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Vue 1.0.28 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.0.28
1 series
Next EOL
None upcoming
Active Versions
2
of 15 total
EOL Versions
13
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2016201720182019202020212022202320242025202612.02.12.22.32.42.52.63.03.13.22.73.33.43.5TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1 1.0.28 Oct 27, 2015 Supported indefinitely Supported Active
2.0 2.0.8 Sep 30, 2016 Nov 22, 2016 3455 days past EOL EOL
2.1 2.1.10 Nov 22, 2016 Feb 26, 2017 3359 days past EOL EOL
2.2 2.2.6 Feb 26, 2017 Apr 27, 2017 3299 days past EOL EOL
2.3 2.3.4 Apr 27, 2017 Jul 13, 2017 3222 days past EOL EOL
2.4 2.4.4 Jul 13, 2017 Oct 13, 2017 3130 days past EOL EOL
2.5 2.5.22 Oct 13, 2017 Feb 4, 2019 2651 days past EOL EOL
2.6 2.6.14 Feb 4, 2019 Jul 1, 2022 1408 days past EOL EOL
3.0 3.0.11 Sep 18, 2020 Jun 7, 2021 1797 days past EOL EOL
3.1 3.1.5 Jun 7, 2021 Aug 9, 2021 1734 days past EOL EOL
3.2 3.2.47 Aug 9, 2021 May 11, 2023 1094 days past EOL EOL
2.7 2.7.16 Jul 1, 2022 Dec 31, 2023 860 days past EOL EOL
3.3 3.3.13 May 11, 2023 Dec 29, 2023 862 days past EOL EOL
3.4 3.4.38 Dec 29, 2023 Sep 3, 2024 613 days past EOL EOL
3.5 3.5.34 Sep 3, 2024 Already EOL Supported Active

What does Vue end of life mean for your organization?

When a Vue 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 Vue 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 Vue versions. This is a bridge, not a permanent solution — plan your migration in parallel.

HeroDevs
Extended Vue Support

Never-Ending Support for Vue 2 — patched, secure, drop-in compatible.

Learn More →
endoflife.ai
Check Your Full Stack

Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.

Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Vue?
See the full table above for all Vue version EOL dates.
What is the latest supported version of Vue?
The latest active version of Vue is 1.0.28. Always verify against the table above as support windows can change.
What happens when Vue reaches end of life?
When Vue 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 Vue?
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 Vue versions?
Yes — HeroDevs offers extended support for EOL Vue versions, providing continued security patches while you plan your migration.

Related Products

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