VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

tarantool: vulnerability history, versions and safety

tarantool is a package in the OSS-Fuzz ecosystem. Vulert records 13 vulnerabilities for it across 40 releases, from Feb 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded H10 M2 U1
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 05 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tarantool vulnerabilities

Vulert verdict on tarantool i

Updated on 23 Oct 2026

Careful: 4 of the 13 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 13 vulnerabilities on record across 2 years, 3 in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 13 over 2 years · 3 in the last year i
  • Latest disclosure 05 Jul 2026 i
  • Highest CVSS n/a i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for tarantool, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 40 of 40 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3
  • 2025 8
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 13 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for tarantool

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Buffer Overflow Vulnerability in Tarantool - OSV-2025-1020 N/A high No fix published 25 Dec 2025
Critical Stack Buffer Overflow Vulnerability in Tarantool N/A high 8c7cfb1cd0b3f5ce1d5b181403f68f7aaf657d9a 08 Apr 2025
Heap Buffer Overflow Vulnerability in Tarantool - OSV-2025-437 N/A high 8c7cfb1cd0b3f5ce1d5b181403f68f7aaf657d9a 05 Jun 2025
Heap Buffer Overflow Vulnerability in Tarantool - OSV-2025-593 N/A high No fix published 02 Aug 2025
Heap Buffer Overflow Vulnerability in Tarantool - OSV-2025-266 N/A medium No fix published 08 Apr 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About tarantool

Is tarantool safe to use?

Vulert records 13 vulnerabilities for tarantool in OSS-Fuzz: 0 critical, 10 high, 2 medium and 0 low, plus 1 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does tarantool have?

13 vulnerabilities are recorded for tarantool in the OSS-Fuzz ecosystem: 0 critical, 10 high, 2 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tarantool vulnerabilities disclosed?

3 vulnerabilities were recorded for tarantool in the last 12 months, and the oldest entry in this database dates to 17 Feb 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of tarantool are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor tarantool for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the tarantool version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.