VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

tracing: vulnerability history, versions and safety

tracing is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from Oct 2023 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
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 tracing vulnerabilities

Vulert verdict on tracing 0.1.44 i

Updated on 23 Oct 2026

Good news: 0.1.44, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 0.1.44 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.1.44 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.1.44 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jan 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 9,231 packages i
  • Stars 6,936 i
  • OpenSSF scorecard 4/10 i
  • Last release 10 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for tracing, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.1.44 18 Dec 2025 none MIT — Details →
0.1.43 28 Nov 2025 none MIT — Details →
0.1.42 26 Nov 2025 none MIT — Details →
0.1.41 27 Nov 2024 none MIT — Details →
0.1.40 19 Oct 2023 none MIT — Details →
0.1.39 13 Oct 2023 M1 U1 MIT Yes Details →
0.1.38 25 Apr 2023 M1 MIT Yes Details →
0.1.37 06 Oct 2022 none MIT — Details →
0.1.36 29 Jul 2022 none MIT — Details →
0.1.35 08 Jun 2022 none MIT — Details →
0.1.34 14 Apr 2022 none MIT — Details →
0.1.33 09 Apr 2022 none MIT — Details →
0.1.32 09 Mar 2022 none MIT — Details →
0.1.31 17 Feb 2022 none MIT — Details →
0.1.30 04 Feb 2022 none MIT — Details →
0.1.29 06 Oct 2021 none MIT — Details →
0.1.28 17 Sep 2021 none MIT — Details →
0.1.27 13 Sep 2021 none MIT — Details →
0.1.26 30 Apr 2021 none MIT — Details →
0.1.25 23 Feb 2021 none MIT — Details →
0.1.24 17 Feb 2021 none MIT — Details →
0.1.23 04 Feb 2021 none MIT — Details →
0.1.22 23 Nov 2020 none MIT — Details →
0.1.21 28 Sep 2020 none MIT — Details →
0.1.20 24 Aug 2020 none MIT — Details →
0.1.19 11 Aug 2020 none MIT — Details →
0.1.18 31 Jul 2020 none MIT — Details →
0.1.17 22 Jul 2020 none MIT — Details →
0.1.16 08 Jul 2020 none MIT — Details →
0.1.15 03 Jun 2020 none MIT — Details →
0.1.14 14 May 2020 none MIT — Details →
0.1.13 27 Feb 2020 none MIT — Details →
0.1.12 15 Jan 2020 none MIT — Details →
0.1.11 20 Dec 2019 none MIT — Details →
0.1.10 23 Oct 2019 none MIT — Details →
0.1.9 13 Sep 2019 none MIT — Details →
0.1.8 04 Sep 2019 none MIT — Details →
0.1.7 30 Aug 2019 none MIT — Details →
0.1.6 20 Aug 2019 none MIT — Details →
0.1.5 10 Aug 2019 none MIT — Details →
0.1.4 09 Aug 2019 none MIT — Details →
0.1.3 11 Jul 2019 none MIT — Details →
0.1.2 06 Jul 2019 none MIT — Details →
0.1.1 03 Jul 2019 none MIT — Details →
0.1.0 28 Jun 2019 none MIT — Details →
0.0.0 27 Nov 2017 none MIT — Details →

All 46 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for tracing

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Potential stack use-after-free in `Instrumented::into_inner` in tracing N/A unrated 0.1.40 19 Oct 2023
Use-after-free vulnerability in tracing crate N/A medium 0.1.40 17 Jan 2024

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 tracing

Is tracing safe to use?

Vulert records 2 vulnerabilities for tracing in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is tracing's Vulert package health score?

Vulert scores tracing 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of tracing affected?

No. 0.1.44, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of tracing should I use?

0.1.44 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does tracing have?

2 vulnerabilities are recorded for tracing in the crates.io ecosystem: 0 critical, 0 high, 1 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 tracing vulnerabilities disclosed?

0 vulnerabilities were recorded for tracing in the last 12 months, and the oldest entry in this database dates to 19 Oct 2023. 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 tracing 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 tracing for upcoming vulnerabilities?

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