dbcve.org
ParquetApplication · Apache

CVE-2025-46762

HIGH · 8.1 CVSS v3.1 Published 2025-05-06
Fix available
A fix is available. Upgrade to 1.15.2 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Schema parsing in the parquet-avro module of Apache Parquet 1.15.0 and previous versions allows bad actors to execute arbitrary code. While 1.15.1 introduced a fix to restrict untrusted packages, the default setting of trusted packages still allows malicious classes from these packages to be executed. The exploit is only applicable if the client code of parquet-avro uses the "specific" or the "reflect" models deliberately for reading Parquet files. ("generic" model is not impacted) Users are recommended to upgrade to 1.15.2 or set the system property "org.apache.parquet.avro.SERIALIZABLE_PACKAGES" to an empty string on 1.15.1. Both are sufficient to fix the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The parquet-avro module's schema parsing in Apache Parquet 1.15.0 and prior versions allows arbitrary code execution through unsafe deserialization of untrusted packages. While version 1.15.1 attempted to restrict untrusted packages, the default trusted package configuration still permits malicious classes to execute when using the 'specific' or 'reflect' reading models (but not 'generic').

MitigationUpgrade to Apache Parquet 1.15.2 or set the system property 'org.apache.parquet.avro.SERIALIZABLE_PACKAGES' to an empty string as a workaround on 1.15.1. Verify that no critical functionality depends on the affected 'specific' or 'reflect' models before upgrading.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ParquetApplication
Affected:< 1.15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Parquet version
    Check your project's dependency management file (pom.xml, build.gradle, or equivalent) for the parquet-avro or parquet version, or run a dependency tree command to list the parquet version in use
    Affected if The version listed is 1.15.2 or higher, then you are NOT affected. If version is lower than 1.15.2, continue to the next checks.
  2. Verify if parquet-avro module is in use
    Search your codebase for imports or references to org.apache.parquet.avro, specifically looking for AvroParquetReader or similar parquet-avro reader classes
    Affected if Your application does not use the parquet-avro module at all, then you are NOT affected by this specific vulnerability.
  3. Determine which Avro reading model is used
    Inspect your code where parquet-avro readers are instantiated. Look for Reader' methods or configuration that specify 'specific', 'reflect', or 'generic' model types. Common patterns include SpecificData or ReflectData classes, or corresponding configuration properties.
    Affected if The code uses 'specific' or 'reflect' reading models (not 'generic'), and your Parquet version is below 1.15.2, then you ARE likely affected by this vulnerability.
  4. Check for deserialization of untrusted Avro data
    Review whether the parquet-avro reader processes data from untrusted sources (external APIs, user uploads, network streams from non-authenticated sources)
    Affected if The application deserializes Avro/Parquet data from untrusted sources using 'specific' or 'reflect' models on a vulnerable version, then you ARE directly affected.

You are affected if your Apache Parquet version is below 1.15.2, you use the parquet-avro module, and your application deserializes untrusted Avro data using the 'specific' or 'reflect' reading models.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.2 or later
Fixed in 1.15.2
Interim mitigation

Upgrade to Apache Parquet 1.15.2 or set the system property 'org.apache.parquet.avro.SERIALIZABLE_PACKAGES' to an empty string as a workaround on 1.15.1. Verify that no critical functionality depends on the affected 'specific' or 'reflect' models before upgrading.

Recommended fix High confidence

Apache Parquet 1.15.2

  1. 1. Update the parquet-mr dependency in your project's pom.xml (Maven) or build.gradle (Gradle) to version 1.15.2 or later
  2. 2. Rebuild and redeploy your application with the updated dependency
  3. 3. For users on version 1.15.1 who cannot upgrade immediately, add the JVM argument -Dorg.apache.parquet.avro.SERIALIZABLE_PACKAGES="" to disable the default trusted packages setting

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parquet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46762 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data