{"answers":{"affected":"2 open source packages ship an affected version, including @quasar/app-vite.","exploited":"There is no known exploitation of CVE-2026-106109 in the wild and no public exploit code.","fix":"Upgrade @quasar/app-vite to 3.3.0 or later.","what":"CVE-2026-106109 is a medium-severity path traversal vulnerability in @quasar app-vite, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-106109 and fix it if it is affected.\n\nWhat it is: CVE-2026-106109 is a medium-severity path traversal vulnerability in @quasar app-vite, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-106109 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @quasar/app-vite (npm): affected from 1.0.0; fixed in 3.3.0\n- @quasar/app-vite (npm): affected from 1.0.0; fixed in 3.3.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-106109/ (Markdown: https://insights.sbomify.com/CVE-2026-106109/index.md)","id":"CVE-2026-106109","markdown":"https://insights.sbomify.com/CVE-2026-106109/index.md","name":"CVE-2026-106109","record":{"aliases":["GHSA-q9mq-245r-4g93"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Vue.js UI framework","requires_auth":"high_privilege","summary":"Attackers with build configuration control can delete arbitrary files by specifying unsafe output directories during the Vite build process.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Quasar Framework is a framework for building high-performance Vue.js user interfaces. From 1.0.0 until 3.3.0, @quasar/app-vite recursively removed the resolved build.distDir before building without rejecting the project root, user home directory, filesystem roots, or symlink-resolved external directories. An unsafe trusted configuration can delete data writable by the build user before compilation begins. No attacker-controlled input reaches build.distDir by default, so exploitation requires compromised or less-trusted automation to influence build configuration, or a developer to run a mistaken configuration. This issue is fixed in version 3.3.0.","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":"Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories","id":"CVE-2026-106109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"ImageSharp: TIFF CCITT T4 encoder can write past its compressed output buffer","id":"CVE-2026-106110"},"packages":[{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["1.0.0"],"last_affected":[],"package":"@quasar/app-vite","purl":null,"source":"GHSA-q9mq-245r-4g93"},{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["1.0.0"],"last_affected":[],"package":"@quasar/app-vite","purl":"pkg:npm/%40quasar/app-vite","source":"GHSA-q9mq-245r-4g93"}],"prev":{"headline":"Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory","id":"CVE-2026-106108"},"products":["app-vite","quasar"],"published":"2026-10-06","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-06","vendors":["@quasar","quasarframework"]},"summary":"Attackers with build configuration control can delete arbitrary files by specifying unsafe output directories during the Vite build process.","url":"https://insights.sbomify.com/CVE-2026-106109/"}