CVE-2026-59727

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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, secondary
Elevated
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: Elevated riskExposed: 0

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

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 v3
2.1
EG Score
2.1(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity21% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 28, 2026

References (5)

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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
astro—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 / 33× 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-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-09 11:45 UTCEG score recompute
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 09:19 UTCEG score recompute
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 03:24 UTCEG score recompute
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:42 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 21:41 UTCEG score recompute
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-23 14:17 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 08:34 UTCEG score recompute
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 33 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 02:52 UTCEG score recompute
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 21:09 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-10 15:22 UTCEG score recompute
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-07 09:39 UTCEG score recompute
  14. 2026-08-06 13:47 UTCEPSS rescore
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-04 03:57 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-31 22:14 UTCEG score recompute
  22. 2026-07-30 16:28 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-28 16:31 UTCEG score recompute
  26. 2026-07-28 15:39 UTCEG score recompute
  27. 2026-07-28 15:37 UTCEPSS rescore
  28. 2026-07-27 20:22 UTCEG score recompute
  29. 2026-07-27 19:55 UTCEG score recompute▲ 2.10
  30. 2026-07-27 19:54 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
  31. 2026-07-26 10:45 UTCEG score recompute
  32. 2026-07-23 03:21 UTCEG score recompute
  33. 2026-07-20 23:33 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59727?
CVE-2026-59727 is a low vulnerability 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 CVE-2026-59727 disclosed?
CVE-2026-59727 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59727 actively exploited?
CVE-2026-59727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.5% of all scored CVEs.
What is the CVSS score of CVE-2026-59727?
CVE-2026-59727 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-59727?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59727, 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-59727

Explore →

Is Your Infrastructure Affected by CVE-2026-59727?

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

Start Free Scan →Browse All CVEs