Skip to main content
VulnerabilityPublished Updated

CVE-2026-45028: withastro astro · Reusing a Nonce, Key Pair in Encryption

Affects withastro astroSource CVE Database V5

0
Compare

Public exploit available · CVSS 2.9 Low : upgrade to 6.1.10 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.1.10
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade withastro astro to 6.1.10.

Affected software

ProductAffectedFixed in
withastroastroAffected
  • <6.1.10
Fixed in
  • 6.1.10
npmastropkg:npm/astroOther threatsAffected
  • <6.1.10
Fixed in
  • 6.1.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Astro to version 6.1.10 or later, where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 6.1.10, applying this official fix is the recommended remediation. No additional mitigation steps are specified.

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.

References

Community reviews

Loading reviews…