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 unaffected, as the IPC server runs only in development.
CVE-2026-56301
MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence
Score 5.5 from GitHub Security Advisory published 2026-06-23. a secondary CVSS source baseline 5.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EPSS
- 1.2%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
June 25, 2026
Advisory Details (4)
Auto-updated Jun 23, 2026Patch available. Sources: github_commit, github.
generic
Nuxt - Arbitrary File Read via World-Connectable vite-node IPC Socket on Linux | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nuxt-arbitrary-file-read-via-world-connectable-vite-node-ipc-socket-on-linuxgithub Patch Available
Nuxt dev server vite-node IPC socket is world-connectable on Linux · Advisory · nuxt/nuxt · GitHub
https://github.com/nuxt/nuxt/security/advisories/GHSA-534h-c3cw-v3h9github_commit
commit c293bf9503cc (nuxt/nuxt)
Fix landed in nuxt/nuxt commit c293bf9503cc — awaiting tagged release
https://github.com/nuxt/nuxt/commit/c293bf9503ccb3bc9559bff4a1f592f99063c9eagithub_commit
commit 1f9f4767a872 (nuxt/nuxt)
Fix landed in nuxt/nuxt commit 1f9f4767a872 — awaiting tagged release
https://github.com/nuxt/nuxt/commit/1f9f4767a8725104da9bee872bb8d35246f25ae5Vendor Advisories for CVE-2026-56301(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(5)
What is CVE-2026-56301?
CVE-2026-56301 is a medium vulnerability published on June 23, 2026. 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…
When was CVE-2026-56301 disclosed?
CVE-2026-56301 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56301 actively exploited?
CVE-2026-56301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56301?
CVE-2026-56301 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-56301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56301, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56301
Is Your Infrastructure Affected by CVE-2026-56301?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.