VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

anyhow: vulnerability history, versions and safety

anyhow is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 103 releases, first recorded in Jun 2026. 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 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 25 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all anyhow vulnerabilities

Vulert verdict on anyhow 1.0.104 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 1.0.104 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 13,990 packages i
  • Stars 6,684 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 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 anyhow, 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
1.0.104 18 Jul 2026 none Apache-2.0 OR MIT — Details →
1.0.103 25 Jun 2026 none Apache-2.0 OR MIT — Details →
1.0.102 20 Feb 2026 U1 Apache-2.0 OR MIT Yes Details →
1.0.101 05 Feb 2026 U1 Apache-2.0 OR MIT Yes Details →
1.0.100 19 Sep 2025 U1 Apache-2.0 OR MIT Yes Details →
1.0.99 11 Aug 2025 U1 Apache-2.0 OR MIT Yes Details →
1.0.98 14 Apr 2025 U1 Apache-2.0 OR MIT Yes Details →
1.0.97 03 Mar 2025 U1 Apache-2.0 OR MIT Yes Details →
1.0.96 20 Feb 2025 U1 Apache-2.0 OR MIT Yes Details →
1.0.95 22 Dec 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.94 03 Dec 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.93 06 Nov 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.92 01 Nov 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.91 22 Oct 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.90 18 Oct 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.89 15 Sep 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.88 11 Sep 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.87 06 Sep 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.86 18 May 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.85 17 May 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.84 17 May 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.83 06 May 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.82 10 Apr 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.81 12 Mar 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.80 19 Feb 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.79 02 Jan 2024 U1 Apache-2.0 OR MIT Yes Details →
1.0.78 30 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.77 26 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.76 21 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.75 17 Aug 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.74 15 Aug 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.73 15 Aug 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.72 15 Jul 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.71 29 Apr 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.70 18 Mar 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.69 05 Feb 2023 U1 Apache-2.0 OR MIT Yes Details →
1.0.68 18 Dec 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.67 17 Dec 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.66 20 Oct 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.65 13 Sep 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.64 04 Sep 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.63 31 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.62 16 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.61 10 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.60 03 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.59 01 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.58 18 Jun 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.57 21 Apr 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.56 07 Mar 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.55 21 Feb 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.54 19 Feb 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.53 22 Jan 2022 U1 Apache-2.0 OR MIT Yes Details →
1.0.52 23 Dec 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.51 29 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.50 28 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.49 27 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.48 22 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.47 19 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.46 08 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.45 02 Nov 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.44 12 Sep 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.43 14 Aug 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.42 09 Jul 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.41 10 Jun 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.40 26 Mar 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.39 20 Mar 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.38 11 Jan 2021 U1 Apache-2.0 OR MIT Yes Details →
1.0.37 28 Dec 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.36 18 Dec 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.35 06 Dec 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.34 02 Nov 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.33 06 Oct 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.32 24 Jul 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.31 15 May 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.30 13 May 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.29 13 May 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.28 30 Mar 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.27 14 Mar 2020 U1 Apache-2.0 OR MIT Yes Details →
1.0.26 24 Dec 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.25 28 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.24 27 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.23 23 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.22 18 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.21 17 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.20 16 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.19 02 Nov 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.18 28 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.17 21 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.16 19 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.15 19 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.14 18 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.13 13 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.12 12 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.11 10 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.10 09 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.9 09 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.8 09 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.7 09 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.6 08 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.5 08 Oct 2019 U1 Apache-2.0 OR MIT Yes Details →
1.0.4 08 Oct 2019 U1 — Yes Details →
1.0.3 08 Oct 2019 U1 — Yes Details →
1.0.2 08 Oct 2019 U1 — Yes Details →
1.0.1 07 Oct 2019 U1 — Yes Details →
1.0.0 07 Oct 2019 U1 — Yes Details →
0.0.0 05 Oct 2019 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for anyhow

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unsoundness in Error Handling: Vulnerability in anyhow Package N/A unrated 1.0.103 25 Jun 2026

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 anyhow

Is anyhow safe to use?

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

Vulert scores anyhow 84/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 anyhow affected?

No. 1.0.104, 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 anyhow should I use?

1.0.104 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 anyhow have?

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

1 vulnerability was recorded for anyhow in the last 12 months, and the oldest entry in this database dates to 25 Jun 2026. 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 anyhow 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 anyhow for upcoming vulnerabilities?

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