astro (npm) has 30 known vulnerabilities, the worst rated CRITICAL. Upgrade to 7.4.7 or later to clear all of them. No malicious-package signal is recorded.
A vulnerability in libheif, used by the default Sharp image service in Astro, can lead to remote code execution when a malicious AVIF image is optimized.
CyberXYZ does not call a package safe in absolute terms. It records 30 known vulnerabilities for astro (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does astro have known vulnerabilities?
Yes. CyberXYZ records 30 known vulnerabilities for astro (npm), the worst rated CRITICAL. These include GHSA-26w7-cxv4-gfx2, GHSA-vj59-8hwv-xxmv, GHSA-8hv8-536x-4wqp, GHSA-2pvr-wf23-7pc7, GHSA-wrwg-2hg8-v723.
Which version of astro should I use?
7.4.7 or later clears every advisory recorded for astro (npm). Check the release you pick before installing it.
How do I check astro before installing?
Search astro in CyberXYZ Check at https://cyberxyz.io/check?q=astro. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:33 UTC. The most recent advisory here was published 2026-11-13. Updated continuously from NVD, GHSA, OSV and CNA feeds.