Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Astro | Astro | < 6.1.10 |
Related Weaknesses (CWE)
References
- https://github.com/withastro/astro/commit/3d82220a1549e699e34ed433f3846a919f4c02Patch
- https://github.com/withastro/astro/pull/16457Issue TrackingPatch
- https://github.com/withastro/astro/security/advisories/GHSA-xr5h-phrj-8vxvVendor Advisory
FAQ
What is CVE-2026-45028?
CVE-2026-45028 is a vulnerability with a CVSS score of 6.1 (MEDIUM). 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 cipherte...
How severe is CVE-2026-45028?
CVE-2026-45028 has been rated MEDIUM with a CVSS base score of 6.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-45028?
Check the references section above for vendor advisories and patch information. Affected products include: Astro Astro.