CVE-2024-56159

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 1.5% (73rd percentile of EPSS-scored CVEs). 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Astro is a web framework for content-driven websites. A bug in the build process allows any unauthenticated user to read parts of the server source code. During build, along with client assets such as css and font files, the sourcemap files for the server code are moved to a publicly-accessible folder. Any outside party can read them with an unauthorized HTTP GET request to the same server hosting the rest of the website. While some server files are hashed, making their access obscure, the files corresponding to the file system router (those in src/pages) are predictably named. For example. the sourcemap file for src/pages/index.astro gets named dist/client/pages/index.astro.mjs.map. This vulnerability is the root cause of issue #12703, which links to a simple stackblitz project demonstrating the vulnerability. Upon build, notice the contents of the dist/client (referred to as config.build.client in astro code) folder. All astro servers make the folder in question accessible to the public internet without any authentication. It contains .map files corresponding to the code that runs on the server. All server-output projects on Astro 5 versions v5.0.3 through v5.0.7, that have sourcemaps enabled, either directly or through an add-on such as sentry, are affected. The fix for server-output projects was released in [email protected]. Additionally, all static-output projects built using Astro 4 versions 4.16.17 or older, or Astro 5 versions 5.0.8 or older, that have sourcemaps enabled are also affected. The fix for static-output projects was released in [email protected], and backported to Astro v4 in [email protected]. The immediate impact is limited to source code. Any secrets or environment variables are not exposed unless they are present verbatim in the source code. There is no immediate loss of integrity within the the vulnerable server. However, it is possible to subsequently discover another vulnerability via the revealed source code . There is no immediate impact to availability of the vulnerable server. However, the presence of an unsafe regular expression, for example, can quickly be exploited to subsequently compromise the availability. The fix for server-output projects was released in [email protected], and the fix for static-output projects was released in [email protected] and backported to Astro v4 in [email protected]. Users are advised to update immediately if they are using sourcemaps or an integration that enables sourcemaps.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100CISA SSVC

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
74th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 19, 2024

Last Modified

November 25, 2025

References (5)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
astro—
  • 5.0.0-alpha.0 up to 5.0.8: fixed in 5.0.8
  • every version up to 4.16.18: fixed in 4.16.18
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 27× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:08 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:16 UTCEPSS rescore
  5. 2026-10-05 17:41 UTCEPSS rescore
  6. 2026-10-03 14:24 UTCEPSS rescore
  7. 2026-10-02 16:24 UTCEG score recompute
  8. 2026-10-01 19:48 UTCEPSS rescore
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-28 13:50 UTCEPSS rescore
  12. 2026-09-27 13:44 UTCEPSS rescore
  13. 2026-09-27 13:44 UTCEPSS rescore
  14. 2026-09-26 15:57 UTCEPSS rescore
  15. 2026-09-24 14:01 UTCEPSS rescore
  16. 2026-09-23 13:46 UTCEPSS rescore
  17. 2026-09-22 14:47 UTCEPSS rescore
  18. 2026-09-20 15:14 UTCOSV refresh
  19. 2026-09-18 19:26 UTCEPSS rescore
  20. 2026-09-16 14:06 UTCEPSS rescore
  21. 2026-09-16 14:06 UTCEPSS rescore
  22. 2026-09-16 05:12 UTCEPSS rescore
  23. 2026-09-15 03:08 UTCEPSS rescore
  24. 2026-09-12 14:59 UTCEPSS rescore
  25. 2026-09-11 14:51 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:35 UTCEPSS rescore
  2. 2026-09-10 09:33 UTCEPSS rescore
  3. 2026-09-08 21:59 UTCEPSS rescore
  4. 2026-09-07 16:00 UTCEPSS rescore
  5. 2026-09-06 13:46 UTCEPSS rescore
  6. 2026-09-04 13:59 UTCEPSS rescore
  7. 2026-09-04 05:05 UTCEPSS rescore
  8. 2026-09-02 14:10 UTCEPSS rescore
  9. 2026-09-01 15:53 UTCOSV refresh
  10. 2026-09-01 13:52 UTCEPSS rescore
  11. 2026-08-30 19:16 UTCEPSS rescore
  12. 2026-08-30 19:16 UTCEPSS rescore
  13. 2026-08-30 01:21 UTCEPSS rescore
  14. 2026-08-28 21:39 UTCEPSS rescore
  15. 2026-08-27 14:24 UTCEPSS rescore
  16. 2026-08-26 14:44 UTCEPSS rescore
  17. 2026-08-25 13:47 UTCEPSS rescore
  18. 2026-08-24 14:15 UTCEPSS rescore
  19. 2026-08-23 00:18 UTCEPSS rescore
  20. 2026-08-21 23:47 UTCEPSS rescore
  21. 2026-08-20 22:54 UTCEPSS rescore
  22. 2026-08-19 17:02 UTCEPSS rescore
  23. 2026-08-18 13:47 UTCEPSS rescore
  24. 2026-08-17 13:45 UTCEPSS rescore
  25. 2026-08-16 14:55 UTCEPSS rescore
  26. 2026-08-16 02:13 UTCEPSS rescore
  27. 2026-08-15 16:37 UTCOSV refresh
  28. 2026-08-15 01:29 UTCEPSS rescore
  29. 2026-08-13 21:59 UTCEPSS rescore
  30. 2026-08-12 13:49 UTCEPSS rescore
  31. 2026-08-11 13:41 UTCEPSS rescore
  32. 2026-08-10 23:58 UTCEPSS rescore
  33. 2026-08-09 13:45 UTCEPSS rescore
  34. 2026-08-08 16:35 UTCEPSS rescore
  35. 2026-08-07 16:26 UTCEPSS rescore
  36. 2026-08-06 13:45 UTCEPSS rescore
  37. 2026-08-05 19:16 UTCEPSS rescore
  38. 2026-08-04 15:08 UTCEPSS rescore
  39. 2026-08-03 10:35 UTCEPSS rescore
  40. 2026-08-02 02:25 UTCEPSS rescore
  41. 2026-08-02 02:25 UTCEPSS rescore
  42. 2026-08-01 04:14 UTCEPSS rescore
  43. 2026-07-31 08:42 UTCOSV refresh
  44. 2026-07-30 16:26 UTCEPSS rescore
  45. 2026-07-30 16:26 UTCEPSS rescore
  46. 2026-07-30 01:29 UTCEPSS rescore
  47. 2026-07-28 15:35 UTCEPSS rescore
  48. 2026-07-26 14:53 UTCEPSS rescore
  49. 2026-07-25 14:17 UTCEPSS rescore
  50. 2026-07-25 14:17 UTCEPSS rescore
  51. 2026-07-24 14:16 UTCEPSS rescore
  52. 2026-07-23 14:17 UTCEPSS rescore
  53. 2026-07-23 14:17 UTCEPSS rescore
  54. 2026-07-23 02:44 UTCEG score recompute
  55. 2026-07-22 14:07 UTCEPSS rescore
  56. 2026-07-21 15:23 UTCEPSS rescore
  57. 2026-07-20 17:07 UTCEPSS rescore
  58. 2026-07-19 14:30 UTCEPSS rescore
  59. 2026-07-19 14:30 UTCEPSS rescore
  60. 2026-07-19 02:28 UTCEPSS rescore
  61. 2026-07-19 02:28 UTCEPSS rescore
  62. 2026-07-18 10:03 UTCEPSS rescore
  63. 2026-07-16 17:02 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-13 22:29 UTCEPSS rescore
  68. 2026-07-13 16:08 UTCOSV refresh
  69. 2026-07-13 06:12 UTCEPSS rescore
  70. 2026-07-12 05:45 UTCEPSS rescore
  71. 2026-07-11 08:26 UTCEPSS rescore
  72. 2026-07-09 19:09 UTCEPSS rescore
  73. 2026-07-09 19:09 UTCEPSS rescore
  74. 2026-07-08 15:14 UTCEPSS rescore
  75. 2026-07-07 13:45 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2024/CVE-2024-56159.yaml
    First seen Jan 1, 2024

    Astro - Information Disclosure

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-56159?
CVE-2024-56159 is a medium vulnerability published on December 19, 2024. Astro is a web framework for content-driven websites. A bug in the build process allows any unauthenticated user to read parts of the server source code. During build, along with client assets such as css and font files, the sourcemap files for the server code are moved to a publicly-accessible…
When was CVE-2024-56159 disclosed?
CVE-2024-56159 was first published on December 19, 2024, with the most recent update on November 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56159 actively exploited?
CVE-2024-56159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56159?
CVE-2024-56159 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2024-56159?
A fix for CVE-2024-56159 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-56159

Explore →

Is Your Infrastructure Affected by CVE-2024-56159?

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

Book a Demo →Browse All CVEs