Vulnerability Database · npm · astro · Version
astro 7.0.5
7.0.5 is affected by 7 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 0 Medium 5 Low 0 Unrated 0
-
Released 01 Jul 2026
Licence MIT
Also known from other sources 6
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
astro 7.0.5 vulnerabilities
7 vulnerabilities cover astro 7.0.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Remote Code Execution Vulnerability in Astro Package Due to AVIF Image Optimization | 9.8 critical | 7.2.8 | 08 Sep 2026 |
| CVE-2026-114128: Astro JSX and MDX rendering can enable cross-site scripting | 6.5 medium | 7.3.2 | 22 Oct 2026 |
| CVE-2026-84376: Astro Package Authorization Bypass Due to Path-Segment Boundary Check Failure | 6.3 medium | 7.2.4 | 08 Sep 2026 |
| Reflected XSS Vulnerability in Astro Package: Unescaped View Transition Animation Properties | 5.3 medium | 7.1.0 | 20 Jul 2026 |
| Cross-Site Request Forgery (CSRF) Vulnerability in Astro Package: Bypass of Origin Check | 5.1 medium | 7.0.6 | 20 Jul 2026 |
| CVE-2026-59729: Astro XSS Vulnerability via Unescaped Spread Attribute Names | 5.1 medium | 7.0.6 | 20 Jul 2026 |
| Malicious Code Injection in astro Package - Version 7.1.0 | N/A critical | No fix published | 16 Jul 2026 |
Looking for another version, or everything Vulert holds for astro?
Questions
About astro 7.0.5
Is astro 7.0.5 vulnerable?
Yes. 7 vulnerabilities in the Vulert database cover astro 7.0.5: 2 critical, 0 high, 5 medium and 0 low. Each entry above names the fixed version to move to.
Is 7.0.5 the latest release of astro?
No. 7.0.5 was published 01 Jul 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
What does a malicious-package vulnerability mean?
It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.
How do I monitor astro for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the astro version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.