{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126361 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.","fix":"No fix has been published for CVE-2026-126361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126361 is a low-severity cross-site scripting vulnerability in withastro astro, published on 12 Nov 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-126361 and fix it if it is affected.\n\nWhat it is: CVE-2026-126361 is a low-severity cross-site scripting vulnerability in withastro astro, published on 12 Nov 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: There is no known exploitation of CVE-2026-126361 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.\n\nAffected product: withastro astro. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-126361/ (Markdown: https://insights.sbomify.com/CVE-2026-126361/index.md)","id":"CVE-2026-126361","markdown":"https://insights.sbomify.com/CVE-2026-126361/index.md","name":"CVE-2026-126361","record":{"aliases":["GHSA-mh32-jxcr-mh9f"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript web framework","requires_auth":"none","requires_specific_call":true,"summary":"Untrusted data used as element names can inject event-handler markup into Astro pages, enabling XSS; Astro site developers should care.","user_interaction":"required","vuln_class":"xss","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"Astro is a web framework for content-driven websites. Prior to 7.4.5, Astro rendered a string used as a dynamic element name as raw HTML after applying an incomplete character filter. A / in the string could make an HTML parser treat the remainder as attributes, allowing untrusted element-name input to inject event-handler markup. The .astro dynamic-tag renderer, JSX renderer, and MDX renderer were affected, and exploitation required an application to use request-controlled or stored untrusted data as all or part of an element name. This issue is fixed in version 7.4.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Astro: XSS via attribute injection in dynamic tag names","id":"CVE-2026-126361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Astro: Reflected XSS via unescaped slot names in @astrojs/svelte","id":"CVE-2026-126362"},"nickname":null,"packages":[],"prev":{"headline":"OpenTelemetry Python: Denial of service through quadratic-time traceparent parsing in opentelemetry-api","id":"CVE-2026-126360"},"products":["astro"],"published":"2026-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["withastro"]},"summary":"Untrusted data used as element names can inject event-handler markup into Astro pages, enabling XSS; Astro site developers should care.","url":"https://insights.sbomify.com/CVE-2026-126361/"}