CVE-2026-59727

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th 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-49581 (ENISA EUVD) · GHSA-7pw4-f3q4-r2p2 (GitHub Security Advisories)Source: ENISA EUVD

2.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.4%CVSS: 2.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Astro is a web framework for content-driven websites. In versions 3.10.0 through 7.0.3, when a transition:persist, transition:scope, or transition:persist-props directive is applied to a client-hydrated (client:*) component, Astro copied the directive value onto the rendered element without HTML-escaping it. If a developer reflects attacker-controlled input into one of these directives, an attacker can break out of the attribute and inject arbitrary HTML/JavaScript into the server-rendered output, resulting in reflected cross-site scripting (XSS). Exploitation requires the application developer to have written a non-idiomatic pattern — passing untrusted, request-derived input directly into a transition directive. Astro applications that do not route untrusted input into these directives are unaffected. This issue has been fixed in version 7.0.4.

CVSS
2.1
EG Score
2.1LOWmedium confidence
EG Risk
25
EG Risk 25/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)
Severity21% × 45%
Impact severity (EG Severity): CVSS 2.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.4%
EPSS %ILE
34th
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 (2.1): severity, escalated by confirmed exploitation. This CVE's 2.1 is its impact severity (EG Severity), not escalated.

EG Severity
2.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% 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

References (4)

Vendor Advisories for CVE-2026-59727(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.4 (fixes >= 3.10.0, < 7.0.4)—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—
  • 3.10.0 up to 7.0.4: fixed in 7.0.4
—

Weakness Classification(3)

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-59727?
CVE-2026-59727 is a low-severity vulnerability; its CVE record was published on July 20, 2026. Astro is a web framework for content-driven websites. In versions 3.10.0 through 7.0.3, when a transition:persist, transition:scope, or transition:persist-props directive is applied to a client-hydrated (client:*) component, Astro copied the directive value onto the rendered <astro-island> element…
When was the CVE record for CVE-2026-59727 published?
The CVE record for CVE-2026-59727 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-59727 actively exploited?
CVE-2026-59727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59727?
CVE-2026-59727 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59727?
A fix for CVE-2026-59727 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59727 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-59727

Explore →

Is Your Infrastructure Affected by CVE-2026-59727?

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

Book a Demo →Browse All CVEs