Heap-use-after-free in .tmpoLlNv4 in wasmtime

wasmtime Updated 02 Oct 2025

Summary

19/07/2022
HIGH
Yes i
High
Not published

OSV-2022-590: Heap-use-after-free in .tmpoLlNv4. Affects wasmtime versions >= 80976b6fc7558ddd0ef71894c5e4a89346e260e6, < 2154c63de94e0372bca5a596c3eaf90147c922d1. Fixed in 2154c63de94e0372bca5a596c3eaf90147c922d1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

wasmtime is an open-source runtime for WebAssembly and WASI (WebAssembly System Interface) that allows executing WebAssembly modules outside of a web browser. It provides a safe and efficient environment for running WebAssembly code. However, a vulnerability has been discovered in the .tmpoLlNv4 function of wasmtime, which can lead to a heap-use-after-free issue.

Vulnerability Detail

The vulnerability in .tmpoLlNv4 function of wasmtime is a heap-use-after-free issue. This occurs when a program attempts to access memory that has already been freed. An attacker can exploit this vulnerability by crafting a malicious WebAssembly module that triggers the use of freed memory, potentially leading to arbitrary code execution or a crash. The vulnerability has been assigned a severity rating of HIGH.

How To Fix

Minimum fixed version

2154c63de94e0372bca5a596c3eaf90147c922d1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there is no known workaround for this vulnerability. It is recommended to apply the fix mentioned above by updating to the latest version of wasmtime.

Conclusion

In conclusion, a heap-use-after-free vulnerability has been discovered in the .tmpoLlNv4 function of wasmtime. This vulnerability can be exploited by an attacker to execute arbitrary code or cause a crash. It is crucial to update to the latest version of wasmtime that includes the fix to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for wasmtime →

Share this vulnerability

FAQ

wasmtime is an open-source runtime for WebAssembly and WASI (WebAssembly System Interface) that allows executing WebAssembly modules outside of a web browser.

A heap-use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to crashes or potentially allow an attacker to execute arbitrary code.

An attacker can exploit this vulnerability by crafting a malicious WebAssembly module that triggers the use of freed memory in the .tmpoLlNv4 function of wasmtime.

This vulnerability has been assigned a severity rating of HIGH.

Currently, there is no known workaround for this vulnerability. It is recommended to update to the latest version of wasmtime that includes the fix.

Related vulnerabilities

Recent vulnerabilities recorded for wasmtime.

How To Fix

Minimum fixed version

2154c63de94e0372bca5a596c3eaf90147c922d1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback