Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-56301: Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Linux, bin

25
Routine
MEDIUM 5.5WATCHLISTUPGRADE

CVE-2026-56301 is a medium-severity flaw (CVSS 5.5) affecting nuxt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Linux, binds the vite-node IPC server to an abstract-namespace Unix socket without permission restrictions, allowing local users to enumerate and connect. Unprivileged co-resident users can exploit the unprotected module request handler to read arbitrary files such as .env and SSH keys through the SSR plugin pipeline. Production builds are unaffect

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.5 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.1% (top 96%)
CISA exploited listNo
WeaknessCWE-276
Published2026-06-23
Last modified2026-06-25
Publisher (CNA): VulnCheck · Vendor: nuxt

Share: LinkedIn · X · Reddit

Last updated 2026-06-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nuxt nuxt UPGRADE
Affected: >= 3.18.0 and < 3.21.7 · >= 4.0.0 and < 4.4.7
Fixed in: 3.21.7, 4.4.7
Safe to downgrade to: a release before 3.18.0
1. Check installed version
apt-cache policy nuxt || rpm -q nuxt || nuxt --version
2. UPGRADE to 3.21.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade nuxt
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade nuxt
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.18.0 (Debian / Ubuntu)
apt-cache madison nuxt sudo apt install nuxt=<VERSION_BEFORE_3.18.0> sudo apt-mark hold nuxt
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list nuxt sudo dnf downgrade nuxt-<VERSION_BEFORE_3.18.0> sudo dnf versionlock add nuxt
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-56301?

nuxt: upgrade to 3.21.7, 4.4.7. Exact commands for each OS are on this page.

Is CVE-2026-56301 being exploited?

CVE-2026-56301 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-56301 affect?

CVE-2026-56301 affects nuxt. Severity is medium (CVSS 5.5). Nuxt 4.0.0 before 4.4.7 and 3.18.0 before 3.21.7, when running the development server (nuxt dev) on Linux, binds the vite-node IPC server to an abstract-namespace Unix socket without permission restrictions, allowing local users to enumerat

How urgent is CVE-2026-56301?

Priority 25/100. On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.