CVE-2026-41322 @astrojs/node: Cache Poisoning due to incorrect error handling when if-match header is malformed
Attackers can cause persistent denial of service for static assets by triggering cache poisoning via malformed headers in the Astro Node adapter.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41322?
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.
Official 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.
Weakness: CWE-525
Which versions are affected by CVE-2026-41322?
2 open source packages ship an affected version, including @astrojs/node.
| Package | Affected | Fixed in |
|---|---|---|
@astrojs/node npm | All versions | 10.0.5 |
@astrojs/node npm | All versions | 10.0.5 |
How do I fix CVE-2026-41322?
Upgrade @astrojs/node to 10.0.5 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-41322 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41322 exists.
Sources
Also known as GHSA-c57f-mm3j-27q9.