VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

magic-crypt: vulnerability history, versions and safety

magic-crypt is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 34 releases, first recorded in Dec 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 L1 U1
i
2 with no fix published

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

See the unfixed vulnerabilities →
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 magic-crypt vulnerabilities

Vulert verdict on magic-crypt 6.0.0 i

Updated on 23 Oct 2026

Careful: 6.0.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 59/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.0.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 30 Dec 2024 i
  • Highest CVSS n/a i
  • With no published fix 2 i
  • Stars 38 i
  • OpenSSF scorecard 2/10 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 magic-crypt, 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
6.0.0 18 Oct 2026 L1 U1 Apache-2.0 No Details →
5.0.1 10 Jul 2026 L1 U1 Apache-2.0 No Details →
5.0.0 10 Jul 2026 L1 U1 Apache-2.0 No Details →
4.0.1 02 Nov 2024 L1 U1 Apache-2.0 No Details →
4.0.0 02 Nov 2024 L1 U1 Apache-2.0 No Details →
3.1.13 10 Nov 2023 L1 U1 Apache-2.0 No Details →
3.1.12 14 Oct 2022 L1 U1 Apache-2.0 No Details →
3.1.11 14 Oct 2022 L1 U1 Apache-2.0 No Details →
3.1.10 17 Mar 2022 L1 U1 Apache-2.0 No Details →
3.1.9 19 Sep 2021 L1 U1 Apache-2.0 No Details →
3.1.8 21 Apr 2021 L1 U1 Apache-2.0 No Details →
3.1.7 11 Mar 2021 L1 U1 Apache-2.0 No Details →
3.1.6 13 Nov 2020 L1 U1 Apache-2.0 No Details →
3.1.5 12 Aug 2020 L1 U1 Apache-2.0 No Details →
3.1.4 21 Jul 2020 L1 U1 Apache-2.0 No Details →
3.1.3 27 Jun 2020 L1 U1 Apache-2.0 No Details →
3.1.2 24 Jun 2020 L1 U1 Apache-2.0 No Details →
3.1.1 30 May 2020 L1 U1 Apache-2.0 No Details →
3.1.0 30 May 2020 L1 U1 Apache-2.0 No Details →
3.0.1 25 May 2020 L1 U1 Apache-2.0 No Details →
3.0.0 15 May 2020 L1 U1 Apache-2.0 No Details →
2.1.10 27 Feb 2020 L1 U1 Apache-2.0 No Details →
2.1.9 23 Feb 2020 L1 U1 Apache-2.0 No Details →
2.1.8 21 Feb 2020 L1 U1 Apache-2.0 No Details →
2.1.7 17 Sep 2019 L1 U1 Apache-2.0 No Details →
2.1.6 28 Jul 2019 L1 U1 Apache-2.0 No Details →
2.1.5 07 Jul 2019 L1 U1 Apache-2.0 No Details →
2.1.4 14 Nov 2018 L1 U1 Apache-2.0 No Details →
2.1.3 14 Nov 2018 L1 U1 Apache-2.0 No Details →
2.1.2 01 Sep 2018 L1 U1 Apache-2.0 No Details →
2.1.1 26 Aug 2018 L1 U1 Apache-2.0 No Details →
2.1.0 25 Aug 2018 L1 U1 Apache-2.0 No Details →
2.0.1 24 Aug 2018 L1 U1 Apache-2.0 No Details →
2.0.0 24 Aug 2018 L1 U1 Apache-2.0 No Details →

All 34 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 2

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 magic-crypt

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Insecure Cryptographic Algorithms in MagicCrypt Package - RUSTSEC-2024-0430 N/A unrated No fix published 28 Dec 2024
Insecure Cryptographic Algorithms in magic-crypt Package N/A low No fix published 30 Dec 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 magic-crypt

Is magic-crypt safe to use?

Vulert records 2 vulnerabilities for magic-crypt in crates.io: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is magic-crypt's Vulert package health score?

Vulert scores magic-crypt 59/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of magic-crypt affected?

Yes. 6.0.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does magic-crypt have?

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

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

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