Vue.js 1 · Version Status

Vue.js 1 End of Life Date

Vue.js 1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Vue.js 1 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
1.0.28
Standard release
Release Date
Oct 27, 2015
Vue.js 1 series
Lifecycle detail

Vue.js 1 was released on October 27, 2015. Its most recent patch is 1.0.28, published September 27, 2016.

All Vue.js versions Vue.js 2.0 →
55 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
20/30 High 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
Vue.js 3.5
Latest release: 3.5.41 · EOL: Supported
View full Vue.js timeline →
Extended Support
Extended Vue.js 1 support is available

Commercial vendors offer security patches beyond EOL. Right now that coverage spans Vue.js 2.x. Compare your options.

Compare Options →
All Vue.js Versions
VersionLatestEOL DateStatus
1 1.0.28 Supported EOL
2.0 2.0.8 Nov 22, 2016 EOL
2.1 2.1.10 Feb 26, 2017 EOL
2.2 2.2.6 Apr 27, 2017 EOL
2.3 2.3.4 Jul 13, 2017 EOL
2.4 2.4.4 Oct 13, 2017 EOL
2.5 2.5.22 Feb 4, 2019 EOL
2.6 2.6.14 Jul 1, 2022 EOL

What does Vue.js 1 end of life mean?

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

Migrate to Vue.js 3.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Vue.js 1 reach end of life?
Vue.js 1 has already reached end of life, though the vendor has not published an exact date.
Is Vue.js 1 still supported?
No. Vue.js 1 reached end of life on date not published and is no longer receiving security patches.
What should I upgrade to from Vue.js 1?
The recommended upgrade from Vue.js 1 is Vue.js 3.5 — the latest actively supported version. Check the Vue.js full timeline for all supported versions.
What are the security risks of running Vue.js 1 past EOL?
When Vue.js 1 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 Vue.js should migrate immediately or implement compensating controls.
Deep Dive
Full Guide
Vue 2 End of Life: EOL Date, Risk, and Migration to Vue 3
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
ReactAngularNode.jsNuxt.js