CVE-2026-73334: CWE-20 Improper Input Validation in Apache Software Foundation Apache Parquet Hadoop
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.
AI Analysis
Technical Summary
This vulnerability affects Apache Parquet Hadoop versions 1.12 to 1.18 in the org.apache.parquet.crypto.keytools package, which supports envelope encryption using a Key Management Service (KMS). The KMS URL parameter can be controlled either by the application or by the file. When file-controlled, the URL is forwarded to a pluggable KmsClient implementation without guaranteed host validation. If the KmsClient does not validate the host, an attacker can specify a malicious host in the file, causing sensitive KMS tokens to be sent to an unauthorized party. The vulnerability stems from improper input validation (CWE-20). The vendor recommends users leverage application control of the KMS URL parameter as a mitigation until the issue is fixed. The anticipated fix in version 1.19 will disable file-controlled KMS URLs by default and require explicit validation and authentication if this feature is enabled.
Potential Impact
If exploited, this vulnerability could lead to the exposure of sensitive KMS tokens to an attacker-controlled host, potentially compromising the confidentiality of encrypted Parquet files. The impact depends on whether the KmsClient implementation performs host validation and whether the KMS URL is file-controlled. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Users should enforce application control over the KMS URL parameter in readers for affected versions 1.12 through 1.18 to prevent malicious hosts from receiving KMS tokens. After upgrading to version 1.19 or later, file-controlled KMS URLs will be disabled by default. If file-controlled KMS URLs are enabled via a new application parameter, users must ensure that their KmsClient implementation performs strict host validation and uses authentication as documented. Patch status is not yet confirmed—check the vendor advisory for current remediation guidance.
CVE-2026-73334: CWE-20 Improper Input Validation in Apache Software Foundation Apache Parquet Hadoop
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.
Affected software
pkg:maven/Apache Software Foundation/org.apache.parquet.crypto.keytools:parquet-hadoopRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability affects Apache Parquet Hadoop versions 1.12 to 1.18 in the org.apache.parquet.crypto.keytools package, which supports envelope encryption using a Key Management Service (KMS). The KMS URL parameter can be controlled either by the application or by the file. When file-controlled, the URL is forwarded to a pluggable KmsClient implementation without guaranteed host validation. If the KmsClient does not validate the host, an attacker can specify a malicious host in the file, causing sensitive KMS tokens to be sent to an unauthorized party. The vulnerability stems from improper input validation (CWE-20). The vendor recommends users leverage application control of the KMS URL parameter as a mitigation until the issue is fixed. The anticipated fix in version 1.19 will disable file-controlled KMS URLs by default and require explicit validation and authentication if this feature is enabled.
Potential Impact
If exploited, this vulnerability could lead to the exposure of sensitive KMS tokens to an attacker-controlled host, potentially compromising the confidentiality of encrypted Parquet files. The impact depends on whether the KmsClient implementation performs host validation and whether the KMS URL is file-controlled. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Users should enforce application control over the KMS URL parameter in readers for affected versions 1.12 through 1.18 to prevent malicious hosts from receiving KMS tokens. After upgrading to version 1.19 or later, file-controlled KMS URLs will be disabled by default. If file-controlled KMS URLs are enabled via a new application parameter, users must ensure that their KmsClient implementation performs strict host validation and uses authentication as documented. Patch status is not yet confirmed—check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-08-12T06:00:31.756Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa13a92acd9273b4930a731
Added to database: 09/09/2026, 10:53:06 UTC
Last enriched: 09/09/2026, 11:10:46 UTC
Last updated: 09/09/2026, 16:15:18 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.