{"answers":{"affected":"2 open source packages ship an affected version, including @astrojs/node.","exploited":"There is no known exploitation of CVE-2026-102984 in the wild and no public exploit code.","fix":"Upgrade @astrojs/node to 11.1.3 or later.","what":"CVE-2026-102984 is a high-severity denial of service vulnerability in withastro astro, published on 30 Sep 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-102984 and fix it if it is affected.\n\nWhat it is: CVE-2026-102984 is a high-severity denial of service vulnerability in withastro astro, published on 30 Sep 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-102984 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @astrojs/node (npm): affected all versions; fixed in 11.1.3\n- @astrojs/node (npm): affected all versions; fixed in 11.1.3\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-102984/ (Markdown: https://insights.sbomify.com/CVE-2026-102984/index.md)","id":"CVE-2026-102984","markdown":"https://insights.sbomify.com/CVE-2026-102984/index.md","name":"CVE-2026-102984","record":{"aliases":["GHSA-qh8j-hqjv-7m4x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Astro web framework","requires_auth":"none","summary":"A malformed Host header can crash the Astro Node adapter process when staticHeaders is enabled, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"Astro is a web framework for content-driven websites. Prior to 11.1.3, the @astrojs/node adapter builds a request URL from the Host header, and a malformed port can make that URL invalid. The recovery path reuses the same malformed host and throws an uncaught TypeError: Invalid URL before routing begins. In the default standalone configuration, the request returns an HTTP 500 response and the server continues running, but when staticHeaders is enabled the synchronous handler does not catch the exception and the Node process terminates. Proxies and CDNs that reject malformed Host headers prevent this path from reaching the origin. The issue affects availability only and does not expose data or permit code execution. This issue is fixed in version 11.1.3.","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":"Astro: Malformed port in the Host header can crash the Node adapter","id":"CVE-2026-102984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Plane: Any project member can modify (deactivate) other members' records","id":"CVE-2026-102985"},"packages":[{"ecosystem":"npm","fixed":["11.1.3"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":null,"source":"GHSA-qh8j-hqjv-7m4x"},{"ecosystem":"npm","fixed":["11.1.3"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":"pkg:npm/%40astrojs/node","source":"GHSA-qh8j-hqjv-7m4x"}],"prev":{"headline":"Astro: Netlify Image CDN allowlist bypass enables SSRF","id":"CVE-2026-102983"},"products":["astro"],"published":"2026-09-30","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-09-30","vendors":["withastro"]},"summary":"A malformed Host header can crash the Astro Node adapter process when staticHeaders is enabled, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-102984/"}