{"answers":{"affected":"2 open source packages ship an affected version, including @quasar/app-vite.","exploited":"There is no known exploitation of CVE-2026-106107 in the wild and no public exploit code.","fix":"Upgrade @quasar/app-vite to 3.3.0 or later.","what":"CVE-2026-106107 is a high-severity cross-site scripting vulnerability in @quasar app-vite, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-106107 and fix it if it is affected.\n\nWhat it is: CVE-2026-106107 is a high-severity cross-site scripting vulnerability in @quasar app-vite, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-106107 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @quasar/app-vite (npm): affected all versions; fixed in 3.3.0\n- @quasar/app-vite (npm): affected all versions; 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-106107/ (Markdown: https://insights.sbomify.com/CVE-2026-106107/index.md)","id":"CVE-2026-106107","markdown":"https://insights.sbomify.com/CVE-2026-106107/index.md","name":"CVE-2026-106107","record":{"aliases":["GHSA-5m6h-8g35-p3m7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Vue.js UI framework","requires_auth":"none","summary":"Attackers can inject malicious HTML attributes into SSR/SSG output if the nonce value is attacker-controlled, leading to XSS.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 3.3.0, several @quasar/app-vite SSR and SSG rendering paths interpolated ssrContext.nonce directly into quoted HTML attributes. An application that derives or overrides this value with attacker-controlled data can allow a quote to terminate the nonce attribute and inject additional attributes or markup into generated HTML across development and production SSR or SSG output. Cryptographically generated base64 or base64url nonces are not affected because they lack HTML attribute delimiters. 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 SSR and SSG nonce attributes are not safely constrained","id":"CVE-2026-106107","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory","id":"CVE-2026-106108"},"packages":[{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["0"],"last_affected":[],"package":"@quasar/app-vite","purl":null,"source":"GHSA-5m6h-8g35-p3m7"},{"ecosystem":"npm","fixed":["3.3.0"],"introduced":["0"],"last_affected":[],"package":"@quasar/app-vite","purl":"pkg:npm/%40quasar/app-vite","source":"GHSA-5m6h-8g35-p3m7"}],"prev":{"headline":"Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its \u003c/script\u003e escape is bypassable","id":"CVE-2026-106106"},"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 can inject malicious HTML attributes into SSR/SSG output if the nonce value is attacker-controlled, leading to XSS.","url":"https://insights.sbomify.com/CVE-2026-106107/"}