withastro up to 6.1.9 nonce re-use

Summaryinfo

A vulnerability identified as problematic has been detected in withastro astro up to 6.1.9. The impacted element is an unknown function. Performing a manipulation results in nonce re-use. This vulnerability is known as CVE-2026-45028. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in withastro astro up to 6.1.9. This affects some unknown functionality. The manipulation with an unknown input leads to a nonce re-use vulnerability. CWE is classifying the issue as CWE-323. Nonces should be used for the present occasion and only once. This is going to have an impact on integrity. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-45028 since 05/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 6.1.10 eliminates this vulnerability. Applying the patch 3d82220a1549e699e34ed433f3846a919f4c02bd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• withastro

Name

• astro

Version

• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9

License

• open-source

Website

• Product: https://github.com/withastro/astro/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion