CISA list

Nuxt versions

Nuxt: update to 4.6.4. 3 and older have reached end of life in the lifecycle data, which lists commercial support for 2.

Data: .

Which Nuxt branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.

Which Nuxt branch to run
BranchStatusNewest safe releaseUpgrade to
429 CVE records that this page readsBug and security fixes, no end date announced4.6.44.6.4 (this branch)
320 CVE records that this page readsEnded on 31 July 2026None, the branch has ended4.6.4 (move to 4)
2Ended on 30 June 2024, commercial support listedNone, the branch has ended4.6.4 (move to 4)
1Ended on 21 September 2019None, the branch has ended4.6.4 (move to 4)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 44 CVE records that the CVE Numbering Authorities GitHub_M and VulnCheck (as the CVE List names them) published and that name Nuxt. The fixes are from the 34 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended.

The product lifecycle data lists commercial support for 2. This page lists only what the CVE records name.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.

10 records are not placed on a branch, so no branch or release row counts them: CVE-2023-54418, CVE-2024-23657, CVE-2024-34343, CVE-2026-53722, CVE-2026-56317, CVE-2026-56326, CVE-2026-56697, CVE-2026-56698, CVE-2026-114130 and CVE-2026-114132.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)