Skip to main content
VulnerabilityPublished Updated

CVE-2026-92287: Pass-through of unvalidated KMS URLs to KMS clients in Apache C++ Parquet and PyArrow versions 4.0.0

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-92287· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 26.0.0 soon.

Data as of 29 Oct 2026, 22:46 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.18.1
Patch
Available – fixed in 26.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Apache Arrow C++ and PyArrow and apache/arrow and pyarrow to 26.0.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Arrow C++Affected
  • >=4.0.0 <26.0.0
Fixed in
  • 26.0.0
PyArrowpyarrowAffected
  • >=8.0.0 <26.0.0
Fixed in
  • 26.0.0
GitHubapache/arrowpkg:github/apache/arrowOther threatsAffected
  • <26.0.0 >=4.0.0
Fixed in
  • 26.0.0
PyPIpyarrowpkg:pypi/pyarrowOther threatsAffected
  • >=8.0.0 <26.0.0
Fixed in
  • 26.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Pass-through of unvalidated KMS URLs to KMS clients in Apache C++ Parquet and PyArrow versions 4.0.0 to 25.0.1. This affects users who read Parquet files and configure Parquet decryption properties with a KmsClient implementation. On the reader side, the KMS URL can be application-controlled (specified in the KmsConnectionConfig) 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 KMS implementation does not perform host validation and makes use of the provided KMS URL, a KMS token can be sent to a malicious host set by an attacker in the file. Users are recommended to upgrade to version 26.0.0, which disables this behavior by default and requires that users opt-in to it by enabling the read_kms_url flag in the DecryptionConfiguration. Users of affected versions are recommended to either specify the KMS URL in the KmsConnectionConfig when reading files, or ensure any KmsClient implementations validate received KMS URLs. Users that opt-in to file-controlled KMS URLs in version 26.0.0 and later must ensure KmsClients validate KMS URLs.

References

Community reviews

Loading reviews…