{"answers":{"affected":"2 open source packages ship an affected version, including quasar.","exploited":"There is no known exploitation of CVE-2026-106102 in the wild and no public exploit code.","fix":"Upgrade quasar to 2.22.0 or later.","what":"CVE-2026-106102 is a critical cross-site scripting vulnerability in quasarframework quasar, 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-106102 and fix it if it is affected.\n\nWhat it is: CVE-2026-106102 is a critical cross-site scripting vulnerability in quasarframework quasar, 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-106102 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quasar (npm): affected all versions; fixed in 2.22.0\n- quasar (npm): affected all versions; fixed in 2.22.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-106102/ (Markdown: https://insights.sbomify.com/CVE-2026-106102/index.md)","id":"CVE-2026-106102","markdown":"https://insights.sbomify.com/CVE-2026-106102/index.md","name":"CVE-2026-106102","record":{"aliases":["GHSA-pq96-jpmf-w254"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Vue.js UI framework","requires_auth":"none","summary":"Attackers can inject executable scripts via unescaped SSR meta tags in Quasar Framework, affecting server-rendered pages.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"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 2.22.0, the SSR-only getHead() serializer in ui/src/plugins/meta/Meta.js used getAttr() to interpolate values supplied through useMeta() into title, meta, link, and script markup without HTML text or quoted-attribute encoding. injectServerMeta() appended that output to the raw server-rendered response. An attacker who can influence dynamic page metadata, such as a post title, product name, excerpt, or display name, can terminate the intended HTML context and inject executable markup before hydration. The client-side apply() path is not affected because it uses DOM APIs that encode attributes. This issue is fixed in version 2.22.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: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()","id":"CVE-2026-106102","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: Path Traversal / Arbitrary File Write via crafted Icon Genie profile","id":"CVE-2026-106103"},"packages":[{"ecosystem":"npm","fixed":["2.22.0"],"introduced":["0"],"last_affected":[],"package":"quasar","purl":null,"source":"GHSA-pq96-jpmf-w254"},{"ecosystem":"npm","fixed":["2.22.0"],"introduced":["0"],"last_affected":[],"package":"quasar","purl":"pkg:npm/quasar","source":"GHSA-pq96-jpmf-w254"}],"prev":{"headline":"Quasar Framework: DOM Clobbering in Quasar openURL() SafariViewController Integration Causes Client-Side Denial of Service","id":"CVE-2026-106101"},"products":["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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["quasarframework"]},"summary":"Attackers can inject executable scripts via unescaped SSR meta tags in Quasar Framework, affecting server-rendered pages.","url":"https://insights.sbomify.com/CVE-2026-106102/"}