Apache Parquet security advisories
Security information for Apache Parquet
Reporting
Do you want to disclose a potential security issue for Apache Parquet? Send your report to the Apache Security Team.
You can read more about the security policy on:
Advisories
This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. It may also lack details found on the project security page linked above. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org
File-controlled KMS URL is forwarded to pluggable KmsClient that skips host validation
CVE-2026-73334 [CVE] [CVE json] [OSV json]
Last updated: 2026-09-09T10:48:34.905Z
Affected
- Apache Parquet Hadoop from 1.12 through 1.18.0
Description
Potential problem for users of the org.apache.parquet.crypto.keytools package in Apache Parquet, versions 1.12 to 1.18.
This package enables users to encrypt Parquet files via an envelope encryption mechanism that wraps (encrypts) data keys via a Key Management Service (KMS).
On the reader side, the KMS URL can be application-controlled or file-controlled.
If the user does not leverage application control for this parameter, a file-controlled KMS URL is forwarded to a pluggable KmsClient implementation.
If the pluggable implementation does not perform host validation, a KMS token can be sent to a malicious host set by an attacker in the file.
Before the problem is fixed, users are recommended to leverage application control for KMS URL parameter in readers (versions 1.12-1.18).
After the problem is fixed (presumably in version 1.19), the upgrade will disable file-controlled KMS URL by default. Users of the KMS URL parameter
will have two options then: leverage application control for KMS URL parameter in readers, or enable file-controlled KMS URL (via a new app parameter).
The latter option will explicitly require (in the new parameter documentation) to validate the KMS URL and use authentication in the custom implementation of the KMS client plug in.
References
Credits
- n0mi1k (finder)
Potential malicious code execution from trusted packages in the parquet-avro module when reading an Avro schema from a Parquet file metadata
CVE-2025-46762 [CVE] [CVE json] [OSV json]
Last updated: 2025-05-06T09:08:12.043Z
Affected
- Apache Parquet Java through 1.15.1
Description
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.
References
Credits
- Andrew Pikler (reporter)
- David Handermann (reporter)
- Nándor Kollár (reporter)
Arbitrary code execution in the parquet-avro module when reading an Avro schema from a Parquet file metadata
CVE-2025-30065 [CVE] [CVE json] [OSV json]
Last updated: 2025-07-11T10:32:31.431Z
Affected
- Apache Parquet Java through 1.15.0
Description
Schema parsing in the parquet-avro module of Apache Parquet 1.15.0 and previous versions allows bad actors to execute arbitrary code
Users are recommended to upgrade to version 1.15.1, which fixes the issue.
References
Credits
- Keyi Li (Amazon) (finder)
Apache Parquet-MR potential DoS in case of malicious Parquet file
CVE-2021-41561 [CVE] [CVE json] [OSV json]
Last updated: 2021-12-20T11:09:26.601Z
Affected
- Apache Parquet from 1.9.0 before Parquet-MR*
Description
Improper Input Validation vulnerability in Parquet-MR of Apache Parquet allows an attacker to DoS by malicious Parquet files. This issue affects Apache Parquet-MR version 1.9.0 and later versions.
References
Credits
- This issue was discovered by Sergey Temnikov of the Amazon S3 team.