{"answers":{"affected":"4 open source packages ship an affected version, including @vitest/mocker.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112950 exists.","fix":"Upgrade @vitest/mocker to a fixed version for your release line: 4.1.12 or 5.0.3.","what":"CVE-2026-112950 is a medium-severity vulnerability in @vitest mocker, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-112950 and fix it if it is affected.\n\nWhat it is: CVE-2026-112950 is a medium-severity vulnerability in @vitest mocker, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112950 exists.\n\nAffected packages and fixed versions:\n- @vitest/mocker (npm): affected from 4.1.11; fixed in 4.1.12\n- @vitest/mocker (npm): affected from 4.1.11; fixed in 4.1.12\n- @vitest/mocker (npm): affected from 5.0.0-rc.2; fixed in 5.0.3\n- @vitest/mocker (npm): affected from 5.0.0-rc.2; fixed in 5.0.3\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-112950/ (Markdown: https://insights.sbomify.com/CVE-2026-112950/index.md)","id":"CVE-2026-112950","markdown":"https://insights.sbomify.com/CVE-2026-112950/index.md","name":"CVE-2026-112950","record":{"aliases":["CLSA-2026-1792617972","GHSA-xp26-3454-mjgp"],"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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Vitest is a Vite-native testing framework for JavaScript and TypeScript projects. From 4.1.11 until 4.1.12 and 5.0.3, isFileLoadingAllowed and the filesystem read interpret backslashes differently on Windows in packages/mocker/src/node/interceptorPlugin.ts. When a client can reach the Vite dev server on Windows and register a redirect mock containing backslash traversal, POSIX joining preserves a Windows backslash traversal that the later filesystem read interprets as a path separator, so the client can read a file outside server.fs.allow that the Vitest process can access. This issue is fixed in versions 4.1.12 and 5.0.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Vitest: Windows backslash traversal bypasses the @vitest/mocker redirect allowlist fix","id":"CVE-2026-112950","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"ApostropheCMS: Color field validation bypass allows stored XSS via HTML appended after rgb()/hsl() prefix","id":"CVE-2026-112951"},"packages":[{"ecosystem":"npm","fixed":["4.1.12"],"introduced":["4.1.11"],"last_affected":[],"package":"@vitest/mocker","purl":null,"source":"GHSA-xp26-3454-mjgp"},{"ecosystem":"npm","fixed":["4.1.12"],"introduced":["4.1.11"],"last_affected":[],"package":"@vitest/mocker","purl":"pkg:npm/%40vitest/mocker","source":"GHSA-xp26-3454-mjgp"},{"ecosystem":"npm","fixed":["5.0.3"],"introduced":["5.0.0-rc.2"],"last_affected":[],"package":"@vitest/mocker","purl":null,"source":"GHSA-xp26-3454-mjgp"},{"ecosystem":"npm","fixed":["5.0.3"],"introduced":["5.0.0-rc.2"],"last_affected":[],"package":"@vitest/mocker","purl":"pkg:npm/%40vitest/mocker","source":"GHSA-xp26-3454-mjgp"}],"prev":{"headline":"Vitest: Code injection via unauthenticated manual mock registration","id":"CVE-2026-112949"},"products":["mocker","vitest"],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["@vitest","vitest-dev"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-112950/"}