{"answers":{"affected":"2 open source packages ship an affected version, including @astrojs/node.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41322 exists.","fix":"Upgrade @astrojs/node to 10.0.5 or later.","what":"CVE-2026-41322 is a medium-severity denial of service vulnerability in withastro astro, published on 24 Apr 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-41322 and fix it if it is affected.\n\nWhat it is: CVE-2026-41322 is a medium-severity denial of service vulnerability in withastro astro, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41322 exists.\n\nAffected packages and fixed versions:\n- @astrojs/node (npm): affected all versions; fixed in 10.0.5\n- @astrojs/node (npm): affected all versions; fixed in 10.0.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-41322/ (Markdown: https://insights.sbomify.com/CVE-2026-41322/index.md)","id":"CVE-2026-41322","markdown":"https://insights.sbomify.com/CVE-2026-41322/index.md","name":"CVE-2026-41322","record":{"aliases":["GHSA-c57f-mm3j-27q9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Astro Node adapter","requires_auth":"none","summary":"Attackers can cause persistent denial of service for static assets by triggering cache poisoning via malformed headers in the Astro Node adapter.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-525","name":"Use of Web Browser Cache Containing Sensitive Information"}],"description":"@astrojs/node allows Astro to deploy your SSR site to Node targets. Prior to 10.0.5, requesting a static js/css resources from _astro path with an incorrect/malformed if-match header returns a 500 error with a one year cache lifetime instead of 412 in some cases. This has the effect that all subsequent requests to that file, regardless of if-match header will be served a 5xx error instead of the file until the cache expires. This vulnerability is fixed in 10.0.5.","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":"@astrojs/node: Cache Poisoning due to incorrect error handling when if-match header is malformed","id":"CVE-2026-41322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Kyverno: ServiceAccount token leaked to external servers via apiCall service URL","id":"CVE-2026-41323"},"packages":[{"ecosystem":"npm","fixed":["10.0.5"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":null,"source":"GHSA-c57f-mm3j-27q9"},{"ecosystem":"npm","fixed":["10.0.5"],"introduced":["0"],"last_affected":[],"package":"@astrojs/node","purl":"pkg:npm/%40astrojs/node","source":"GHSA-c57f-mm3j-27q9"}],"prev":{"headline":"@astrojs/cloudflare: SSRF via redirect following in Cloudflare image-binding-transform endpoint","id":"CVE-2026-41321"},"products":["astro"],"published":"2026-04-24","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-25","vendors":["withastro"]},"summary":"Attackers can cause persistent denial of service for static assets by triggering cache poisoning via malformed headers in the Astro Node adapter.","url":"https://insights.sbomify.com/CVE-2026-41322/"}