{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119198 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-119198 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119198 is a medium-severity vulnerability in nuxt, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119198 and fix it if it is affected.\n\nWhat it is: CVE-2026-119198 is a medium-severity vulnerability in nuxt, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119198 in the wild and no public exploit code.\n\nAffected product: nuxt. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-119198/ (Markdown: https://insights.sbomify.com/CVE-2026-119198/index.md)","id":"CVE-2026-119198","markdown":"https://insights.sbomify.com/CVE-2026-119198/index.md","name":"CVE-2026-119198","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, a client with TCP access to an exposed Nuxt development server can send a nuxt:dev:client-error event over the HMR socket with an absolute file path at the end of its message. The development server reads that file while building the client error report and returns its contents through the error overlay, development error channel, and terminal report, bypassing Vite's server.fs allow list. The default localhost binding limits remote exposure, cross-origin browser requests are rejected, production builds and Nuxt 3 are not affected, and no browser interaction is required. This issue is fixed in version 4.6.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Nuxt dev server arbitrary file read through client error reports","id":"CVE-2026-119198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Nuxt dev server exposes private runtime config through the Nitro dev bundle","id":"CVE-2026-119199"},"packages":[],"prev":{"headline":"pyasn1: Quadratic-complexity denial of service in binary REAL decoding","id":"CVE-2026-119197"},"products":["nuxt"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["nuxt"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119198/"}