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.

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.

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, 2026
Patch 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-linux
github 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-v3h9
github_commit

commit c293bf9503cc (nuxt/nuxt)

Fix landed in nuxt/nuxt commit c293bf9503cc — awaiting tagged release

https://github.com/nuxt/nuxt/commit/c293bf9503ccb3bc9559bff4a1f592f99063c9ea
github_commit

commit 1f9f4767a872 (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 1f9f4767a872 — awaiting tagged release

https://github.com/nuxt/nuxt/commit/1f9f4767a8725104da9bee872bb8d35246f25ae5

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
nuxt—4.4.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 14:19 UTCGHSA enrichment
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 14:53 UTCGHSA enrichment
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 15:56 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 16:55 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 17:54 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 18:56 UTCGHSA enrichment
  22. 2026-07-10 19:58 UTCGHSA enrichment
  23. 2026-07-09 21:00 UTCGHSA enrichment
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 36 more
  1. 2026-07-08 22:02 UTCGHSA enrichment
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 23:03 UTCGHSA enrichment
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 00:04 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 01:06 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 01:58 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 03:00 UTCGHSA enrichment
  17. 2026-07-03 03:55 UTCGHSA enrichment
  18. 2026-07-02 04:54 UTCGHSA enrichment
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 05:56 UTCGHSA enrichment
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 06:58 UTCGHSA enrichment
  23. 2026-06-29 08:00 UTCGHSA enrichment
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 09:01 UTCGHSA enrichment
  26. 2026-06-28 04:56 UTCEPSS rescore
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-27 10:04 UTCGHSA enrichment
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-26 11:06 UTCGHSA enrichment
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 10:37 UTCGHSA enrichment
  33. 2026-06-24 14:05 UTCEPSS rescore
  34. 2026-06-24 11:39 UTCGHSA enrichment
  35. 2026-06-23 12:42 UTCEG score recompute
  36. 2026-06-23 12:40 UTCMITRE cvelistV5first tracked

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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56301

Explore →

Is Your Infrastructure Affected by CVE-2026-56301?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs