{"answers":{"affected":"2 open source packages ship an affected version, including svelte. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27119 in the wild and no public exploit code.","fix":"Upgrade svelte to 5.51.5 or later.","what":"CVE-2026-27119 is a medium-severity cross-site scripting vulnerability in sveltejs svelte, published on 20 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27119 and fix it if it is affected.\n\nWhat it is: CVE-2026-27119 is a medium-severity cross-site scripting vulnerability in sveltejs svelte, published on 20 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27119 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- svelte (npm): affected from 5.39.3; fixed in 5.51.5\n- svelte (npm): affected from 5.39.3; fixed in 5.51.5\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-27119/ (Markdown: https://insights.sbomify.com/CVE-2026-27119/index.md)","id":"CVE-2026-27119","markdown":"https://insights.sbomify.com/CVE-2026-27119/index.md","name":"CVE-2026-27119","record":{"aliases":["GHSA-h7h7-mm68-gmrc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Svelte web framework","requires_auth":"high_privilege","summary":"Attackers can inject HTML via unescaped SSR option elements, potentially leading to code execution in server-rendered applications.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"svelte","vendor":"svelte"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"svelte performance oriented web framework. From 5.39.3, \u003c=5.51.4, in certain circumstances, the server-side rendering output of an \u003coption\u003e element does not properly escape its content, potentially allowing HTML injection in the SSR output. Client-side rendering is not affected. This vulnerability is fixed in 5.51.5.","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":"Svelte affected by XSS in SSR `\u003coption\u003e` element","id":"CVE-2026-27119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Leaf-kit html escaping does not work on characters that are part of extended grapheme cluster","id":"CVE-2026-27120"},"packages":[{"ecosystem":"npm","fixed":["5.51.5"],"introduced":["5.39.3"],"last_affected":[],"package":"svelte","purl":null,"source":"GHSA-h7h7-mm68-gmrc"},{"ecosystem":"npm","fixed":["5.51.5"],"introduced":["5.39.3"],"last_affected":[],"package":"svelte","purl":"pkg:npm/svelte","source":"GHSA-h7h7-mm68-gmrc"}],"prev":{"headline":"Cache poisoning in @sveltejs/adapter-vercel","id":"CVE-2026-27118"},"products":["svelte"],"published":"2026-02-20","related":[{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2021-29261","kev_date_added":null,"published":"2021-04-05"},{"cvss_score":5.9,"headline":"Svelte: ReDoS in `\u003csvelte:element\u003e` Tag Validation","id":"CVE-2026-42567","kev_date_added":null,"published":"2026-06-09"},{"cvss_score":5.4,"headline":"Potential mXSS vulnerability due to improper HTML escaping in svelte","id":"CVE-2024-45047","kev_date_added":null,"published":"2024-08-30"},{"cvss_score":5.4,"headline":"Cross-site Scripting (XSS)","id":"CVE-2022-25875","kev_date_added":null,"published":"2022-07-12"},{"cvss_score":5.3,"headline":"Svelte: XSS via DOM Clobbering of Internal Framework State","id":"CVE-2026-42573","kev_date_added":null,"published":"2026-06-09"},{"cvss_score":5.3,"headline":"Svelte vulnerable to XSS during SSR with contenteditable `bind:innerText` and `bind:textContent`","id":"CVE-2026-27901","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":5.3,"headline":"Svelte Vulnerable to XSS via HTML Comment Injection in SSR Error Boundary Hydration Markers","id":"CVE-2026-27902","kev_date_added":null,"published":"2026-02-26"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-02-23","vendors":["sveltejs"]},"summary":"Attackers can inject HTML via unescaped SSR option elements, potentially leading to code execution in server-rendered applications.","url":"https://insights.sbomify.com/CVE-2026-27119/"}