VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

tcmalloc: vulnerability history, versions and safety

tcmalloc is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 2 affected ranges, from Jan 2022 to May 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tcmalloc vulnerabilities

Vulert verdict on tcmalloc i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 11 May 2023. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 11 May 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from c33cb2d8935002f8ba942028a1f0871d075345a1 up to 200f3b2b1ce4012433495d4f7281cbbb740b7004 (exclusive) 1
from 778abcc57b634d93f2b9fe196f556673402b9a53 up to a4838d5b4ab520f4d6360865464d63993561c732 (exclusive) 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for tcmalloc

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-after-poison vulnerability in tcmalloc N/A high a4838d5b4ab520f4d6360865464d63993561c732 13 Jan 2022
Heap-buffer-overflow in tcmalloc: Heap-buffer-overflow READ 1 N/A medium a4838d5b4ab520f4d6360865464d63993561c732 13 Jan 2022
Heap-buffer-overflow in tcmalloc N/A medium 200f3b2b1ce4012433495d4f7281cbbb740b7004 11 May 2023

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 tcmalloc

Is tcmalloc safe to use?

Vulert records 3 vulnerabilities for tcmalloc in OSS-Fuzz: 0 critical, 1 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does tcmalloc have?

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

How often are new tcmalloc vulnerabilities disclosed?

0 vulnerabilities were recorded for tcmalloc in the last 12 months, and the oldest entry in this database dates to 13 Jan 2022. 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 tcmalloc 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 tcmalloc for upcoming vulnerabilities?

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