CVE-2026-115893

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-28. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-109188 (ENISA EUVD) · GHSA-mghf-wjfp-p5xm (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is a runtime for WebAssembly. Prior to 36.0.19, 48.0.7, and 49.0.4, the Cranelift compiler backend on aarch64 can compile a Wasm br_table instruction with more than approximately 256,000 targets so that it has an incorrect conditional branch target. The branch can then jump to arbitrary other code at a user-controlled offset, allowing a user-controlled Wasm module to escape the sandbox on aarch64 engines using the default Cranelift backend. This issue is fixed in versions 36.0.19, 48.0.7, and 49.0.4.

CVSS v3
9.9
EG Score
9.9CRITICALhigh confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
1.0%
EPSS %ILE
62nd
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 23, 2026

Last Modified

October 29, 2026

Advisory Details (11)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github_pr, github_release.
GitHub release Patch Available

Release v48.0.7 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v48.0.7

https://github.com/bytecodealliance/wasmtime/releases/tag/v48.0.7
GitHub release Patch Available

Release v36.0.19 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v36.0.19

https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.19
GitHub pull request

Cranelift/aarch64: fix br_tables with very large target count.

Fix merged in bytecodealliance/wasmtime PR #14826 on 2026-10-19 — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/pull/14826
GitHub pull request

Security Fixes for release 49.0.4

Fix merged in bytecodealliance/wasmtime PR #14820 on 2026-10-19 — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/pull/14820
GitHub pull request

Security Fixes for 48.0.7

Fix merged in bytecodealliance/wasmtime PR #14819 on 2026-10-19 — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/pull/14819
GitHub pull request

Security fixes for release 36.0.19

Fix merged in bytecodealliance/wasmtime PR #14818 on 2026-10-19 — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/pull/14818
GitHub commit

commit f517bd6e890c (bytecodealliance/wasmtime)

Fix landed in bytecodealliance/wasmtime commit f517bd6e890c — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/commit/f517bd6e890c7c1291ab9fe05d8cc0c9f11e56aa
GitHub commit

commit e61df1b454be (bytecodealliance/wasmtime)

Fix landed in bytecodealliance/wasmtime commit e61df1b454be — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/commit/e61df1b454be9313d61a5f8de07722a421139bbe
GitHub commit

commit 994549891c8a (bytecodealliance/wasmtime)

Fix landed in bytecodealliance/wasmtime commit 994549891c8a — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/commit/994549891c8a706cb4f2809f9d17b9f67b31e618
GitHub commit

commit 222ff3a65dab (bytecodealliance/wasmtime)

Fix landed in bytecodealliance/wasmtime commit 222ff3a65dab — awaiting tagged release

https://github.com/bytecodealliance/wasmtime/commit/222ff3a65dab9aa7011f8c246937751a0bac5abd
GitHub advisoryMentions a patch (unverified)

Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-mghf-wjfp-p5xm

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustwasmtime @ 48.0.7 (fixes >= 37.0.0, < 48.0.7)—ghsa
rustwasmtime @ 49.0.4 (fixes >= 49.0.0, < 49.0.4)—ghsa
rustwasmtime @ 36.0.19 (fixes < 36.0.19)—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

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime—49.0.4 (one range)—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-11-01 13:48 UTCVendor advisory
  3. 2026-11-01 13:48 UTCGHSA enrichmentGHSA-mghf-wjfp-p5xm · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-01 07:59 UTCEG score recompute
  5. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-mghf-wjfp-p5xm · GitHub severity CRITICAL · GitHub CVSS 9.9
  6. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-31 15:41 UTCVendor advisory
  8. 2026-10-30 17:35 UTCEG score recompute
  9. 2026-10-30 17:35 UTCVendor advisory
  10. 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-10-29 19:26 UTCEG score recompute
  12. 2026-10-29 19:26 UTCVendor advisory
  13. 2026-10-29 18:27 UTCEG score recompute
  14. 2026-10-29 18:27 UTCVendor advisory
  15. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-10-29 12:11 UTCEG score recompute
  17. 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-10-28 13:58 UTCEG score recompute
  19. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-26 17:18 UTCEG score recompute
  21. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-25 18:50 UTCEG score recompute
  23. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-25 14:50 UTCEG score recompute
  25. 2026-10-24 20:34 UTCEG score recompute
Show 4 more
  1. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-23 22:28 UTCEG score recompute
  3. 2026-10-23 21:35 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  4. 2026-10-23 21:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-115893?
CVE-2026-115893 is a critical-severity vulnerability; its CVE record was published on October 23, 2026. Wasmtime is a runtime for WebAssembly. Prior to 36.0.19, 48.0.7, and 49.0.4, the Cranelift compiler backend on aarch64 can compile a Wasm br_table instruction with more than approximately 256,000 targets so that it has an incorrect conditional branch target. The branch can then jump to arbitrary…
When was the CVE record for CVE-2026-115893 published?
The CVE record for CVE-2026-115893 was published on October 23, 2026. 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 October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-115893 actively exploited?
CVE-2026-115893 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115893?
CVE-2026-115893 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-115893?
A fix for CVE-2026-115893 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115893 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-2026-115893

Explore →

Is Your Infrastructure Affected by CVE-2026-115893?

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