{"answers":{"affected":"2 open source packages ship an affected version, including astro.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59729 exists.","fix":"Upgrade astro to 7.0.6 or later.","what":"CVE-2026-59729 is a medium-severity cross-site scripting vulnerability in withastro astro, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59729 and fix it if it is affected.\n\nWhat it is: CVE-2026-59729 is a medium-severity cross-site scripting vulnerability in withastro astro, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59729 exists.\n\nAffected packages and fixed versions:\n- astro (npm): affected all versions; fixed in 7.0.6\n- astro (npm): affected all versions; fixed in 7.0.6\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-59729/ (Markdown: https://insights.sbomify.com/CVE-2026-59729/index.md)","id":"CVE-2026-59729","markdown":"https://insights.sbomify.com/CVE-2026-59729/index.md","name":"CVE-2026-59729","record":{"aliases":["CLSA-2026-1788892753","CLSA-2026-1788970606","CLSA-2026-1792161561","CLSA-2026-1792161703","CLSA-2026-1792161706","CLSA-2026-1792161792","CLSA-2026-1792161858","GHSA-f48w-9m4c-m7f5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Astro web framework","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via unescaped spread attribute names in Astro's renderHTMLElement function, affecting web applications built with the framework.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Astro is a web framework for content-driven websites. Versions prior to 7.0.6 are vulnerable to XSS through unescaped spread attribute names in renderHTMLElement. The fix for CVE-2026-54298 (GHSA-jrpj-wcv7-9fh9) added an INVALID_ATTR_NAME_CHAR guard to addAttribute() so that spread-prop attribute names containing \"' \u003e/= or whitespace are dropped. A second attribute-rendering path, renderHTMLElement() in packages/astro/src/runtime/server/render/dom.ts, has its own inline attribute loop that does not go through addAttribute() and was not updated. It interpolates the attribute name unescaped and only escapes the value, so untrusted prop keys spread onto a native-HTMLElement-subclass component can still break out of the attribute context. This issue has been fixed in version 7.0.6.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Astro: XSS via unescaped spread attribute names in renderHTMLElement (incomplete fix for CVE-2026-54298)","id":"CVE-2026-59729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect","id":"CVE-2026-59730"},"packages":[{"ecosystem":"npm","fixed":["7.0.6"],"introduced":["0"],"last_affected":[],"package":"astro","purl":null,"source":"GHSA-f48w-9m4c-m7f5"},{"ecosystem":"npm","fixed":["7.0.6"],"introduced":["0"],"last_affected":[],"package":"astro","purl":"pkg:npm/astro","source":"GHSA-f48w-9m4c-m7f5"}],"prev":{"headline":"@astrojs/rss: XML Injection via Unescaped RSS Feed Fields","id":"CVE-2026-59728"},"products":["astro"],"published":"2026-07-27","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["withastro"]},"summary":"Attackers can execute arbitrary scripts via unescaped spread attribute names in Astro's renderHTMLElement function, affecting web applications built with the framework.","url":"https://insights.sbomify.com/CVE-2026-59729/"}