Vue 2 end of life
Vue 2 reached end of life on 31 December 2023. Vue 2.7 "Naruto" was the last minor release and 2.7.16 "Swan Song" (24 December 2023) the last release overall, so no Vue 2 release has fixed anything since. Vue 2 stays on npm and CDNs but gets no security or browser compatibility fixes. You can migrate to Vue 3 or keep Vue 2.7 patched with third-party security support.
What now
Which vendors provide Vue 2 security patches now that support has ended?
Vue extended support- End of life
- 31 December 2023
- Released
- Sept 2016
- Final release
- 2.7.16 (24 December 2023)
- Successor
- Vue 3
Date published by Vue 2 LTS, EOL & Extended Support (vuejs.org). We do not publish a lifecycle date we cannot source. Dates checked on v2.vuejs.org, GitHub releases and endoflife.date on 19 November 2026.
Last reviewed
Vue versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Vue 2 (this page) | 30 Sept 2016 | 31 December 2023 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 December 2023
- Security fixes. The Vue 2 LTS page says that after 31 December 2023 Vue 2 stays available in all existing distribution channels but no longer receives updates, including security and browser compatibility fixes.
- Releases on the 2.x line. 2.7.16 "Swan Song" (24 December 2023) is the last, and 2.7 was the final minor.
- Triage of new reports against Vue 2. CVE-2024-6783 (July 2024) and CVE-2024-9506 (October 2024) were published after the end date and list Vue up to 2.7.16 as affected, with no Vue 2 fix.
- Nothing stops on the day for your running application: Vue 2 keeps working. What ends is the supply of fixes.
What actually breaks in the upgrade
If you are on 2.6 or older, move to 2.7 first
The Vue 2 LTS page says that teams staying on Vue 2 should at least be on 2.7, the maintained release before end of life. 2.7 also backports the Composition API and script setup from Vue 3, so a codebase can adopt Vue 3 patterns before it moves.
What blocks the move to Vue 3
The Vue 3 migration guide lists the blockers: dependencies that use Vue 2 internals or private VNode properties, component libraries such as Vuetify, Quasar or ElementUI without a Vue 3 version, a custom server-side rendering setup built on vue-server-renderer, and Internet Explorer 11, which Vue 3 does not support. Teams that must support IE11 have to stay on Vue 2. Vue 3 migration build (@vue/compat).
The migration build lets you move in steps
@vue/compat is a build of Vue 3 that runs in Vue 2 mode by default and warns about each behaviour that changed. Compatibility can be switched on and off per component, so a large application does not have to move in one release.
Vue 2 CVEs published after end of life
Both records were checked on cveawg.mitre.org and in the GitHub advisory on 19 November 2026. The CVE records list Vue up to 2.7.16 as affected, and the GitHub advisories agree: no patched Vue 2 version exists for CVE-2024-6783, and for CVE-2024-9506 the first patched version is 3.0.0-alpha.0. This is every Vue 2 CVE we could confirm, not a claim that none exist.
| CVE | What it is | Severity (CVSS 3.1) | Published | Fixed in a Vue 2 release |
|---|---|---|---|---|
| CVE-2024-6783 | Cross-site scripting through prototype pollution of Object.prototype.staticClass and staticStyle (the GitHub advisory is filed against vue-template-compiler) | Medium (4.8) | 23 Jul 2024 | None |
| CVE-2024-9506 | Regular-expression denial of service in the parseHTML function of the template compiler | Low (3.7) | 15 Oct 2024 | None |
Both flaws sit in template-compilation code. An application that precompiles its templates at build time and never compiles user-controlled template strings in the browser has a narrower exposure. A scanner will flag the library either way.
Who patches Vue 2 after end of life?
The Vue 2 LTS page itself points teams that expect to run Vue 2 past end of life to HeroDevs' Never-Ending Support for Vue 2 (read on 19 November 2026). OSSeva is another option. The table lists what each provider's own page says.
Facts from the Vue 2 LTS page and each provider's own page, read on 19 November 2026. Nothing here comes from a third party.
| Provider | Vue versions the page lists | Fix timing the page states |
|---|---|---|
| HeroDevs (NES for Vue 2) | Vue 2.x, with the same two CVEs listed as fixed | FAQ says security issues are top priority and fixed the same day where possible; SLA on request |
| OSSeva | Vue 2.7. Other versions case by case | Critical within 48 hours, High within 7 days |
How we compared: HeroDevs' row uses only its own Vue 2 page, read on 19 November 2026, and the fix-timing column reports the timing each provider names, which are different measures. Where HeroDevs is the better fit: it is the provider the Vue 2 LTS page names, and its page lists Vue 2.x without limiting it to 2.7.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Migrate to Vue 3 | Move to the current major, using the migration build to go component by component. | Scales with dependencies, SSR setup and test coverage | Engineering time | The default destination, where no blocker applies. |
| Upgrade to Vue 2.7 and adopt Vue 3 patterns | Take the Composition API and script setup on 2.7 and migrate later. | Small for a 2.6 codebase | Engineering time | A sensible first step, but 2.7 gets no fixes either. |
| Extended security support | Backported fixes for Vue 2.7 after end of life: Critical CVEs within 48 hours, High within 7 days. | Starts from your current version | Subscription, priced per application | For applications held by IE11, a component library or a release freeze. |
| Stay unpatched | No fixes for newly found vulnerabilities, and CVE-2024-6783 and CVE-2024-9506 stay open. | None | Zero now | Both known CVEs are low to medium, but scanners and auditors flag end-of-life libraries regardless. |
What OSSeva does for Vue 2
OSSeva patches this line
OSSeva patches Vue 2.7 after end of life. Other Vue versions, including 2.6 and older, are assessed case by case through a version coverage check.
Vue extended supportWhat your auditor will say
Requirement 6.3.3. Payment pages on an end-of-life front-end library need patched components or a documented compensating control.
CC7.1. Auditors look for evidence that production dependencies receive security fixes.
Is Vue 2 end of life?
Yes. Vue 2 reached end of life on 31 December 2023, per the Vue 2 LTS page. 2.7.16, released on 24 December 2023, was the last release.
When did Vue 2 reach end of life?
31 December 2023. Vue 2.7 had received 18 months of long-term support from its release on 1 July 2022, and the Vue team has shipped nothing for Vue 2 since 2.7.16.
What was the last Vue 2 version?
Vue 2.7.16, named "Swan Song", released on 24 December 2023. Vue 2.7 "Naruto" (1 July 2022) was the last minor release.
Is Vue 2 still safe to use?
It keeps working, and the Vue 2 LTS page notes it has been stable and battle-tested. It receives no fixes, though: CVE-2024-6783 and CVE-2024-9506 were published after end of life and have no Vue 2 fix.
Can I get security patches for Vue 2 after end of life?
Not from the Vue team. The Vue 2 LTS page points to HeroDevs' Never-Ending Support, and third parties including OSSeva backport fixes to Vue 2.7.
Should I upgrade Vue 2 to Vue 3?
Usually yes, if no blocker applies. IE11 support, component libraries without a Vue 3 version and custom server-side rendering are the common blockers, and the migration build helps move in steps.
Get a quote
Still running Vue 2?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?