CVE-2026-54299

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: 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, Astro SSR apps with prerendered error pages (/404 or /500 using export const prerender = true) fetch those pages over HTTP at runtime when an error occurs. The URL for this fetch is derived from request.url, which in turn gets its origin from the incoming Host header. When the Host header is not validated against allowedDomains, an attacker can point the fetch at an arbitrary host and read the response. This vulnerability is fixed in 6.4.6.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
9.5%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
github Patch Available

Host header SSRF in prerendered error page fetch · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-2pvr-wf23-7pc7

Vendor Advisories for CVE-2026-54299(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—6.4.6—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 59× 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 23:20 UTCEG score recompute
  7. 2026-07-05 10:46 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 22:13 UTCEG score recompute
  11. 2026-07-04 09:42 UTCEG score recompute
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 21:09 UTCEG score recompute
  15. 2026-07-03 08:37 UTCEG score recompute
  16. 2026-07-02 20:06 UTCEG score recompute
  17. 2026-07-02 07:34 UTCEG score recompute
  18. 2026-07-01 19:01 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 06:30 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 17:58 UTCEG score recompute
  23. 2026-06-30 05:27 UTCEG score recompute
  24. 2026-06-29 16:54 UTCEG score recompute
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 34 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 04:21 UTCEG score recompute
  3. 2026-06-28 15:46 UTCEG score recompute
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 03:11 UTCEG score recompute
  8. 2026-06-27 14:40 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-27 02:08 UTCEG score recompute
  11. 2026-06-26 13:36 UTCEG score recompute
  12. 2026-06-26 00:59 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 12:25 UTCEG score recompute
  15. 2026-06-24 23:53 UTCEG score recompute
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-24 11:21 UTCEG score recompute
  18. 2026-06-23 22:48 UTCEG score recompute
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 10:16 UTCEG score recompute
  22. 2026-06-22 21:45 UTCEG score recompute
  23. 2026-06-22 09:05 UTCEG score recompute
  24. 2026-06-21 20:33 UTCEG score recompute
  25. 2026-06-21 08:00 UTCEG score recompute
  26. 2026-06-20 19:26 UTCEG score recompute
  27. 2026-06-20 06:47 UTCEG score recompute
  28. 2026-06-19 18:13 UTCEG score recompute
  29. 2026-06-19 05:40 UTCEG score recompute
  30. 2026-06-18 16:53 UTCEG score recompute
  31. 2026-06-18 04:22 UTCEG score recompute
  32. 2026-06-17 15:51 UTCEG score recompute
  33. 2026-06-17 03:17 UTCEG score recompute
  34. 2026-06-16 14:46 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54299?
CVE-2026-54299 is a high vulnerability published on June 16, 2026. Astro is a web framework. Prior to 6.4.6, Astro SSR apps with prerendered error pages (/404 or /500 using export const prerender = true) fetch those pages over HTTP at runtime when an error occurs. The URL for this fetch is derived from request.url, which in turn gets its origin from the incoming…
When was CVE-2026-54299 disclosed?
CVE-2026-54299 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-54299 actively exploited?
CVE-2026-54299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54299?
CVE-2026-54299 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54299, 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-54299

Explore →

Is Your Infrastructure Affected by CVE-2026-54299?

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

Start Free Scan →Browse All CVEs