{"answers":{"affected":"6 open source packages ship an affected version, including vite and vite-plus.","exploited":"There is no known exploitation of CVE-2026-112947 in the wild and no public exploit code.","fix":"Upgrade vite to a fixed version for your release line: 8.2.4 or 8.3.3.","what":"CVE-2026-112947 is a medium-severity vulnerability in vitejs vite, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-112947 and fix it if it is affected.\n\nWhat it is: CVE-2026-112947 is a medium-severity vulnerability in vitejs vite, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-112947 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vite (npm): affected from 8.2.0; fixed in 8.2.4\n- vite (npm): affected from 8.2.0; fixed in 8.2.4\n- vite (npm): affected from 8.3.0; fixed in 8.3.3\n- vite (npm): affected from 8.3.0; fixed in 8.3.3\n- vite-plus (npm): affected from 0.2.8; fixed in 1.1.0\n- vite-plus (npm): affected from 0.2.8; fixed in 1.1.0\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-112947/ (Markdown: https://insights.sbomify.com/CVE-2026-112947/index.md)","id":"CVE-2026-112947","markdown":"https://insights.sbomify.com/CVE-2026-112947/index.md","name":"CVE-2026-112947","record":{"aliases":["ECHO-4beb-4040-cfe3","GHSA-vfpm-58rq-9qcg","UBUNTU-CVE-2026-112947"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Vite is a frontend tooling framework for JavaScript. From 8.2.0 until 8.2.4 and 8.3.3, the first 4 bytes of files outside of server.fs setting can be returned to the browser by a request containing ?vite-wasm-instance. Requests containing the ?vite-wasm-instance query are handled by the internal Wasm plugin's load hook. The hook removes the query and reads the resulting path directly from disk, but the server.fs checks were not applied. After reading the file, Vite attempts to parse it as WebAssembly. When that parse fails, Node and deno throws an error that contains the first 4 bytes of the file. This vulnerability is fixed in 8.2.4 and 8.3.3.","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":"Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`","id":"CVE-2026-112947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":6,"n_references":4,"next":{"headline":"Vitest: Servers misapply `server.fs.deny`, serving `.env`, private keys, `.git`, and the API token file","id":"CVE-2026-112948"},"packages":[{"ecosystem":"npm","fixed":["8.2.4"],"introduced":["8.2.0"],"last_affected":[],"package":"vite","purl":null,"source":"GHSA-vfpm-58rq-9qcg"},{"ecosystem":"npm","fixed":["8.2.4"],"introduced":["8.2.0"],"last_affected":[],"package":"vite","purl":"pkg:npm/vite","source":"GHSA-vfpm-58rq-9qcg"},{"ecosystem":"npm","fixed":["8.3.3"],"introduced":["8.3.0"],"last_affected":[],"package":"vite","purl":null,"source":"GHSA-vfpm-58rq-9qcg"},{"ecosystem":"npm","fixed":["8.3.3"],"introduced":["8.3.0"],"last_affected":[],"package":"vite","purl":"pkg:npm/vite","source":"GHSA-vfpm-58rq-9qcg"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.2.8"],"last_affected":[],"package":"vite-plus","purl":null,"source":"GHSA-vfpm-58rq-9qcg"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.2.8"],"last_affected":[],"package":"vite-plus","purl":"pkg:npm/vite-plus","source":"GHSA-vfpm-58rq-9qcg"}],"prev":{"headline":"Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine","id":"CVE-2026-112946"},"products":["vite","vite-plus"],"published":"2026-10-20","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-10-21","vendors":["vitejs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-112947/"}