# CVE-2025-58749: WAMR runtime hangs or crashes with large memory.fill addresses in LLVM-JIT mode

> Attackers can cause the WAMR runtime to hang or crash by providing WebAssembly programs with large memory.fill addresses in LLVM-JIT mode.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** AZL-67608, AZL-67617, GHSA-xj5p-r8jq-pw47

## What is CVE-2025-58749?

CVE-2025-58749 is a low-severity denial of service vulnerability in bytecodealliance wasm-micro-runtime, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. In WAMR versions prior to 2.4.2, when running in LLVM-JIT mode, the runtime cannot exit normally when executing WebAssembly programs containing a memory.fill instruction where the first operand (memory address pointer) is greater than or equal to 2147483648 bytes (2GiB). This causes the runtime to hang in release builds or crash in debug builds due to accessing an invalid pointer. The issue does not occur in FAST-JIT mode or other runtime tools. This has been fixed in version 2.4.2.

Weakness: CWE-822 (Untrusted Pointer Dereference), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-58749?

It affects 1 product.


Products: Bytecodealliance Webassembly Micro Runtime.

## How do I fix CVE-2025-58749?

Upgrade to a fixed version.

## Is CVE-2025-58749 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58749 exists.

## Other vulnerabilities in bytecodealliance wasm-micro-runtime

- [CVE-2024-25431](https://insights.sbomify.com/CVE-2024-25431/): Memory corruption in n/a (high 8.8)
- [CVE-2024-27532](https://insights.sbomify.com/CVE-2024-27532/): Null dereference in n/a (high 7.5)
- [CVE-2024-34251](https://insights.sbomify.com/CVE-2024-34251/): Memory corruption in n/a (high 7.5)
- [CVE-2023-48105](https://insights.sbomify.com/CVE-2023-48105/): Memory corruption in n/a (high 7.5)
- [CVE-2025-43853](https://insights.sbomify.com/CVE-2025-43853/): iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58749 and fix it if it is affected.

What it is: CVE-2025-58749 is a low-severity denial of service vulnerability in bytecodealliance wasm-micro-runtime, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58749 exists.

Affected product: bytecodealliance wasm-micro-runtime. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58749/ (Markdown: https://insights.sbomify.com/CVE-2025-58749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58749
- OSV: https://osv.dev/vulnerability/CVE-2025-58749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58749/
Summaries are generated and may contain mistakes; the official description above is the record.