{"answers":{"affected":"4 open source packages ship an affected version, including nuxt.","exploited":"There is no known exploitation of CVE-2026-71318 in the wild and no public exploit code.","fix":"Upgrade nuxt to a fixed version for your release line: 3.21.10 or 4.5.1.","what":"CVE-2026-71318 is a medium-severity code injection vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71318 and fix it if it is affected.\n\nWhat it is: CVE-2026-71318 is a medium-severity code injection vulnerability in nuxt, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71318 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nuxt (npm): affected from 3.1.0; fixed in 3.21.10\n- nuxt (npm): affected from 3.1.0; fixed in 3.21.10\n- nuxt (npm): affected from 4.0.0; fixed in 4.5.1\n- nuxt (npm): affected from 4.0.0; fixed in 4.5.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-71318/ (Markdown: https://insights.sbomify.com/CVE-2026-71318/index.md)","id":"CVE-2026-71318","markdown":"https://insights.sbomify.com/CVE-2026-71318/index.md","name":"CVE-2026-71318","record":{"aliases":["GHSA-48hr-524c-v5w3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nuxt web framework","requires_auth":"none","summary":"Attackers can execute arbitrary code by injecting malicious props into Nuxt server island endpoints, requiring an upgrade to patched versions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Nuxt is an open-source web development framework for Vue.js. From 3.1.0 until 3.21.10 and 4.5.1, an attacker can supply a top-level `as` prop to the /__nuxt_island/ endpoint and drive dynamic component resolution through \u003ccomponent :is\u003e, resolveDynamicComponent, or h(). This issue is fixed in 3.21.10 and 4.5.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nuxt: Unauthorized Component Instantiation via Server Island Props","id":"CVE-2026-71318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution","id":"CVE-2026-71319"},"packages":[{"ecosystem":"npm","fixed":["3.21.10"],"introduced":["3.1.0"],"last_affected":[],"package":"nuxt","purl":null,"source":"GHSA-48hr-524c-v5w3"},{"ecosystem":"npm","fixed":["3.21.10"],"introduced":["3.1.0"],"last_affected":[],"package":"nuxt","purl":"pkg:npm/nuxt","source":"GHSA-48hr-524c-v5w3"},{"ecosystem":"npm","fixed":["4.5.1"],"introduced":["4.0.0"],"last_affected":[],"package":"nuxt","purl":null,"source":"GHSA-48hr-524c-v5w3"},{"ecosystem":"npm","fixed":["4.5.1"],"introduced":["4.0.0"],"last_affected":[],"package":"nuxt","purl":"pkg:npm/nuxt","source":"GHSA-48hr-524c-v5w3"}],"prev":{"headline":"Lemur: Sub-CA creation never checks `AuthorityPermission` on the parent authority","id":"CVE-2026-71317"},"products":["nuxt"],"published":"2026-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-06","vendors":["nuxt"]},"summary":"Attackers can execute arbitrary code by injecting malicious props into Nuxt server island endpoints, requiring an upgrade to patched versions.","url":"https://insights.sbomify.com/CVE-2026-71318/"}