{"answers":{"affected":"2 open source packages ship an affected version, including @quasar/app-vite.","exploited":"There is no known exploitation of CVE-2026-106108 in the wild and no public exploit code.","fix":"Upgrade @quasar/app-vite to 3.3.0 or later.","what":"CVE-2026-106108 is a medium-severity path traversal vulnerability in @quasar app-vite, published on 13 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-106108 and fix it if it is affected.\n\nWhat it is: CVE-2026-106108 is a medium-severity path traversal vulnerability in @quasar app-vite, published on 13 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-106108 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @quasar/app-vite (npm): affected from 3.1.0; fixed in 3.3.0\n- @quasar/app-vite (npm): affected from 3.1.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-106108/ (Markdown: https://insights.sbomify.com/CVE-2026-106108/index.md)","id":"CVE-2026-106108","markdown":"https://insights.sbomify.com/CVE-2026-106108/index.md","name":"CVE-2026-106108","record":{"aliases":["GHSA-vhhq-m2gm-rwc9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Quasar Framework","requires_auth":"none","summary":"Attackers can write files outside the build directory if SSG page definitions are derived from untrusted content, requiring a build process that trusts external inputs.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"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 3.1.0 until 3.3.0, @quasar/app-vite SSG page definitions returned by getSsgPages() could supply dir and filename values that were joined to build.distDir without verifying the final destination. Parent traversal or an existing symlink below the distribution directory could create new HTML files or directories outside the output tree with the build user's permissions. Application configuration and SSG page definitions are trusted by default, so exploitation requires a build process that derives them from external or otherwise less-trusted content; existing files remain protected by the renderer's no-overwrite behavior. 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 SSG page output paths can escape the configured distribution directory","id":"CVE-2026-106108","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":"Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories","id":"CVE-2026-106109"},"packages":[{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["3.1.0"],"last_affected":[],"package":"@quasar/app-vite","purl":null,"source":"GHSA-vhhq-m2gm-rwc9"},{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["3.1.0"],"last_affected":[],"package":"@quasar/app-vite","purl":"pkg:npm/%40quasar/app-vite","source":"GHSA-vhhq-m2gm-rwc9"}],"prev":{"headline":"Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained","id":"CVE-2026-106107"},"products":["app-vite","quasar"],"published":"2026-10-13","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-13","vendors":["@quasar","quasarframework"]},"summary":"Attackers can write files outside the build directory if SSG page definitions are derived from untrusted content, requiring a build process that trusts external inputs.","url":"https://insights.sbomify.com/CVE-2026-106108/"}