CVE-2024-47763

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2024-10-09. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-3109 (ENISA EUVD) · GHSA-q8hx-mm92-4wvg (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is an open source runtime for WebAssembly. Wasmtime's implementation of WebAssembly tail calls combined with stack traces can result in a runtime crash in certain WebAssembly modules. The runtime crash may be undefined behavior if Wasmtime was compiled with Rust 1.80 or prior. The runtime crash is a deterministic process abort when Wasmtime is compiled with Rust 1.81 and later. WebAssembly tail calls are a proposal which relatively recently reached stage 4 in the standardization process. Wasmtime first enabled support for tail calls by default in Wasmtime 21.0.0, although that release contained a bug where it was only on-by-default for some configurations. In Wasmtime 22.0.0 tail calls were enabled by default for all configurations. The specific crash happens when an exported function in a WebAssembly module (or component) performs a return_call (or return_call_indirect or return_call_ref) to an imported host function which captures a stack trace (for example, the host function raises a trap). In this situation, the stack-walking code previously assumed there was always at least one WebAssembly frame on the stack but with tail calls that is no longer true. With the tail-call proposal it's possible to have an entry trampoline appear as if it directly called the exit trampoline. This situation triggers an internal assert in the stack-walking code which raises a Rust panic!(). When Wasmtime is compiled with Rust versions 1.80 and prior this means that an extern "C" function in Rust is raising a panic!(). This is technically undefined behavior and typically manifests as a process abort when the unwinder fails to unwind Cranelift-generated frames. When Wasmtime is compiled with Rust versions 1.81 and later this panic becomes a deterministic process abort. Overall the impact of this issue is that this is a denial-of-service vector where a malicious WebAssembly module or component can cause the host to crash. There is no other impact at this time other than availability of a service as the result of the crash is always a crash and no more. This issue was discovered by routine fuzzing performed by the Wasmtime project via Google's OSS-Fuzz infrastructure. We have no evidence that it has ever been exploited by an attacker in the wild. All versions of Wasmtime which have tail calls enabled by default have been patched: * 21.0.x - patched in 21.0.2 * 22.0.x - patched in 22.0.1 * 23.0.x - patched in 23.0.3 * 24.0.x - patched in 24.0.1 * 25.0.x - patched in 25.0.2. Wasmtime versions from 12.0.x (the first release with experimental tail call support) to 20.0.x (the last release with tail-calls off-by-default) have support for tail calls but the support is disabled by default. These versions are not affected in their default configurations, but users who explicitly enabled tail call support will need to either disable tail call support or upgrade to a patched version of Wasmtime. The main workaround for this issue is to disable tail support for tail calls in Wasmtime, for example with Config::wasm_tail_call(false). Users are otherwise encouraged to upgrade to patched versions.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium 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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.2%
EPSS %ILE
15th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% 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 every mission impact level.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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (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

October 9, 2024

Last Modified

September 29, 2025

References (6)

Vendor Advisories for CVE-2024-47763(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustwasmtime @ 21.0.2 (fixes >= 12.0.0, < 21.0.2)—ghsa
rustwasmtime @ 22.0.1 (fixes >= 22.0.0, < 22.0.1)—ghsa
rustwasmtime @ 23.0.3 (fixes >= 23.0.0, < 23.0.3)—ghsa
rustwasmtime @ 24.0.1 (fixes >= 24.0.0, < 24.0.1)—ghsa
rustwasmtime @ 25.0.2 (fixes >= 25.0.0, < 25.0.2)—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

(4 across 4 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime—
  • 12.0.0 up to 21.0.2: fixed in 21.0.2
  • 22.0.0 up to 22.0.1: fixed in 22.0.1
  • 23.0.0 up to 23.0.3: fixed in 23.0.3
  • 24.0.0 up to 24.0.1: fixed in 24.0.1
  • 25.0.0 up to 25.0.2: fixed in 25.0.2
  • 21.0.0 up to 21.0.2: fixed in 21.0.2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime—
  • every version up to 21.0.2+dfsg-1: fixed in 21.0.2+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime—
  • every version up to 21.0.2+dfsg-1: fixed in 21.0.2+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime-bin—
  • every version through 21.0.0: no fix on record
  • every version through 21.0.1: no fix on record
  • every version through 22.0.0: no fix on record
  • every version through 23.0.0: no fix on record
  • every version through 23.0.1: no fix on record
  • every version through 23.0.2: no fix on record
  • every version through 24.0.0: no fix on record
  • every version through 25.0.0: no fix on record
  • every version through 25.0.1: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 94 of 210 refreshes 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-q8hx-mm92-4wvg · GitHub severity MODERATE · GitHub CVSS 5.5
  3. 2026-11-01 08:11 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-10-25 17:00 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  12. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-24 04:28 UTCEG score recompute
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-10-18 06:57 UTCEG score recompute
  21. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
Show 69 more
  1. 2026-10-12 17:43 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-11 21:09 UTCEG score recompute
  4. 2026-10-11 16:01 UTCEG score recompute
  5. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-10 12:25 UTCOSV refresh
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-09-30 19:55 UTCEG score recompute
  17. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  24. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  25. 2026-09-20 21:56 UTCOSV refresh
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  27. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  29. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  31. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  32. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  34. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  38. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  44. 2026-09-01 21:27 UTCOSV refresh
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  46. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  48. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  49. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  50. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  51. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  52. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  53. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  54. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  55. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  56. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  57. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  58. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  59. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  60. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  61. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  62. 2026-08-15 23:07 UTCOSV refresh
  63. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  64. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  65. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  67. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  68. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  69. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-47763?
CVE-2024-47763 is a medium-severity vulnerability; its CVE record was published on October 9, 2024. Wasmtime is an open source runtime for WebAssembly. Wasmtime's implementation of WebAssembly tail calls combined with stack traces can result in a runtime crash in certain WebAssembly modules. The runtime crash may be undefined behavior if Wasmtime was compiled with Rust 1.80 or prior. The runtime…
When was the CVE record for CVE-2024-47763 published?
The CVE record for CVE-2024-47763 was published on October 9, 2024. 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 September 29, 2025; the record at its source may have been updated since.
Is CVE-2024-47763 actively exploited?
CVE-2024-47763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-47763?
CVE-2024-47763 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-47763?
A fix for CVE-2024-47763 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-47763 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-2024-47763

Explore →

Is Your Infrastructure Affected by CVE-2024-47763?

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

Book a Demo →Browse All CVEs