VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

untrusted: vulnerability history, versions and safety

untrusted is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 9 releases, from Jun 2018 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 H1 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 untrusted vulnerabilities

Vulert verdict on untrusted 0.9.0 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.9.0 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 953 packages i
  • Stars 215 i
  • OpenSSF scorecard 3/10 i
  • Last release 63 months ago i
  • Licence ISC 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 untrusted, 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.9.0 13 Jul 2021 none ISC — Details →
0.8.0 04 May 2021 none ISC — Details →
0.7.1 28 Apr 2020 none ISC — Details →
0.7.0 16 Jul 2019 none ISC — Details →
0.7.0-alpha1 03 Jul 2019 none ISC — Details →
0.6.2 21 Jun 2018 none ISC — Details →
0.6.1 24 Dec 2017 H1 U2 ISC Yes Details →
0.6.0 19 Sep 2017 H1 U2 non-standard Yes Details →
0.5.1 28 Aug 2017 H1 U2 non-standard Yes Details →
0.5.0 27 Apr 2017 H1 U2 non-standard Yes Details →
0.3.2 12 Nov 2016 H1 U2 non-standard Yes Details →
0.3.1 12 Aug 2016 H1 U2 non-standard Yes Details →
0.3.0 11 Aug 2016 H1 U2 non-standard Yes Details →
0.2.0 01 Jul 2016 H1 U2 non-standard Yes Details →
0.1.0 05 Jun 2016 H1 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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 untrusted

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-20989: Integer underflow in untrusted crate 7.5 high 0.6.2 21 Jun 2018
CVE-2018-20989: Integer Underflow Leading to Panic in untrusted 7.5 high 0.6.2 21 Jun 2018
CVE-2018-20989: Integer Underflow in untrusted crate 7.5 high 0.6.2 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 untrusted

Is untrusted safe to use?

Vulert records 3 vulnerabilities for untrusted in crates.io: 0 critical, 1 high, 0 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 untrusted's Vulert package health score?

Vulert scores untrusted 61/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).

Is the latest version of untrusted affected?

No. 0.9.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 untrusted should I use?

0.9.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 untrusted have?

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

0 vulnerabilities were recorded for untrusted in the last 12 months, and the oldest entry in this database dates to 21 Jun 2018. 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 untrusted 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 untrusted for upcoming vulnerabilities?

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