VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

tor-circmgr: vulnerability history, versions and safety

tor-circmgr is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 1 release, first recorded in May 2024. 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 M1 U2
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 tor-circmgr vulnerabilities

Vulert verdict on tor-circmgr 0.47.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 0.47.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 18 May 2024 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Last release this month i
  • Licence Apache-2.0 OR 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 tor-circmgr, 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.47.0 01 Oct 2026 none Apache-2.0 OR MIT — Details →
0.46.0 02 Sep 2026 none Apache-2.0 OR MIT — Details →
0.45.0 03 Aug 2026 none Apache-2.0 OR MIT — Details →
0.44.0 30 Jun 2026 none Apache-2.0 OR MIT — Details →
0.43.0 01 Jun 2026 none Apache-2.0 OR MIT — Details →
0.42.0 07 May 2026 none Apache-2.0 OR MIT — Details →
0.41.0 30 Mar 2026 none Apache-2.0 OR MIT — Details →
0.40.0 03 Mar 2026 none Apache-2.0 OR MIT — Details →
0.39.0 02 Feb 2026 none Apache-2.0 OR MIT — Details →
0.38.0 13 Jan 2026 none Apache-2.0 OR MIT — Details →
0.37.0 02 Dec 2025 none Apache-2.0 OR MIT — Details →
0.36.0 30 Oct 2025 none Apache-2.0 OR MIT — Details →
0.35.0 06 Oct 2025 none Apache-2.0 OR MIT — Details →
0.34.0 28 Aug 2025 none Apache-2.0 OR MIT — Details →
0.33.0 05 Aug 2025 none Apache-2.0 OR MIT — Details →
0.32.0 08 Jul 2025 none Apache-2.0 OR MIT — Details →
0.31.0 05 Jun 2025 none Apache-2.0 OR MIT — Details →
0.30.0 01 May 2025 none Apache-2.0 OR MIT — Details →
0.29.0 01 Apr 2025 none Apache-2.0 OR MIT — Details →
0.28.0 03 Mar 2025 none Apache-2.0 OR MIT — Details →
0.27.0 07 Feb 2025 none Apache-2.0 OR MIT — Details →
0.26.0 07 Jan 2025 none Apache-2.0 OR MIT — Details →
0.25.0 02 Dec 2024 none Apache-2.0 OR MIT — Details →
0.24.0 31 Oct 2024 none Apache-2.0 OR MIT — Details →
0.23.0 30 Sep 2024 none Apache-2.0 OR MIT — Details →
0.22.0 03 Sep 2024 none Apache-2.0 OR MIT — Details →
0.21.0 01 Aug 2024 none Apache-2.0 OR MIT — Details →
0.20.0 27 Jun 2024 none Apache-2.0 OR MIT — Details →
0.19.0 05 Jun 2024 none Apache-2.0 OR MIT — Details →
0.18.1 15 May 2024 none Apache-2.0 OR MIT — Details →
0.18.0 30 Apr 2024 M1 Apache-2.0 OR MIT Yes Details →
0.17.0 02 Apr 2024 none Apache-2.0 OR MIT — Details →
0.16.0 04 Mar 2024 none Apache-2.0 OR MIT — Details →
0.15.0 05 Feb 2024 none Apache-2.0 OR MIT — Details →
0.14.0 09 Jan 2024 none Apache-2.0 OR MIT — Details →
0.13.0 04 Dec 2023 none Apache-2.0 OR MIT — Details →
0.12.0 31 Oct 2023 none Apache-2.0 OR MIT — Details →
0.11.0 02 Oct 2023 none Apache-2.0 OR MIT — Details →
0.10.1 05 Sep 2023 none Apache-2.0 OR MIT — Details →
0.10.0 01 Aug 2023 none Apache-2.0 OR MIT — Details →
0.9.1 30 Jun 2023 none Apache-2.0 OR MIT — Details →
0.9.0 01 Jun 2023 none Apache-2.0 OR MIT — Details →
0.8.0 03 May 2023 none Apache-2.0 OR MIT — Details →
0.7.3 31 Mar 2023 none Apache-2.0 OR MIT — Details →
0.7.2 28 Feb 2023 none Apache-2.0 OR MIT — Details →
0.7.1 01 Feb 2023 none Apache-2.0 OR MIT — Details →
0.7.0 30 Nov 2022 none Apache-2.0 OR MIT — Details →
0.6.0 03 Oct 2022 none Apache-2.0 OR MIT — Details →
0.5.0 01 Sep 2022 none Apache-2.0 OR MIT — Details →
0.4.0 01 Aug 2022 none Apache-2.0 OR MIT — Details →
0.3.2 24 Jun 2022 none Apache-2.0 OR MIT — Details →
0.3.1 27 May 2022 none Apache-2.0 OR MIT — Details →
0.3.0 06 May 2022 none Apache-2.0 OR MIT — Details →
0.2.0 01 Apr 2022 none Apache-2.0 OR MIT — Details →
0.1.0 01 Mar 2022 none Apache-2.0 OR MIT — Details →
0.0.4 31 Jan 2022 none Apache-2.0 OR MIT — Details →
0.0.3 11 Jan 2022 none Apache-2.0 OR MIT — Details →
0.0.2 30 Nov 2021 none Apache-2.0 OR MIT — Details →
0.0.1 29 Oct 2021 none Apache-2.0 OR MIT — Details →
0.0.0 24 Jun 2021 none Apache-2.0 OR MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3

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 tor-circmgr

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-35313: Tor path lengths too short when "full Vanguards" configured 5.9 medium 0.18.1 18 May 2024
CVE-2024-35313: Vulnerability in tor-circmgr - Tor path lengths too short when "Vanguards lite" configured N/A unrated 0.18.1 15 May 2024
CVE-2024-35313: Vulnerability in tor-circmgr - Tor path lengths too short when "full Vanguards" configured N/A unrated 0.18.1 15 May 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 tor-circmgr

Is tor-circmgr safe to use?

Vulert records 3 vulnerabilities for tor-circmgr in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 2 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 tor-circmgr's Vulert package health score?

Vulert scores tor-circmgr 79/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 tor-circmgr affected?

No. 0.47.0, 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 tor-circmgr should I use?

0.47.0 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 tor-circmgr have?

3 vulnerabilities are recorded for tor-circmgr in the crates.io ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 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 tor-circmgr vulnerabilities disclosed?

0 vulnerabilities were recorded for tor-circmgr in the last 12 months, and the oldest entry in this database dates to 15 May 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 tor-circmgr 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 tor-circmgr for upcoming vulnerabilities?

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