Apache Arrow: Potential use-after-free when reading IPC file with pre-buffering
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++:
-
check whether you enable pre-buffering on the IPC file reader (using
RecordBatchFileReader::PreBufferMetadata) -
if so, either disable pre-buffering (which may have adverse performance consequences), or switch to Arrow 23.0.1 which is not vulnerable
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Python (PyPI) | pyarrow | >= 15.0.0, < 23.0.1 | 23.0.1 |
Odnośniki
- http://www.openwall.com/lists/oss-security/2026/02/17/4
- https://lists.apache.org/thread/mpm4ld1qony30tchfpjtk5b11tcyvmwh
- https://github.com/apache/arrow/pull/48925
- https://github.com/advisories/GHSA-rgxp-2hwp-jwgg
- https://nvd.nist.gov/vuln/detail/CVE-2026-25087
- https://github.com/apache/arrow
- https://github.com/pypa/advisory-database/tree/main/vulns/pyarrow/PYSEC-2026-113.yaml
- Wektor CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H- Słabość (CWE)
CWE-416- Platforma
- Python (PyPI)
- Paczka
pyarrow- Ujawniono
- 17.02.2026
- Aktualizacja
- 11.10.2026 15:17
Źródła i licencje
OSV / GitHub Advisory Database - PYSEC-2026-113 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-rgxp-2hwp-jwgg - CC BY 4.0
Historia podatności: pyarrow
Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 5
- Pierwsza → ostatnia
- 11.2019 02.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Krytyczna 1
- Wysoka 3
- Nieoceniona 1
Ujawnienia w latach
- 2019: 2
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 1
- 2024: 1
- 2025: 0
- 2026: 1
-
Apache Arrow: Potential use-after-free when reading IPC file with pre-buffering ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.