Heap Buffer Overflow Vulnerability in Tarantool - OSV-2025-1020

tarantool Updated 24 Mar 2026

Summary

25/12/2025
HIGH
No i
High
Not published

OSV-2025-1020: Heap-buffer-overflow in mmcall. Affects tarantool versions >= 8c7cfb1cd0b3f5ce1d5b181403f68f7aaf657d9a. No fix is published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Tarantool is an open-source in-memory database and application server designed for high performance and scalability. It supports Lua scripting and is often used for building real-time applications. The package is known for its flexibility and speed, making it a popular choice among developers. However, it has been identified to have a critical vulnerability that could lead to severe security issues.

Vulnerability Detail

The vulnerability identified as OSV-2025-1020 is a heap buffer overflow in the 'mmcall' function of Tarantool. This issue arises from improper memory management, allowing an attacker to write beyond the allocated buffer. The crash report indicates that the overflow occurs during the execution of the 'lj_meta_tset' and 'lj_vmeta_tsetv' functions. If exploited, this vulnerability could lead to arbitrary code execution, data corruption, or application crashes, posing a significant risk to systems using this package.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can limit access to the affected functionality or disable features that utilize 'mmcall' until a patch is applied. Additionally, implementing strict input validation can help mitigate the risk of exploitation.

Conclusion

The heap buffer overflow vulnerability in Tarantool (OSV-2025-1020) poses a significant risk to applications utilizing this package. It is crucial for users to update to the latest patched version and consider implementing workarounds to mitigate potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for tarantool →

Share this vulnerability

FAQ

A heap buffer overflow occurs when a program writes more data to a buffer located on the heap than it can hold, potentially overwriting adjacent memory and leading to unpredictable behavior.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. By simply uploading your manifest file like package-lock.json, you can check if your application is affected. Visit the Vulert playground at Vulert Scanner for more information.

Exploitation of this vulnerability could lead to arbitrary code execution, data corruption, or application crashes, which can compromise the integrity and availability of your application.

Yes, a patched version of Tarantool is available. Users are encouraged to update to the latest version to mitigate the risk associated with this vulnerability.

If an immediate update is not possible, consider implementing workarounds such as limiting access to the affected functionality and enhancing input validation to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for tarantool.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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