VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

apache-avro: vulnerability history, versions and safety

apache-avro is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 1 release, first recorded in Aug 2022. 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 H3
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 apache-avro vulnerabilities

Vulert verdict on apache-avro 0.22.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 0.22.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 10 Aug 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 131 i
  • Last release 2 months 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 apache-avro, 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.22.0 10 Aug 2026 none Apache-2.0 — Details →
0.21.0 13 Nov 2025 none Apache-2.0 — Details →
0.20.0 25 Aug 2025 none Apache-2.0 — Details →
0.19.0 27 Jun 2025 none Apache-2.0 — Details →
0.18.0 14 Apr 2025 none Apache-2.0 — Details →
0.17.0 05 Aug 2024 none Apache-2.0 — Details →
0.16.0 26 Sep 2023 none Apache-2.0 — Details →
0.15.0 10 Jul 2023 none Apache-2.0 — Details →
0.14.0 03 Aug 2022 none Apache-2.0 — Details →
0.0.1 31 Jan 2022 H3 Apache-2.0 Yes Details →

All 10 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 3

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 apache-avro

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-36125: Apache Avro Rust SDK corrupted data read can cause crash 7.5 high 0.14.0 10 Aug 2022
CVE-2022-35724: Apache Avro Rust SDK Vulnerability in reader looping 7.5 high 0.14.0 10 Aug 2022
CVE-2022-36124: Apache Avro Rust SDK's Reader Memory Consumption Vulnerability 7.5 high 0.14.0 10 Aug 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 apache-avro

Is apache-avro safe to use?

Vulert records 3 vulnerabilities for apache-avro in crates.io: 0 critical, 3 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is apache-avro's Vulert package health score?

Vulert scores apache-avro 75/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 apache-avro affected?

No. 0.22.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 apache-avro should I use?

0.22.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 apache-avro have?

3 vulnerabilities are recorded for apache-avro in the crates.io ecosystem: 0 critical, 3 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apache-avro vulnerabilities disclosed?

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

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