CVSS 4.0
6.9 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NMedium (6.9) in astro astro. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in astro 4.16.19, 5.13.2.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:Nastro (npm): fixed in 5.13.2, 4.16.19@astrojs/node (npm): fixed in 9.1.1Explain CVE-2025-55303 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-55303?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-55303?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-55303 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| astro:astro | before 4.16.18 |
| astro:astro | from 5.0.0 before 5.13.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-xf8x-j4p2-f749 | npm | astro | >=5.0.0-alpha.0 <5.13.2 | 5.13.2 |
| GHSA-xf8x-j4p2-f749 | npm | @astrojs/node | <9.1.1 | 9.1.1 |
| GHSA-xf8x-j4p2-f749 | npm | astro | <4.16.19 | 4.16.19 |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.