CVE-2026-54298

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Astro is a web framework. Prior to 6.4.6, the spreadAttributes function in Astro's server-side rendering pipeline iterates over object keys and passes them directly to addAttribute, which interpolates the key into the HTML output without escaping. When a developer uses the spread syntax {...props} on an HTML element and the object keys come from an untrusted source (API, CMS, URL parameters), an attacker can inject arbitrary HTML attributes including event handlers like onmousemove, onclick, or break out of the attribute context entirely to inject new elements. This vulnerability is fixed in 6.4.6.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
5.5%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

XSS via Unescaped Attribute Names in Spread Props · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-jrpj-wcv7-9fh9

Vendor Advisories for CVE-2026-54298(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
astro6.4.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:15 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 20:08 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 18:38 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 16:43 UTCEG score recompute
  13. 2026-07-02 15:13 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 13:39 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 12:10 UTCEG score recompute
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 09:25 UTCEG score recompute
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 07:56 UTCEG score recompute
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 06:28 UTCEG score recompute
Show 16 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 04:59 UTCEG score recompute
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-25 03:31 UTCEG score recompute
  5. 2026-06-24 14:05 UTCEPSS rescore
  6. 2026-06-24 02:01 UTCEG score recompute
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 00:31 UTCEG score recompute 1.90
  10. 2026-06-22 21:37 UTCNVD updateCVSS v3 → 6.1
  11. 2026-06-21 23:00 UTCEG score recompute
  12. 2026-06-20 21:18 UTCEG score recompute
  13. 2026-06-19 19:49 UTCEG score recompute
  14. 2026-06-18 18:21 UTCEG score recompute
  15. 2026-06-17 16:52 UTCEG score recompute
  16. 2026-06-16 15:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54298?
CVE-2026-54298 is a medium vulnerability published on June 16, 2026. Astro is a web framework. Prior to 6.4.6, the spreadAttributes function in Astro's server-side rendering pipeline iterates over object keys and passes them directly to addAttribute, which interpolates the key into the HTML output without escaping. When a developer uses the spread syntax {...props}…
When was CVE-2026-54298 disclosed?
CVE-2026-54298 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54298 actively exploited?
CVE-2026-54298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54298?
CVE-2026-54298 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-54298?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54298, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54298

Explore →

Is Your Infrastructure Affected by CVE-2026-54298?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.