Is org.apache.avro:avro 1.11 vulnerable?
Maven · 6 releases from 1.11.0 to 1.11.5 · latest org.apache.avro:avro is 1.12.2 · checked 18 Nov 2026
No known advisories in the last release
org.apache.avro:avro 1.11.5, the last 1.11 release, has no known advisories. 2 advisories affect earlier 1.11.x releases, so update to 1.11.5.
mvn versions:use-dep-version -Dincludes=org.apache.avro:avro -DdepVersion=1.11.5 -DforceVersion=trueIs your project on an affected org.apache.avro:avro?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.11.x, affecting earlier releases
Apache Avro Java SDK: Arbitrary Code Execution when reading Avro Data (Java SDK)
- Affected
- <1.11.4
- Fixed in
- 1.11.4
Apache Avro Java SDK vulnerable to Improper Input Validation
- Affected
- <1.11.3
- Fixed in
- 1.11.3
Every org.apache.avro:avro 1.11.x release
Affected: 1.11.0 to 1.11.3. 1.11.4 and later are not affected. Latest org.apache.avro:avro: 1.12.2.
| Version | Known advisories |
|---|---|
| org.apache.avro:avro 1.11.5 | None |
| org.apache.avro:avro 1.11.4 | None |
| org.apache.avro:avro 1.11.3 | CVE-2024-47561 |
| org.apache.avro:avro 1.11.2 | CVE-2024-47561, CVE-2023-39410 |
| org.apache.avro:avro 1.11.1 | CVE-2024-47561, CVE-2023-39410 |
| org.apache.avro:avro 1.11.0 | CVE-2024-47561, CVE-2023-39410 |
Which of your client projects are still on org.apache.avro:avro 1.11?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.avro:avro version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.avro:avro versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.