Vulnerability Database · crates.io · Package report

arrow: vulnerability history, versions and safety

arrow is a package in the crates.io ecosystem. Vulert records 6 vulnerabilities for it across 30 releases, from Sep 2021 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
6 vulnerabilities recorded H3 U3
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.

Vulert verdict on arrow 60.0.0 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 60.0.0 — unaffected i
  • Vulnerabilities on record 6 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
  • Stars 3,641 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago 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 arrow, 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
59.3.1 15 Oct 2026 none Apache-2.0 — Details →
60.0.0 15 Sep 2026 none Apache-2.0 — Details →
59.3.0 01 Sep 2026 none Apache-2.0 — Details →
59.2.0 06 Aug 2026 none Apache-2.0 — Details →
58.4.0 22 Jul 2026 none Apache-2.0 — Details →
59.1.0 07 Jul 2026 none Apache-2.0 — Details →
59.0.0 09 Jun 2026 none Apache-2.0 — Details →
56.2.1 11 May 2026 none Apache-2.0 — Details →
58.3.0 11 May 2026 none Apache-2.0 — Details →
57.3.1 11 May 2026 none Apache-2.0 — Details →
58.2.0 02 May 2026 none Apache-2.0 — Details →
58.1.0 24 Mar 2026 none Apache-2.0 — Details →
58.0.0 23 Feb 2026 none Apache-2.0 — Details →
57.3.0 06 Feb 2026 none Apache-2.0 — Details →
57.2.0 11 Jan 2026 none Apache-2.0 — Details →
57.1.0 24 Nov 2025 none Apache-2.0 — Details →
57.0.0 23 Oct 2025 none Apache-2.0 — Details →
56.2.0 23 Sep 2025 none Apache-2.0 — Details →
56.1.0 25 Aug 2025 none Apache-2.0 — Details →
56.0.0 01 Aug 2025 none Apache-2.0 — Details →
55.2.0 26 Jun 2025 none Apache-2.0 — Details →
55.1.0 13 May 2025 none Apache-2.0 — Details →
55.0.0 11 Apr 2025 none Apache-2.0 — Details →
54.3.1 30 Mar 2025 none Apache-2.0 — Details →
54.3.0 21 Mar 2025 none Apache-2.0 — Details →
53.4.1 07 Mar 2025 none Apache-2.0 — Details →
54.2.1 27 Feb 2025 none Apache-2.0 — Details →
54.2.0 16 Feb 2025 none Apache-2.0 — Details →
54.1.0 02 Feb 2025 none Apache-2.0 — Details →
53.4.0 18 Jan 2025 none Apache-2.0 — Details →
54.0.0 23 Dec 2024 none Apache-2.0 — Details →
53.3.0 20 Nov 2024 none Apache-2.0 — Details →
53.2.0 24 Oct 2024 none Apache-2.0 — Details →
53.1.0 06 Oct 2024 none Apache-2.0 — Details →
53.0.0 03 Sep 2024 none Apache-2.0 — Details →
52.2.0 28 Jul 2024 none Apache-2.0 — Details →
52.1.0 06 Jul 2024 none Apache-2.0 — Details →
52.0.0 06 Jun 2024 none Apache-2.0 — Details →
51.0.0 18 Mar 2024 none Apache-2.0 — Details →
50.0.0 12 Jan 2024 none Apache-2.0 — Details →
49.0.0 13 Nov 2023 none Apache-2.0 — Details →
48.0.1 13 Nov 2023 none Apache-2.0 — Details →
48.0.0 23 Oct 2023 none Apache-2.0 — Details →
47.0.0 22 Sep 2023 none Apache-2.0 — Details →
46.0.0 24 Aug 2023 none Apache-2.0 — Details →
45.0.0 02 Aug 2023 none Apache-2.0 — Details →
44.0.0 18 Jul 2023 none Apache-2.0 — Details →
43.0.0 03 Jul 2023 none Apache-2.0 — Details →
42.0.0 20 Jun 2023 none Apache-2.0 — Details →
41.0.0 06 Jun 2023 none Apache-2.0 — Details →
40.0.0 22 May 2023 none Apache-2.0 — Details →
39.0.0 09 May 2023 none Apache-2.0 — Details →
38.0.0 25 Apr 2023 none Apache-2.0 — Details →
37.0.0 10 Apr 2023 none Apache-2.0 — Details →
36.0.0 28 Mar 2023 none Apache-2.0 — Details →
35.0.0 13 Mar 2023 none Apache-2.0 — Details →
34.0.0 27 Feb 2023 none Apache-2.0 — Details →
33.0.0 13 Feb 2023 none Apache-2.0 — Details →
32.0.0 30 Jan 2023 none Apache-2.0 — Details →
31.0.0 16 Jan 2023 none Apache-2.0 — Details →
30.0.1 08 Jan 2023 none Apache-2.0 — Details →
30.0.0 03 Jan 2023 none Apache-2.0 — Details →
29.0.0 12 Dec 2022 none Apache-2.0 — Details →
28.0.0 28 Nov 2022 none Apache-2.0 — Details →
27.0.0 14 Nov 2022 none Apache-2.0 — Details →
26.0.0 03 Nov 2022 none Apache-2.0 — Details →
25.0.0 17 Oct 2022 none Apache-2.0 — Details →
24.0.0 03 Oct 2022 none Apache-2.0 — Details →
23.0.0 19 Sep 2022 none Apache-2.0 — Details →
22.0.0 05 Sep 2022 none Apache-2.0 — Details →
21.0.0 29 Aug 2022 none Apache-2.0 — Details →
20.0.0 08 Aug 2022 none Apache-2.0 — Details →
19.0.0 26 Jul 2022 none Apache-2.0 — Details →
18.0.0 11 Jul 2022 none Apache-2.0 — Details →
17.0.0 27 Jun 2022 none Apache-2.0 — Details →
16.0.0 13 Jun 2022 none Apache-2.0 — Details →
15.0.0 30 May 2022 none Apache-2.0 — Details →
14.0.0 16 May 2022 none Apache-2.0 — Details →
0.18.0 12 May 2022 H3 U3 Apache-2.0 Yes Details →
14.0.0-dev 12 May 2022 none Apache-2.0 — Details →
13.0.0 03 May 2022 none Apache-2.0 — Details →
12.0.0 19 Apr 2022 none Apache-2.0 — Details →
11.1.0 04 Apr 2022 none Apache-2.0 — Details →
11.0.0 21 Mar 2022 none Apache-2.0 — Details →
10.0.0 08 Mar 2022 none Apache-2.0 — Details →
9.1.0 22 Feb 2022 none Apache-2.0 — Details →
9.0.2 13 Feb 2022 none Apache-2.0 — Details →
8.0.0 25 Jan 2022 none Apache-2.0 — Details →
7.0.0 12 Jan 2022 none Apache-2.0 — Details →
6.5.0 29 Dec 2021 none Apache-2.0 — Details →
6.4.0 14 Dec 2021 none Apache-2.0 — Details →
6.3.0 29 Nov 2021 H3 U3 Apache-2.0 Yes Details →
6.2.0 15 Nov 2021 H3 U3 Apache-2.0 Yes Details →
6.1.0 03 Nov 2021 H3 U3 Apache-2.0 Yes Details →
6.0.0 17 Oct 2021 H3 U3 Apache-2.0 Yes Details →
5.5.0 28 Sep 2021 H3 U3 Apache-2.0 Yes Details →
5.4.0 15 Sep 2021 H3 U3 Apache-2.0 Yes Details →
5.3.0 31 Aug 2021 H3 U3 Apache-2.0 Yes Details →
5.2.0 16 Aug 2021 H3 U3 Apache-2.0 Yes Details →
5.1.0 02 Aug 2021 H3 U3 Apache-2.0 Yes Details →
5.0.0 17 Jul 2021 H3 U3 — Yes Details →
4.4.0 28 Jun 2021 H3 U3 — Yes Details →
4.3.0 14 Jun 2021 H3 U3 — Yes Details →
4.2.0 01 Jun 2021 H3 U3 — Yes Details →
4.1.0 22 May 2021 H3 U3 — Yes Details →
4.0.0 26 Apr 2021 H3 U3 — Yes Details →
3.0.0 26 Jan 2021 H3 U3 — Yes Details →
2.0.0 19 Oct 2020 H3 U3 — Yes Details →
1.0.1 21 Aug 2020 H3 U3 — Yes Details →
1.0.0 24 Jul 2020 H3 U3 — Yes Details →
0.17.0 21 Apr 2020 H3 U3 — Yes Details →
0.16.0 07 Feb 2020 H3 U3 — Yes Details →
0.15.1 01 Nov 2019 H3 U3 — Yes Details →
0.15.0 06 Oct 2019 H3 U3 — Yes Details →
0.14.1 22 Jul 2019 H3 U3 — Yes Details →
0.14.0 08 Jul 2019 H3 U3 — Yes Details →
0.13.0 01 Apr 2019 H3 U3 — Yes Details →
0.12.0 19 Jan 2019 H3 U3 — Yes Details →
0.11.0 23 Oct 2018 H3 U3 — Yes Details →
0.10.0 07 Aug 2018 H3 U3 — Yes Details →

The newest 120 of 121 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2022 3

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

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 arrow

Is arrow safe to use?

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

Vulert scores arrow 80/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 arrow affected?

No. 60.0.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 arrow should I use?

60.0.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 arrow have?

6 vulnerabilities are recorded for arrow in the crates.io ecosystem: 0 critical, 3 high, 0 medium and 0 low, plus 3 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 arrow vulnerabilities disclosed?

0 vulnerabilities were recorded for arrow in the last 12 months, and the oldest entry in this database dates to 14 Sep 2021. 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 arrow 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 arrow for upcoming vulnerabilities?

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