CVE-2026-71319

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Nuxt is an open-source web development framework for Vue.js. Prior to 3.3.1, Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the nuxt:devtools:rpc plugin. On affected versions the channel has no authentication: any client that can reach the Vite HMR endpoint (ws://:/, subprotocol vite-hmr) can call RPC methods, with no token, handshake, or origin check before the channel is established. The updateOptions(), clearOptions(), and openInEditor() methods do not enforce the ensureDevAuthToken check that the other mutating methods use. openInEditor() reads the persisted behavior.openInEditor value and passes it to the launch-editor package, which spawns it as a child process. That value is settable through the equally unauthenticated updateOptions(). An attacker who can reach the HMR port can therefore chain updateOptions('behavior', { openInEditor: '' }) then openInEditor('') to execute an arbitrary program on the developer's machine. This issue is fixed in 3.3.1.

CVSS v3
9.6
EG Score
9.6(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 7, 2026

Advisory Details (3)

Auto-updated Aug 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Unauthenticated Nuxt DevTools RPC allows arbitrary command execution on the developer's host · Advisory · nuxt/nuxt · GitHub

https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv
github_release Patch Available

v3.3.1

Patch available: nuxt/devtools v3.3.1

https://github.com/nuxt/devtools/releases/tag/v3.3.1
github_commit Patch Available

commit a7b2718b9307 (nuxt/devtools)

Patch available: nuxt/devtools v3.3.0 (contains commit a7b2718b9307)

https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4

Vendor Advisories for CVE-2026-71319(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/devtools—3.3.1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 36× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-19 18:51 UTCEG score recompute
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 18:13 UTCEG score recompute
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-17 16:32 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 16:25 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 04:29 UTCEG score recompute
  13. 2026-08-16 02:15 UTCEPSS rescore
  14. 2026-08-15 04:35 UTCEG score recompute
  15. 2026-08-15 01:31 UTCEPSS rescore
  16. 2026-08-14 00:41 UTCEG score recompute
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 16:49 UTCEG score recompute
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-11 16:55 UTCEG score recompute
  21. 2026-08-11 00:59 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 17:06 UTCEG score recompute
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 17:12 UTCEG score recompute
Show 11 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 17:17 UTCEG score recompute
  3. 2026-08-07 05:20 UTCEG score recompute
  4. 2026-08-07 04:19 UTCEG score recompute
  5. 2026-08-06 15:29 UTCEG score recompute
  6. 2026-08-06 14:46 UTCEG score recompute
  7. 2026-08-06 14:14 UTCEG score recompute
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-05 22:18 UTCEG score recompute
  10. 2026-08-05 21:40 UTCEG score recompute
  11. 2026-08-05 21:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71319?
CVE-2026-71319 is a critical vulnerability published on August 5, 2026. Nuxt is an open-source web development framework for Vue.js. Prior to 3.3.1, Nuxt DevTools (development mode only) exposes a bidirectional RPC channel over the Vite HMR WebSocket via the nuxt:devtools:rpc plugin. On affected versions the channel has no authentication: any client that can reach the…
When was CVE-2026-71319 disclosed?
CVE-2026-71319 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71319 actively exploited?
CVE-2026-71319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-71319?
CVE-2026-71319 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-71319?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71319, 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-71319

Explore →

Is Your Infrastructure Affected by CVE-2026-71319?

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

Start Free Scan →Browse All CVEs