CVE-2026-45028
Astro is a web framework. Astro versions prior to 6.1.10 used …
Astro is a web framework. Astro versions prior to 6.1.10 used AES-GCM encryption to protect the confidentiality and integrity of server island props and slots parameters, but did not bind the ciphertext to its intended component or parameter type. An attacker could replay one component's encrypted props (p) value as another component's slots (s) value, or vice versa. Since slots contain raw unescaped HTML while props may contain user-controlled values, this could lead to XSS in applications. This occurs when the application uses server islands, two different server island components share the same key name for a prop and a slot, and an attacker has full control over the value of the overlapping prop (requires a dynamically rendered page). This vulnerability is fixed in 6.1.10.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/withastro/astro/security/advisories/GHSA-xr5h-phrj-8vxv
- github.com/withastro/astro/pull/16457
- github.com/withastro/astro/commit/3d82220a1549e699e34ed433f3846a919f4c02bd
- github.com/advisories/GHSA-xr5h-phrj-8vxv
- nvd.nist.gov/vuln/detail/CVE-2026-45028
- nvd.nist.gov/vuln/detail/CVE-2026-45028
- cve.org/CVERecord?id=CVE-2026-45028
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.