Advisory record · GHSA-53wx-pr6q-m3j5

Apache Parquet Java: Potential malicious code execution from trusted packages in the parquet-avro module when reading an Avro schema from a Parquet file metadata

CVSS 7.1 HighEPSS 0.016 · 76th percentile

Published by the GitHub Advisory Database at 6 May 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.parquet:parquet-avroMaven<1.15.21.15.2
Identifiers
GHSA-53wx-pr6q-m3j5 · CVE-2025-46762
Weakness (CWE)
CWE-73
Published
6 May 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Parquet Java's parquet-avro module, org.apache.parquet:parquet-avro versions before 1.15.2, can be made to execute arbitrary code when it parses an Avro schema stored in a Parquet file's metadata. The source says that 1.15.1's restriction to untrusted packages still leaves malicious classes from the default trusted packages executable, and that the issue only affects client code that deliberately uses the "specific" or "reflect" models, not "generic". Upgrade to 1.15.2, or on 1.15.1 set the system property org.apache.parquet.avro.SERIALIZABLE_PACKAGES to an empty string.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H/S:N/RE:M/U:Amber CNA (apache)
  • CISA KEV Not listed.
  • EPSS 0.016, the 76th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.