Quick answers
- Is CVE-2026-126364 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126364 being exploited in the wild.
- How severe is CVE-2026-126364?
- Informational severity, published 13 November 2026.
- Which products and versions are affected?
- Astro 5.14.3 to 7.4.6.
- Is there a fix for CVE-2026-126364?
- Yes: fixed in 7.4.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126364 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-126364?
- Check whether you run Astro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.4.7
Technical details
The /_image endpoint's path containment check incorrectly lowercased paths on all filesystems before comparison, causing case-sensitive filesystem directories differing only in capitalization to bypass the check. On case-sensitive systems, a directory like "DIST/client" would be treated as within "dist/client", allowing directory traversal to sibling paths. The vulnerability affects versions 5.14.3 through 7.4.6 with the @astrojs/node adapter, on-demand rendering enabled, and a case-sensitive filesystem with a preexisting case-variant sibling directory; it is fixed by comparing paths case-sensitively on non-Windows systems.
Affected products
- Astro Astro 5.14.3 to 7.4.6
Timeline
- 2026-11-13: disclosed
- 2026-11-05: patched: Astro 7.4.7 released