CVE-2026-71319 (GCVE-0-2026-71319)
Vulnerability from cvelistv5 – Published: 2026-08-05 21:26 – Updated: 2026-08-07 03:55| URL | Tags |
|---|---|
| https://github.com/nuxt/nuxt/security/advisories/… | x_refsource_CONFIRM |
| https://github.com/nuxt/devtools/commit/a7b2718b9… | x_refsource_MISC |
| https://github.com/nuxt/devtools/releases/tag/v3.3.1 | x_refsource_MISC |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-71319",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-06T00:00:00+00:00",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-07T03:55:35.069Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "devtools",
"vendor": "nuxt",
"versions": [
{
"status": "affected",
"version": "\u003c 3.3.1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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://\u003chost\u003e:\u003cport\u003e/, 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(\u0027behavior\u0027, { openInEditor: \u0027\u003ccommand\u003e\u0027 }) then openInEditor(\u0027\u003cany-existing-file\u003e\u0027) to execute an arbitrary program on the developer\u0027s machine. This issue is fixed in 3.3.1."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.6,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-94",
"description": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306: Missing Authentication for Critical Function",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T21:26:59.028Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv"
},
{
"name": "https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4"
},
{
"name": "https://github.com/nuxt/devtools/releases/tag/v3.3.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/nuxt/devtools/releases/tag/v3.3.1"
}
],
"source": {
"advisory": "GHSA-279x-mwfv-vcqv",
"discovery": "UNKNOWN"
},
"title": "Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-71319",
"datePublished": "2026-08-05T21:26:59.028Z",
"dateReserved": "2026-08-05T18:14:42.065Z",
"dateUpdated": "2026-08-07T03:55:35.069Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-71319",
"date": "2026-11-13",
"epss": "0.00629",
"percentile": "0.50728"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "devtools",
"vendor": "nuxt",
"versions": [
{
"status": "affected",
"version": "\u003c 3.3.1"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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://\u003chost\u003e:\u003cport\u003e/, 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(\u0027behavior\u0027, { openInEditor: \u0027\u003ccommand\u003e\u0027 }) then openInEditor(\u0027\u003cany-existing-file\u003e\u0027) to execute an arbitrary program on the developer\u0027s machine. This issue is fixed in 3.3.1."
},
{
"lang": "es",
"value": "Nuxt es un framework de desarrollo web de c\u00f3digo abierto para Vue.js. Antes de la versi\u00f3n 3.3.1, Nuxt DevTools (solo en modo de desarrollo) expone un canal RPC bidireccional a trav\u00e9s del WebSocket HMR de Vite mediante el plugin nuxt:devtools:rpc. En las versiones afectadas, el canal no tiene autenticaci\u00f3n: cualquier cliente que pueda alcanzar el endpoint HMR de Vite (ws://[host]:[port]/, subprotocolo vite-hmr) puede llamar a m\u00e9todos RPC, sin token, handshake o verificaci\u00f3n de origen antes de que se establezca el canal. Los m\u00e9todos updateOptions(), clearOptions() y openInEditor() no aplican la verificaci\u00f3n ensureDevAuthToken que utilizan los otros m\u00e9todos mutadores. openInEditor() lee el valor persistido behavior.openInEditor y lo pasa al paquete launch-editor, que lo genera como un proceso hijo. Ese valor es configurable a trav\u00e9s del igualmente no autenticado updateOptions(). Un atacante que pueda alcanzar el puerto HMR puede, por lo tanto, encadenar updateOptions(\u2019behavior\u2019, { openInEditor: \u2019[command]\u2019 }) y luego openInEditor(\u2019[any-existing-file]\u2019) para ejecutar un programa arbitrario en la m\u00e1quina del desarrollador. Este problema est\u00e1 solucionado en la versi\u00f3n 3.3.1."
}
],
"id": "CVE-2026-71319",
"lastModified": "2026-10-24T15:10:00.190",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.6,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 6.0,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-71319",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-06T00:00:00+00:00",
"version": "2.0.3"
}
}
]
},
"published": "2026-08-05T22:17:08.227",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/nuxt/devtools/releases/tag/v3.3.1"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-94"
},
{
"lang": "en",
"value": "CWE-306"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-71319",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-06T14:38:40.363333Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-06T14:38:51.092Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "devtools",
"vendor": "nuxt",
"versions": [
{
"status": "affected",
"version": "\u003c 3.3.1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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://\u003chost\u003e:\u003cport\u003e/, 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(\u0027behavior\u0027, { openInEditor: \u0027\u003ccommand\u003e\u0027 }) then openInEditor(\u0027\u003cany-existing-file\u003e\u0027) to execute an arbitrary program on the developer\u0027s machine. This issue is fixed in 3.3.1."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.6,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-94",
"description": "CWE-94: Improper Control of Generation of Code (\u0027Code Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306: Missing Authentication for Critical Function",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T21:26:59.028Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv"
},
{
"name": "https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/nuxt/devtools/commit/a7b2718b930766e1ffb0640259d53f5b041a50b4"
},
{
"name": "https://github.com/nuxt/devtools/releases/tag/v3.3.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/nuxt/devtools/releases/tag/v3.3.1"
}
],
"source": {
"advisory": "GHSA-279x-mwfv-vcqv",
"discovery": "UNKNOWN"
},
"title": "Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-71319",
"datePublished": "2026-08-05T21:26:59.028Z",
"dateReserved": "2026-08-05T18:14:42.065Z",
"dateUpdated": "2026-08-07T03:55:35.069Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.