Vulnerability Database · npm · Package report

vue-template-compiler: vulnerability history, versions and safety

vue-template-compiler is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Jul 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on vue-template-compiler 2.7.16 i

Updated on 23 Oct 2026

Action needed: 2.7.16 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 2.7.16 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 23 Jul 2024 i
  • Highest CVSS 4.2 i
  • With no published fix 0 i
  • Depended on by 14,083 packages i
  • Stars 212,693 i
  • OpenSSF scorecard 2/10 i
  • Last release 33 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for vue-template-compiler, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.7.16 24 Dec 2023 M1 MIT Yes Details →
2.7.16-beta.2 14 Dec 2023 M1 MIT Yes Details →
2.7.16-beta.1 08 Dec 2023 M1 MIT Yes Details →
2.7.15 23 Oct 2023 M1 MIT Yes Details →
2.7.14 09 Nov 2022 M1 MIT Yes Details →
2.7.13 14 Oct 2022 M1 MIT Yes Details →
2.7.12 12 Oct 2022 M1 MIT Yes Details →
2.7.11 11 Oct 2022 M1 MIT Yes Details →
2.7.10 23 Aug 2022 M1 MIT Yes Details →
2.7.9 19 Aug 2022 M1 MIT Yes Details →
2.7.8 22 Jul 2022 M1 MIT Yes Details →
2.7.7 16 Jul 2022 M1 MIT Yes Details →
2.7.6 15 Jul 2022 M1 MIT Yes Details →
2.7.5 13 Jul 2022 M1 MIT Yes Details →
2.7.4 08 Jul 2022 M1 MIT Yes Details →
2.7.3 06 Jul 2022 M1 MIT Yes Details →
2.7.2 05 Jul 2022 M1 MIT Yes Details →
2.7.1 04 Jul 2022 M1 MIT Yes Details →
2.7.0 01 Jul 2022 M1 MIT Yes Details →
2.7.0-beta.8 28 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.7 27 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.6 26 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.5 22 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.4 21 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.3 20 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.2 17 Jun 2022 M1 MIT Yes Details →
2.7.0-beta.1 17 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.12 16 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.11 16 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.10 16 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.9 16 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.8 14 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.7 14 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.6 09 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.5 06 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.4 01 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.3 01 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.2 01 Jun 2022 M1 MIT Yes Details →
2.7.0-alpha.1 31 May 2022 M1 MIT Yes Details →
2.6.14 07 Jun 2021 M1 MIT Yes Details →
2.6.13 01 Jun 2021 M1 MIT Yes Details →
2.6.12 20 Aug 2020 M1 MIT Yes Details →
2.6.11 13 Dec 2019 M1 MIT Yes Details →
2.6.10 20 Mar 2019 M1 MIT Yes Details →
2.6.9 14 Mar 2019 M1 MIT Yes Details →
2.6.8 01 Mar 2019 M1 MIT Yes Details →
2.6.7 21 Feb 2019 M1 MIT Yes Details →
2.6.6 12 Feb 2019 M1 MIT Yes Details →
2.6.5 11 Feb 2019 M1 MIT Yes Details →
2.6.4 08 Feb 2019 M1 MIT Yes Details →
2.6.3 06 Feb 2019 M1 MIT Yes Details →
2.6.2 05 Feb 2019 M1 MIT Yes Details →
2.6.1 04 Feb 2019 M1 MIT Yes Details →
2.6.0 04 Feb 2019 M1 MIT Yes Details →
2.6.0-beta.3 30 Jan 2019 M1 MIT Yes Details →
2.6.0-beta.2 26 Jan 2019 M1 MIT Yes Details →
2.6.0-beta.1 16 Jan 2019 M1 MIT Yes Details →
2.5.22 11 Jan 2019 M1 MIT Yes Details →
2.5.21 11 Dec 2018 M1 MIT Yes Details →
2.5.20 10 Dec 2018 M1 MIT Yes Details →
2.5.19 09 Dec 2018 M1 MIT Yes Details →
2.5.18 07 Dec 2018 M1 MIT Yes Details →
2.5.18-beta.0 02 Dec 2018 M1 MIT Yes Details →
2.5.17 01 Aug 2018 M1 MIT Yes Details →
2.5.17-beta.0 23 Mar 2018 M1 MIT Yes Details →
2.5.16 13 Mar 2018 M1 MIT Yes Details →
2.5.15 10 Mar 2018 M1 MIT Yes Details →
2.5.14 09 Mar 2018 M1 MIT Yes Details →
2.5.13 19 Dec 2017 M1 MIT Yes Details →
2.5.12 19 Dec 2017 M1 MIT Yes Details →
2.5.11 14 Dec 2017 M1 MIT Yes Details →
2.5.10 12 Dec 2017 M1 MIT Yes Details →
2.5.9 27 Nov 2017 M1 MIT Yes Details →
2.5.8 21 Nov 2017 M1 MIT Yes Details →
2.5.7 20 Nov 2017 M1 MIT Yes Details →
2.5.6 18 Nov 2017 M1 MIT Yes Details →
2.5.5 17 Nov 2017 M1 MIT Yes Details →
2.5.4 16 Nov 2017 M1 MIT Yes Details →
2.5.3 03 Nov 2017 M1 MIT Yes Details →
2.5.2 13 Oct 2017 M1 MIT Yes Details →
2.5.1 13 Oct 2017 M1 MIT Yes Details →
2.5.0 13 Oct 2017 M1 MIT Yes Details →
2.4.4 14 Sep 2017 M1 MIT Yes Details →
2.4.3 13 Sep 2017 M1 MIT Yes Details →
2.4.2 21 Jul 2017 M1 MIT Yes Details →
2.4.1 13 Jul 2017 M1 MIT Yes Details →
2.4.0 13 Jul 2017 M1 MIT Yes Details →
2.3.4 08 Jun 2017 M1 MIT Yes Details →
2.3.3 09 May 2017 M1 MIT Yes Details →
2.3.2 02 May 2017 M1 MIT Yes Details →
2.3.1 02 May 2017 M1 MIT Yes Details →
2.3.0 27 Apr 2017 M1 MIT Yes Details →
2.3.0-beta.1 26 Apr 2017 M1 MIT Yes Details →
2.2.6 27 Mar 2017 M1 MIT Yes Details →
2.2.5 24 Mar 2017 M1 MIT Yes Details →
2.2.4 13 Mar 2017 M1 MIT Yes Details →
2.2.3 13 Mar 2017 M1 MIT Yes Details →
2.2.2 09 Mar 2017 M1 MIT Yes Details →
2.2.1 26 Feb 2017 M1 MIT Yes Details →
2.2.0 26 Feb 2017 M1 MIT Yes Details →
2.2.0-beta.2 25 Feb 2017 M1 — Yes Details →
2.2.0-beta.1 24 Feb 2017 M1 — Yes Details →
2.1.10 17 Jan 2017 M1 — Yes Details →
2.1.9 16 Jan 2017 M1 — Yes Details →
2.1.8 28 Dec 2016 M1 — Yes Details →
2.1.7 24 Dec 2016 M1 — Yes Details →
2.1.6 13 Dec 2016 M1 — Yes Details →
2.1.5 13 Dec 2016 M1 — Yes Details →
2.1.4 02 Dec 2016 M1 — Yes Details →
2.1.3 24 Nov 2016 M1 — Yes Details →
2.1.2 23 Nov 2016 M1 — Yes Details →
2.1.1 23 Nov 2016 M1 — Yes Details →
2.1.0 22 Nov 2016 M1 — Yes Details →
2.0.8 20 Nov 2016 M1 — Yes Details →
2.0.7 16 Nov 2016 M1 — Yes Details →
2.0.6 15 Nov 2016 M1 — Yes Details →
2.0.5 05 Nov 2016 M1 — Yes Details →
2.0.4 04 Nov 2016 M1 — Yes Details →
2.0.3 13 Oct 2016 M1 — Yes Details →
2.0.2 12 Oct 2016 M1 — Yes Details →

The newest 120 of 147 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for vue-template-compiler

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About vue-template-compiler

Is vue-template-compiler safe to use?

Vulert records 1 vulnerabilities for vue-template-compiler in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is vue-template-compiler's Vulert package health score?

Vulert scores vue-template-compiler 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of vue-template-compiler affected?

Yes. 2.7.16, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of vue-template-compiler should I use?

2.7.16 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does vue-template-compiler have?

1 vulnerability is recorded for vue-template-compiler in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new vue-template-compiler vulnerabilities disclosed?

0 vulnerabilities were recorded for vue-template-compiler in the last 12 months, and the oldest entry in this database dates to 23 Jul 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of vue-template-compiler are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor vue-template-compiler for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the vue-template-compiler version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.