Vulnerability Database · npm · Package report

nuxt: vulnerability history, versions and safety

nuxt is a package in the npm ecosystem. Vulert records 28 vulnerabilities for it across 120 releases, from Jun 2023 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded C2 H7 M13 L6
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
23 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on nuxt 4.6.2 i

Updated on 23 Oct 2026

Careful: 4.6.2 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.6.2 — affected i
  • Vulnerabilities on record 28 over 3 years · 23 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 126 packages i
  • Stars 60,963 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i
  • Similar names next 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 nuxt, 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.6.2 16 Oct 2026 M1 MIT No Details →
4.6.1 09 Oct 2026 M3 MIT No Details →
4.6.0 05 Oct 2026 M3 MIT No Details →
3.21.11 05 Aug 2026 M1 L1 MIT Yes Details →
4.5.2 05 Aug 2026 M3 L1 MIT No Details →
3.21.10 27 Jul 2026 M1 L1 MIT Yes Details →
4.5.1 27 Jul 2026 M3 L1 MIT No Details →
4.5.0 18 Jul 2026 H5 M5 L1 MIT No Details →
3.21.9 18 Jul 2026 M1 L1 MIT Yes Details →
3.21.8 08 Jun 2026 M1 L1 MIT Yes Details →
4.4.8 08 Jun 2026 H5 M5 L1 MIT No Details →
4.4.7 02 Jun 2026 H5 M5 L1 MIT No Details →
3.21.7 02 Jun 2026 M1 L1 MIT Yes Details →
4.4.6 18 May 2026 H5 M7 L4 MIT Yes Details →
3.21.6 18 May 2026 M1 L1 MIT Yes Details →
4.4.5 10 May 2026 H5 M7 L4 MIT Yes Details →
3.21.5 10 May 2026 M3 L2 MIT Yes Details →
3.21.4 29 Apr 2026 M3 L2 MIT Yes Details →
4.4.4 29 Apr 2026 H5 M7 L4 MIT Yes Details →
4.4.2 12 Mar 2026 H5 M8 L4 MIT Yes Details →
3.21.2 12 Mar 2026 M3 L2 MIT Yes Details →
4.3.1 07 Feb 2026 H4 M8 L4 MIT Yes Details →
3.21.1 07 Feb 2026 M3 L2 MIT Yes Details →
3.21.0 22 Jan 2026 M3 L2 MIT Yes Details →
4.3.0 22 Jan 2026 H4 M8 L4 MIT Yes Details →
4.2.2 09 Dec 2025 H4 M8 L4 MIT Yes Details →
3.20.2 09 Dec 2025 M3 L2 MIT Yes Details →
4.2.1 06 Nov 2025 H4 M8 L4 MIT Yes Details →
3.20.1 06 Nov 2025 M3 L2 MIT Yes Details →
3.20.0 28 Oct 2025 M3 L2 MIT Yes Details →
4.2.0 25 Oct 2025 H4 M8 L4 MIT Yes Details →
4.1.3 06 Oct 2025 H4 M8 L4 MIT Yes Details →
3.19.3 06 Oct 2025 M3 L2 MIT Yes Details →
4.1.2 12 Sep 2025 H4 M8 L4 MIT Yes Details →
3.19.2 12 Sep 2025 M3 L2 MIT Yes Details →
4.1.1 05 Sep 2025 H4 M8 L4 MIT Yes Details →
3.19.1 05 Sep 2025 M3 L2 MIT Yes Details →
4.1.0 02 Sep 2025 H4 M8 L4 MIT Yes Details →
3.19.0 02 Sep 2025 M3 L2 MIT Yes Details →
4.0.3 05 Aug 2025 H4 M8 L4 MIT Yes Details →
3.18.1 05 Aug 2025 M3 L3 MIT Yes Details →
4.0.2 29 Jul 2025 H4 M8 L4 MIT Yes Details →
3.18.0 29 Jul 2025 M3 L3 MIT Yes Details →
4.0.1 21 Jul 2025 H4 M8 L4 MIT Yes Details →
4.0.0 15 Jul 2025 H4 M8 L4 MIT Yes Details →
3.17.7 13 Jul 2025 M3 L3 MIT Yes Details →
4.0.0-rc.0 07 Jul 2025 M1 L2 MIT Yes Details →
3.17.6 01 Jul 2025 M3 L3 MIT Yes Details →
4.0.0-alpha.4 27 Jun 2025 M1 L2 MIT Yes Details →
4.0.0-alpha.3 26 Jun 2025 M1 L2 MIT Yes Details →
4.0.0-alpha.2 12 Jun 2025 M1 L2 MIT Yes Details →
3.17.5 03 Jun 2025 M3 L3 MIT Yes Details →
4.0.0-alpha.1 02 Jun 2025 M1 L2 MIT Yes Details →
3.17.4 20 May 2025 M3 L3 MIT Yes Details →
4.0.0-0 15 May 2025 H4 M8 L4 MIT Yes Details →
3.17.3 12 May 2025 M3 L3 MIT Yes Details →
3.17.2 05 May 2025 M3 L3 MIT Yes Details →
3.17.1 29 Apr 2025 M3 L3 MIT Yes Details →
3.17.0 27 Apr 2025 M3 L3 MIT Yes Details →
3.16.2 01 Apr 2025 M3 L3 MIT Yes Details →
3.16.1 19 Mar 2025 M3 L3 MIT Yes Details →
3.16.0 07 Mar 2025 M3 L3 MIT Yes Details →
3.15.4 29 Jan 2025 H1 M3 L3 MIT Yes Details →
3.15.3 24 Jan 2025 H1 M3 L3 MIT Yes Details →
3.15.2 15 Jan 2025 H1 M3 L3 MIT Yes Details →
3.15.1 05 Jan 2025 H1 M3 L3 MIT Yes Details →
3.15.0 24 Dec 2024 H1 M3 L3 MIT Yes Details →
3.14.1592 19 Nov 2024 H1 M3 L3 MIT Yes Details →
3.14.159 06 Nov 2024 H1 M3 L3 MIT Yes Details →
3.14.0 04 Nov 2024 H1 M3 L3 MIT Yes Details →
3.13.2 15 Sep 2024 H1 M3 L3 MIT Yes Details →
3.13.1 04 Sep 2024 H1 M3 L3 MIT Yes Details →
3.13.0 22 Aug 2024 H1 M3 L3 MIT Yes Details →
3.12.4 18 Jul 2024 H1 M2 L3 MIT Yes Details →
3.12.3 02 Jul 2024 C1 H1 M3 L3 MIT Yes Details →
2.18.1 28 Jun 2024 M1 L1 MIT Yes Details →
2.18.0 27 Jun 2024 M1 L1 MIT Yes Details →
3.12.2 16 Jun 2024 C1 H1 M3 L3 MIT Yes Details →
2.17.4 14 Jun 2024 M1 L1 MIT Yes Details →
3.12.1 11 Jun 2024 C1 H1 M3 L3 MIT Yes Details →
3.12.0 11 Jun 2024 C1 H1 M3 L3 MIT Yes Details →
3.11.2 04 Apr 2024 C1 H1 M3 L3 MIT Yes Details →
3.11.1 18 Mar 2024 C1 H1 M3 L3 MIT Yes Details →
3.11.0 17 Mar 2024 C1 H1 M3 L3 MIT Yes Details →
3.10.3 22 Feb 2024 C1 H1 M2 L3 MIT Yes Details →
3.10.2 14 Feb 2024 C1 H1 M2 L3 MIT Yes Details →
3.10.1 05 Feb 2024 C1 H1 M2 L3 MIT Yes Details →
3.10.0 30 Jan 2024 C1 H1 M2 L3 MIT Yes Details →
3.9.3 17 Jan 2024 C1 H1 M2 L3 MIT Yes Details →
3.9.2 16 Jan 2024 C1 H1 M2 L3 MIT Yes Details →
2.17.3 12 Jan 2024 M1 L1 MIT Yes Details →
3.9.1 05 Jan 2024 C1 H1 M2 L3 MIT Yes Details →
3.9.0 25 Dec 2023 C1 H1 M2 L3 MIT Yes Details →
3.8.2 20 Nov 2023 C1 H1 M2 L3 MIT Yes Details →
3.8.1 06 Nov 2023 C1 H1 M2 L3 MIT Yes Details →
2.17.2 24 Oct 2023 M1 L1 MIT Yes Details →
3.8.0 19 Oct 2023 C1 H1 M2 L3 MIT Yes Details →
3.7.4 26 Sep 2023 C1 H1 M2 L3 MIT Yes Details →
3.7.3 13 Sep 2023 C1 H1 M2 L3 MIT Yes Details →
3.7.2 12 Sep 2023 C1 H1 M2 L3 MIT Yes Details →
3.7.1 05 Sep 2023 C1 H1 M2 L3 — Yes Details →
3.7.0 25 Aug 2023 C1 H1 M2 L3 — Yes Details →
3.6.5 19 Jul 2023 C1 H1 M2 L3 — Yes Details →
3.6.4 19 Jul 2023 C1 H1 M2 L3 — Yes Details →
3.6.3 14 Jul 2023 C1 H1 M2 L3 — Yes Details →
2.17.1 14 Jul 2023 M1 L1 — Yes Details →
3.6.2 05 Jul 2023 C1 H1 M2 L3 — Yes Details →
3.6.1 26 Jun 2023 C1 H1 M2 L3 — Yes Details →
3.6.0 23 Jun 2023 C1 H1 M2 L3 — Yes Details →
2.17.0 09 Jun 2023 M1 L1 — Yes Details →
3.5.3 06 Jun 2023 C1 H1 M2 L2 — Yes Details →
3.5.2 29 May 2023 C1 H1 M2 L2 — Yes Details →
3.5.1 21 May 2023 C1 H1 M2 L2 — Yes Details →
3.5.0 16 May 2023 C1 H1 M2 L2 — Yes Details →
3.4.3 28 Apr 2023 C1 H1 M2 L2 — Yes Details →
3.4.2 20 Apr 2023 C2 H1 M1 L2 — Yes Details →
3.4.1 13 Apr 2023 C2 H1 M1 L2 — Yes Details →
3.4.0 11 Apr 2023 C2 H1 M1 L2 — Yes Details →
3.3.3 02 Apr 2023 H1 M1 L2 — Yes Details →
3.3.2 24 Mar 2023 H1 M1 L2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 2
  • 2025 2
  • 2026 23

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

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 nuxt

Is nuxt safe to use?

Vulert records 28 vulnerabilities for nuxt in npm: 2 critical, 7 high, 13 medium and 6 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is nuxt's Vulert package health score?

Vulert scores nuxt 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of nuxt affected?

Yes. 4.6.2, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of nuxt should I use?

4.6.2 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 nuxt have?

28 vulnerabilities are recorded for nuxt in the npm ecosystem: 2 critical, 7 high, 13 medium and 6 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nuxt vulnerabilities disclosed?

23 vulnerabilities were recorded for nuxt in the last 12 months, and the oldest entry in this database dates to 13 Jun 2023. 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 nuxt 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 nuxt for upcoming vulnerabilities?

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