VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vuetify: vulnerability history, versions and safety

vuetify is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 0 release, from Sep 2022 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 12 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vuetify vulnerabilities

Vulert verdict on vuetify 4.3.0 i

Updated on 23 Oct 2026

Good news: 4.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 4.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.0 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 2 in the last year i
  • Latest disclosure 12 Dec 2025 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 83 packages i
  • Stars 41,031 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 vuetify, 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
4.3.0 19 Oct 2026 none MIT — Details →
4.2.6 14 Oct 2026 none MIT — Details →
3.13.7 14 Oct 2026 none MIT — Details →
4.3.0-beta.0 13 Oct 2026 none MIT — Details →
4.2.5 13 Oct 2026 none MIT — Details →
4.2.4 06 Oct 2026 none MIT — Details →
3.13.6 05 Oct 2026 none MIT — Details →
4.2.3 30 Sep 2026 none MIT — Details →
4.2.2 23 Sep 2026 none MIT — Details →
3.13.5 22 Sep 2026 none MIT — Details →
4.2.1 09 Sep 2026 none MIT — Details →
3.13.4 09 Sep 2026 none MIT — Details →
4.2.0 02 Sep 2026 none MIT — Details →
4.1.13 02 Sep 2026 none MIT — Details →
3.13.3 01 Sep 2026 none MIT — Details →
4.2.0-beta.0 27 Aug 2026 none MIT — Details →
4.1.12 26 Aug 2026 none MIT — Details →
4.1.11 19 Aug 2026 none MIT — Details →
4.1.10 18 Aug 2026 none MIT — Details →
3.13.2 18 Aug 2026 none MIT — Details →
4.1.9 13 Aug 2026 none MIT — Details →
4.1.8 07 Aug 2026 none MIT — Details →
3.13.1 07 Aug 2026 none MIT — Details →
4.1.7 30 Jul 2026 none MIT — Details →
3.13.0 27 Jul 2026 none MIT — Details →
4.1.6 23 Jul 2026 none MIT — Details →
3.12.11 22 Jul 2026 none MIT — Details →
4.1.5 13 Jul 2026 none MIT — Details →
3.12.10 13 Jul 2026 none MIT — Details →
4.1.4 07 Jul 2026 none MIT — Details →
4.1.3 02 Jul 2026 none MIT — Details →
3.12.9 02 Jul 2026 none MIT — Details →
4.1.2 16 Jun 2026 none MIT — Details →
4.1.1 08 Jun 2026 none MIT — Details →
4.1.0 02 Jun 2026 none MIT — Details →
4.0.9 02 Jun 2026 none MIT — Details →
3.12.8 02 Jun 2026 none MIT — Details →
4.0.8 28 May 2026 none MIT — Details →
3.12.7 28 May 2026 none MIT — Details →
4.1.0-beta.1 27 May 2026 none MIT — Details →
4.1.0-beta.0 21 May 2026 none MIT — Details →
4.0.7 08 May 2026 none MIT — Details →
3.12.6 08 May 2026 none MIT — Details →
4.0.6 22 Apr 2026 none MIT — Details →
4.0.5 02 Apr 2026 none MIT — Details →
3.12.5 02 Apr 2026 none MIT — Details →
4.0.4 25 Mar 2026 none MIT — Details →
3.12.4 25 Mar 2026 none MIT — Details →
4.0.3 19 Mar 2026 none MIT — Details →
4.0.2 12 Mar 2026 none MIT — Details →
3.12.3 12 Mar 2026 none MIT — Details →
3.12.2 04 Mar 2026 none MIT — Details →
4.0.1 04 Mar 2026 none MIT — Details →
4.0.0 23 Feb 2026 none MIT — Details →
4.0.0-beta.3 23 Feb 2026 none MIT — Details →
3.12.1 23 Feb 2026 none MIT — Details →
3.12.0 20 Feb 2026 none MIT — Details →
3.11.9 20 Feb 2026 none MIT — Details →
4.0.0-beta.2 10 Feb 2026 none MIT — Details →
4.0.0-beta.1 04 Feb 2026 none MIT — Details →
4.0.0-beta.0 30 Jan 2026 none MIT — Details →
3.11.8 27 Jan 2026 none MIT — Details →
3.11.7 20 Jan 2026 none MIT — Details →
4.0.0-alpha.0 30 Dec 2025 none MIT — Details →
3.11.6 30 Dec 2025 none MIT — Details →
3.11.5 24 Dec 2025 none MIT — Details →
3.11.4 16 Dec 2025 none MIT — Details →
3.11.3 09 Dec 2025 none MIT — Details →
3.11.2 03 Dec 2025 none MIT — Details →
3.11.1 24 Nov 2025 none MIT — Details →
3.11.0 24 Nov 2025 none MIT — Details →
3.10.12 24 Nov 2025 none MIT — Details →
3.11.0-beta.1 20 Nov 2025 none MIT — Details →
3.11.0-beta.0 14 Nov 2025 none MIT — Details →
3.10.11 14 Nov 2025 none MIT — Details →
3.10.10 11 Nov 2025 none MIT — Details →
3.10.9 05 Nov 2025 none MIT — Details →
3.10.8 29 Oct 2025 none MIT — Details →
3.10.7 22 Oct 2025 none MIT — Details →
3.10.6 21 Oct 2025 none MIT — Details →
3.10.5 07 Oct 2025 none MIT — Details →
3.10.4 01 Oct 2025 none MIT — Details →
3.10.3 24 Sep 2025 none MIT — Details →
3.10.2 17 Sep 2025 none MIT — Details →
3.10.1 16 Sep 2025 none MIT — Details →
3.10.0 10 Sep 2025 none MIT — Details →
3.9.7 03 Sep 2025 none MIT — Details →
3.9.6 26 Aug 2025 none MIT — Details →
3.9.5 12 Aug 2025 none MIT — Details →
3.9.4 05 Aug 2025 none MIT — Details →
3.9.3 29 Jul 2025 none MIT — Details →
3.9.2 18 Jul 2025 none MIT — Details →
3.9.1 17 Jul 2025 none MIT — Details →
3.9.0 08 Jul 2025 none MIT — Details →
3.8.12 02 Jul 2025 none MIT — Details →
3.9.0-beta.1 26 Jun 2025 none MIT — Details →
3.8.11 24 Jun 2025 none MIT — Details →
3.9.0-beta.0 20 Jun 2025 none MIT — Details →
3.8.10 18 Jun 2025 none MIT — Details →
3.8.9 11 Jun 2025 none MIT — Details →
3.8.8 04 Jun 2025 none — — Details →
3.8.7 27 May 2025 none — — Details →
3.8.6 21 May 2025 none — — Details →
3.8.5 14 May 2025 none — — Details →
3.8.4 07 May 2025 none — — Details →
3.8.3 29 Apr 2025 none — — Details →
3.8.2 16 Apr 2025 none — — Details →
3.8.1 07 Apr 2025 none — — Details →
3.8.0 01 Apr 2025 none — — Details →
3.7.19 26 Mar 2025 none — — Details →
3.8.0-beta.0 21 Mar 2025 none — — Details →
3.7.18 18 Mar 2025 none — — Details →
3.7.17 18 Mar 2025 none — — Details →
3.7.16 11 Mar 2025 none — — Details →
3.7.15 04 Mar 2025 none — — Details →
3.7.14 25 Feb 2025 none — — Details →
3.7.13 20 Feb 2025 none — — Details →
3.7.12 11 Feb 2025 none — — Details →
3.7.11 04 Feb 2025 none — — Details →
3.7.10 04 Feb 2025 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for vuetify

The 3 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2025-8083: Vuetify Prototype Pollution Vulnerability 8.6 high 3.0.0-alpha.10 12 Dec 2025
CVE-2025-8082: Vuetify VDatePicker Component XSS Vulnerability 6.3 medium 3.0.0 12 Dec 2025
CVE-2022-25873: Vuetify Cross-site Scripting Vulnerability 5.4 medium 2.6.10 19 Sep 2022

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 vuetify

Is vuetify safe to use?

Vulert records 4 vulnerabilities for vuetify in npm: 0 critical, 1 high, 3 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 vuetify's Vulert package health score?

Vulert scores vuetify 78/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 vuetify affected?

No. 4.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does vuetify have?

4 vulnerabilities are recorded for vuetify in the npm ecosystem: 0 critical, 1 high, 3 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 vuetify vulnerabilities disclosed?

2 vulnerabilities were recorded for vuetify in the last 12 months, and the oldest entry in this database dates to 19 Sep 2022. 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 vuetify 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 vuetify for upcoming vulnerabilities?

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