VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

bigint: vulnerability history, versions and safety

bigint is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 16 releases, from May 2020 to Aug 2021. 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 C1 U2
i
3 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 bigint vulnerabilities

Vulert verdict on bigint 4.4.3 i

Updated on 23 Oct 2026

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

Package health score 48/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Quiet

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 4.4.3 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 3 i
  • Depended on by 53 packages i
  • Stars 28 i
  • OpenSSF scorecard 2/10 i
  • Last release 77 months ago 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 bigint, 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
4.4.3 07 May 2020 C1 U2 Apache-2.0 OR MIT No Details →
4.4.2 07 May 2020 C1 U2 Apache-2.0 OR MIT No Details →
4.4.1 20 Aug 2018 C1 U2 Apache-2.0 OR MIT No Details →
4.4.0 11 Jun 2018 C1 U2 Apache-2.0 OR MIT No Details →
4.3.0 12 Apr 2018 C1 U2 Apache-2.0 OR MIT No Details →
4.2.0 06 Sep 2017 C1 U2 Apache-2.0 OR MIT No Details →
4.1.2 18 Aug 2017 C1 U2 Apache-2.0 OR MIT No Details →
4.1.1 17 Aug 2017 C1 U2 Apache-2.0 OR MIT No Details →
4.1.0 15 Aug 2017 C1 U2 Apache-2.0 OR MIT No Details →
4.0.0 14 Aug 2017 C1 U2 Apache-2.0 OR MIT No Details →
3.0.0 04 Jul 2017 C1 U2 Apache-2.0 OR MIT No Details →
2.0.0 21 May 2017 C1 U2 Apache-2.0 OR MIT No Details →
1.0.5 16 May 2017 C1 U2 Apache-2.0 OR MIT No Details →
1.0.4 11 May 2017 C1 U2 Apache-2.0 OR MIT No Details →
1.0.1 26 Dec 2016 C1 U2 GPL-3.0 No Details →
1.0.0 22 Dec 2016 C1 U2 GPL-3.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 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 bigint

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35880: Unsoundness in bigint 9.8 critical No fix published 07 May 2020
CVE-2020-35880: bigint crate unmaintained, use uint instead 9.8 critical No fix published 07 May 2020
CVE-2020-35880: Unsoundness in bigint 9.8 critical No fix published 25 Aug 2021

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 bigint

Is bigint safe to use?

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

What is bigint's Vulert package health score?

Vulert scores bigint 48/100, which reads as risky. 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 bigint affected?

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

How many vulnerabilities does bigint have?

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

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

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