VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

dashmap: vulnerability history, versions and safety

dashmap is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 1 release, from Jan 2022 to Jun 2022. 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 H1 U1
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 dashmap vulnerabilities

Vulert verdict on dashmap 6.2.1 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 6.2.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 16 Jun 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 551 packages i
  • Stars 4,123 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence 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 dashmap, 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.2.1 17 May 2026 none MIT — Details →
7.0.0-rc2 05 Mar 2025 none MIT — Details →
7.0.0-rc1 14 Feb 2025 none MIT — Details →
7.0.0-rc0 13 Feb 2025 none MIT — Details →
6.1.0 05 Sep 2024 none MIT — Details →
6.0.1 24 Jun 2024 none MIT — Details →
6.0.0 18 Jun 2024 none MIT — Details →
6.0.0-rc.1 17 Jun 2024 none MIT — Details →
5.5.3 29 Aug 2023 none MIT — Details →
5.5.2 29 Aug 2023 none MIT — Details →
5.5.1 22 Aug 2023 none MIT — Details →
5.5.0 11 Jul 2023 none MIT — Details →
5.4.0 30 Aug 2022 none MIT — Details →
5.3.4 28 May 2022 none MIT — Details →
5.3.3 02 May 2022 none MIT — Details →
5.3.2 30 Apr 2022 none MIT — Details →
5.3.1 29 Apr 2022 none MIT — Details →
5.3.0 29 Apr 2022 none MIT — Details →
5.2.0 14 Mar 2022 none MIT — Details →
5.1.0 06 Feb 2022 none MIT — Details →
5.0.0 12 Dec 2021 H1 MIT Yes Details →
4.0.2 12 Jan 2021 none MIT — Details →
4.0.1 26 Dec 2020 none MIT — Details →
4.0.0 25 Dec 2020 none MIT — Details →
3.11.10 04 Aug 2020 none MIT — Details →
3.11.9 31 Jul 2020 none MIT — Details →
3.11.8 31 Jul 2020 none MIT — Details →
3.11.7 04 Jul 2020 none MIT — Details →
3.11.6 04 Jul 2020 none MIT — Details →
3.11.5 02 Jul 2020 none MIT — Details →
4.0.0-rc6 09 Jun 2020 none MIT — Details →
3.11.4 02 Jun 2020 none MIT — Details →
3.11.3 02 Jun 2020 none MIT — Details →
4.0.0-rc5 01 Jun 2020 none MIT — Details →
3.11.2 24 May 2020 none MIT — Details →
4.0.0-rc4 24 May 2020 none MIT — Details →
4.0.0-rc3 15 May 2020 none MIT — Details →
4.0.0-rc2 09 May 2020 none MIT — Details →
4.0.0-rc1 09 May 2020 none MIT — Details →
4.0.0-rc0 09 May 2020 none MIT — Details →
3.11.1 19 Apr 2020 none MIT — Details →
3.11.0 09 Apr 2020 none MIT — Details →
3.10.0 04 Apr 2020 none MIT — Details →
3.9.1 31 Mar 2020 none MIT — Details →
3.9.0 28 Mar 2020 none MIT — Details →
3.8.1 27 Mar 2020 none MIT — Details →
3.8.0 27 Mar 2020 none MIT — Details →
3.7.0 11 Mar 2020 none MIT — Details →
3.6.0 09 Mar 2020 none MIT — Details →
3.5.1 26 Feb 2020 none MIT — Details →
3.5.0 21 Feb 2020 none MIT — Details →
3.4.4 13 Feb 2020 none MIT — Details →
3.4.3 07 Feb 2020 none MIT — Details →
3.4.2 06 Feb 2020 none MIT — Details →
3.4.1 06 Feb 2020 none MIT — Details →
3.4.0 30 Jan 2020 none MIT — Details →
3.2.2 23 Jan 2020 none MIT — Details →
3.2.1 17 Jan 2020 none MIT — Details →
3.2.0 17 Jan 2020 none MIT — Details →
3.1.2 16 Jan 2020 none MIT — Details →
3.1.1 16 Jan 2020 none MIT — Details →
3.1.0 15 Jan 2020 none MIT — Details →
3.0.7 15 Jan 2020 none MIT — Details →
3.0.6 15 Jan 2020 none MIT — Details →
3.0.5 15 Jan 2020 none MIT — Details →
3.0.4 15 Jan 2020 none MIT — Details →
3.0.3 15 Jan 2020 none MIT — Details →
3.0.2 14 Jan 2020 none MIT — Details →
3.0.1 14 Jan 2020 none MIT — Details →
3.0.0 14 Jan 2020 none MIT — Details →
2.1.1 18 Dec 2019 none MIT — Details →
2.1.0 07 Dec 2019 none MIT — Details →
2.0.3 07 Dec 2019 none MIT — Details →
2.0.2 07 Dec 2019 none MIT — Details →
2.0.1 06 Dec 2019 none MIT — Details →
2.0.0 06 Dec 2019 none MIT — Details →
1.2.1 06 Dec 2019 none MIT — Details →
1.2.0 15 Oct 2019 none MIT — Details →
1.1.0 06 Oct 2019 none MIT — Details →
1.0.5 27 Sep 2019 none MIT — Details →
1.0.4 29 Aug 2019 none MIT — Details →
1.0.3 25 Aug 2019 none MIT — Details →
1.0.2 25 Aug 2019 none MIT — Details →
1.0.1 25 Aug 2019 none MIT — Details →
1.0.0 25 Aug 2019 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 dashmap

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-0002: Unsoundness in dashmap references N/A unrated 5.1.0 10 Jan 2022
Unsoundness in dashmap references N/A high 5.1.0 16 Jun 2022

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 dashmap

Is dashmap safe to use?

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

Vulert scores dashmap 78/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 dashmap affected?

No. 6.2.1, 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 dashmap should I use?

6.2.1 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 dashmap have?

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

0 vulnerabilities were recorded for dashmap in the last 12 months, and the oldest entry in this database dates to 10 Jan 2022. 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 dashmap 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 dashmap for upcoming vulnerabilities?

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