VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

mithril-client: vulnerability history, versions and safety

mithril-client is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 mithril-client vulnerabilities

Vulert verdict on mithril-client 0.14.34 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.14.34 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 May 2025 i
  • Highest CVSS 4.9 i
  • With no published fix 0 i
  • Stars 154 i
  • Last release this month i
  • Licence Apache-2.0 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 mithril-client, 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.14.34 20 Oct 2026 none Apache-2.0 — Details →
0.14.17 03 Aug 2026 none Apache-2.0 — Details →
0.14.5 28 Apr 2026 none Apache-2.0 — Details →
0.13.2 29 Jan 2026 none Apache-2.0 — Details →
0.12.34 03 Nov 2025 none Apache-2.0 — Details →
0.12.30 17 Sep 2025 none Apache-2.0 — Details →
0.12.11 16 Jun 2025 none Apache-2.0 — Details →
0.12.2 06 May 2025 none Apache-2.0 — Details →
0.12.0 05 May 2025 M1 Apache-2.0 Yes Details →
0.11.17 28 Mar 2025 M1 Apache-2.0 Yes Details →
0.11.1 14 Feb 2025 M1 Apache-2.0 Yes Details →
0.10.4 17 Dec 2024 M1 Apache-2.0 Yes Details →
0.10.1 07 Nov 2024 M1 Apache-2.0 Yes Details →
0.9.2 21 Oct 2024 M1 Apache-2.0 Yes Details →
0.8.18 23 Sep 2024 M1 Apache-2.0 Yes Details →
0.8.10 30 Jul 2024 M1 Apache-2.0 Yes Details →
0.8.7 15 Jul 2024 M1 Apache-2.0 Yes Details →
0.8.3 12 Jun 2024 M1 Apache-2.0 Yes Details →
0.8.0 13 May 2024 M1 Apache-2.0 Yes Details →
0.6.9 26 Mar 2024 M1 Apache-2.0 Yes Details →
0.6.4 26 Feb 2024 M1 Apache-2.0 Yes Details →
0.5.17 23 Jan 2024 M1 Apache-2.0 Yes Details →
0.5.7 27 Nov 2023 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for mithril-client

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Compromise Risk in Mithril Client for Cardano Database Certification 4.9 medium 0.12.2 07 May 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 mithril-client

Is mithril-client safe to use?

Vulert records 1 vulnerabilities for mithril-client in crates.io: 0 critical, 0 high, 1 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.

What is mithril-client's Vulert package health score?

Vulert scores mithril-client 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 mithril-client affected?

No. 0.14.34, 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.

How many vulnerabilities does mithril-client have?

1 vulnerability is recorded for mithril-client in the crates.io ecosystem: 0 critical, 0 high, 1 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 mithril-client vulnerabilities disclosed?

0 vulnerabilities were recorded for mithril-client in the last 12 months, and the oldest entry in this database dates to 07 May 2025. 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 mithril-client 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 mithril-client for upcoming vulnerabilities?

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