CVE-2026-59729

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-49580 (ENISA EUVD) · GHSA-f48w-9m4c-m7f5 (GitHub Security Advisories)Source: ENISA EUVD

5.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Astro is a web framework for content-driven websites. Versions prior to 7.0.6 are vulnerable to XSS through unescaped spread attribute names in renderHTMLElement. The fix for CVE-2026-54298 (GHSA-jrpj-wcv7-9fh9) added an INVALID_ATTR_NAME_CHAR guard to addAttribute() so that spread-prop attribute names containing "' >/= or whitespace are dropped. A second attribute-rendering path, renderHTMLElement() in packages/astro/src/runtime/server/render/dom.ts, has its own inline attribute loop that does not go through addAttribute() and was not updated. It interpolates the attribute name unescaped and only escapes the value, so untrusted prop keys spread onto a native-HTMLElement-subclass component can still break out of the attribute context. This issue has been fixed in version 7.0.6.

CVSS
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 20, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Jul 27, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

[email protected]

Patch available: withastro/astro [email protected]

https://github.com/withastro/astro/releases/tag/[email protected]
GitHub commit Patch Available

commit 5240e26c9dd9 (withastro/astro)

Patch available: withastro/astro [email protected] (contains commit 5240e26c9dd9)

https://github.com/withastro/astro/commit/5240e26c9dd91f9bc7140dcfacdb48d5a132830d
GitHub pull request Patch Available

Validate attribute names on custom HTML elements during SSR

Patch available: withastro/astro [email protected] (PR #17251 merged 2026-07-02)

https://github.com/withastro/astro/pull/17251
GitHub advisoryMentions a patch (unverified)

XSS via unescaped spread attribute names in custom element rendering · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-f48w-9m4c-m7f5

Vendor Advisories for CVE-2026-59729(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmastro @ 7.0.6 (fixes < 7.0.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
astro—
  • every version up to 7.0.6: fixed in 7.0.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 156 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 56 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-f48w-9m4c-m7f5 · GitHub severity MODERATE
  15. 2026-11-01 07:42 UTCEchelonGraph re-scored
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-29 16:38 UTCEchelonGraph re-scored
  19. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-25 14:16 UTCEchelonGraph re-scored
  25. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-24 13:34 UTCEchelonGraph re-scored
  2. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-22 20:56 UTCEchelonGraph re-scored
  4. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-18 03:27 UTCEchelonGraph re-scored
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-12 15:52 UTCEchelonGraph re-scored
  17. 2026-10-11 19:36 UTCEchelonGraph re-scored
  18. 2026-10-11 16:51 UTCEchelonGraph re-scored
  19. 2026-10-11 14:13 UTCEchelonGraph re-scored
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-04 14:53 UTCEchelonGraph re-scored
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-01 07:38 UTCEchelonGraph re-scored
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-09-28 06:17 UTCEchelonGraph re-scored
  37. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-09-24 04:11 UTCEchelonGraph re-scored
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  42. 2026-09-23 01:35 UTCEchelonGraph re-scored
  43. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  44. 2026-09-20 06:09 UTCEchelonGraph re-scored
  45. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-09-18 03:54 UTCEchelonGraph re-scored
  47. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-09-16 12:45 UTCEchelonGraph re-scored
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  51. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  53. 2026-09-13 15:59 UTCEchelonGraph re-scored
  54. 2026-09-12 12:34 UTCEchelonGraph re-scored
  55. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  56. 2026-09-11 09:17 UTCEchelonGraph re-scored
  57. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  58. 2026-09-09 11:45 UTCEchelonGraph re-scored
  59. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-09-07 22:47 UTCEchelonGraph re-scored
  61. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-09-06 11:36 UTCEchelonGraph re-scored
  64. 2026-09-05 09:19 UTCEchelonGraph re-scored
  65. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  66. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-09-02 01:02 UTCEchelonGraph re-scored
  68. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-08-31 04:43 UTCEchelonGraph re-scored
  71. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  72. 2026-08-30 02:28 UTCEchelonGraph re-scored
  73. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  74. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  75. 2026-08-27 15:12 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-59729?
CVE-2026-59729 is a medium-severity vulnerability; its CVE record was published on July 20, 2026. Astro is a web framework for content-driven websites. Versions prior to 7.0.6 are vulnerable to XSS through unescaped spread attribute names in renderHTMLElement. The fix for CVE-2026-54298 (GHSA-jrpj-wcv7-9fh9) added an INVALID_ATTR_NAME_CHAR guard to addAttribute() so that spread-prop attribute…
When was the CVE record for CVE-2026-59729 published?
The CVE record for CVE-2026-59729 was published on July 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-59729 actively exploited?
CVE-2026-59729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59729?
CVE-2026-59729 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59729?
A fix for CVE-2026-59729 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59729 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59729?

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

Book a Demo →Browse All CVEs