CVE-2026-50146

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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
Elevated
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.3.3, when a component uses a client:* directive, Astro inserts named slot content into a data-astro-template attribute without HTML escaping the slot name allowing an attacker to break out of the attribute context and inject arbitrary HTML, resulting in reflected XSS during SSR. This vulnerability is fixed in 6.3.3.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
7.4%
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

Reflected XSS via unescaped slot name · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-8hv8-536x-4wqp

Vendor Advisories for CVE-2026-50146(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 47× 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:16 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 10:20 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 09:21 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 08:12 UTCEG score recompute
  9. 2026-07-02 07:19 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 06:27 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 05:35 UTCEG score recompute
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 04:42 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 03:47 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-27 02:55 UTCEG score recompute
  23. 2026-06-26 02:03 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 01:07 UTCEG score recompute
Show 22 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-24 00:15 UTCEG score recompute
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 15:32 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  6. 2026-06-23 14:35 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  7. 2026-06-22 23:21 UTCEG score recompute▼ 1.00
  8. 2026-06-22 21:37 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  9. 2026-06-22 12:28 UTCEG score recompute
  10. 2026-06-22 01:31 UTCEG score recompute
  11. 2026-06-21 14:35 UTCEG score recompute
  12. 2026-06-21 03:42 UTCEG score recompute
  13. 2026-06-20 16:49 UTCEG score recompute
  14. 2026-06-20 05:53 UTCEG score recompute
  15. 2026-06-19 18:17 UTCEG score recompute
  16. 2026-06-19 07:26 UTCEG score recompute
  17. 2026-06-18 20:30 UTCEG score recompute
  18. 2026-06-18 09:37 UTCEG score recompute
  19. 2026-06-17 22:45 UTCEG score recompute
  20. 2026-06-17 11:53 UTCEG score recompute
  21. 2026-06-17 01:01 UTCEG score recompute
  22. 2026-06-16 14:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50146?
CVE-2026-50146 is a medium vulnerability published on June 16, 2026. Astro is a web framework. Prior to 6.3.3, when a component uses a client:* directive, Astro inserts named slot content into a data-astro-template attribute without HTML escaping the slot name allowing an attacker to break out of the attribute context and inject arbitrary HTML, resulting in…
When was CVE-2026-50146 disclosed?
CVE-2026-50146 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-50146 actively exploited?
CVE-2026-50146 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50146?
CVE-2026-50146 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-50146?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50146, 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

Explore the affected products and dependency analysis for CVE-2026-50146

Explore →

Is Your Infrastructure Affected by CVE-2026-50146?

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

Start Free Scan →Browse All CVEs