Skip to content
Fencer Vulns
high 7.0

CVE-2026-25087 json

Apache Arrow: Potential use-after-free when reading IPC file with pre-buffering

published 2026-02-17 8 mo ago modified 2026-09-10 1 mo ago also EUVD-2026-8013 , GHSA-rgxp-2hwp-jwgg , JLSEC-2026-805 , PYSEC-2026-113

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Use After Free vulnerability in Apache Arrow C++.

This issue affects Apache Arrow C++ from 15.0.0 through 23.0.0. It can be triggered when reading an Arrow IPC file (but not an IPC stream) with pre-buffering enabled, if the IPC file contains data with variadic buffers (such as Binary View and String View data). Depending on the number of variadic buffers in a record batch column and on the temporal sequence of multi-threaded IO, a write to a dangling pointer could occur. The value (a `std::shared_ptr<Buffer>` object) that is written to the dangling pointer is not under direct control of the attacker.

Pre-buffering is disabled by default but can be enabled using a specific C++ API call (`RecordBatchFileReader::PreBufferMetadata`). The functionality is not exposed in language bindings (Python, Ruby, C GLib), so these bindings are not vulnerable.

The most likely consequence of this issue would be random crashes or memory corruption when reading specific kinds of IPC files. If the application allows ingesting IPC files from untrusted sources, this could plausibly be exploited for denial of service. Inducing more targeted kinds of misbehavior (such as confidential data extraction from the running process) depends on memory allocation and multi-threaded IO temporal patterns that are unlikely to be easily controlled by an attacker.

Advice for users of Arrow C++:

1. check whether you enable pre-buffering on the IPC file reader (using `RecordBatchFileReader::PreBufferMetadata`)

2. if so, either disable pre-buffering (which may have adverse performance consequences), or switch to Arrow 23.0.1 which is not vulnerable

Patch / fix

  • pypi pyarrow 23.0.1
  • julia Arrow_jll 24.0.0+0
  • Apache Software Foundation Apache Arrow 23.0.1
  • apache-arrow Debian 14 23.0.1-1

debian advisories DEBIAN-CVE-2026-25087

  • apache-arrow openSUSE Tumbleweed 26.0.0-1.1

opensuse advisories openSUSE-SU-2026:12191-1

  • libarrow Azure Linux 3.0 15.0.0-8

azure linux advisories AZL-78129

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-25087 updated cvss 5.3

apache-arrow: Apache Arrow C++: Denial of Service via Use After Free vulnerability when reading IPC files

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat AI Inference Server 3.2 rhaiis/model-opt-cuda-rhel9 1787772157
    fixed: vendor fix RHSA-2026:61628

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8 mo ago

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
GitHub 3.1 7.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
CNA 3.1 7.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
OSV 3.1 7.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Affected packages

ecosystem package affected fixed in
pypi pyarrow
>=15.0.0, <23.0.1
23.0.1
julia Arrow_jll
>=18.1.0+0, <24.0.0+0
24.0.0+0

Affected products

  • Apache Software Foundation Apache Arrow

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.