Skip to main content
No exploitation reportedFix available

CVE-2026-25087

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

No exploitation reported by the sources we read.

  • Published2026-02-17
  • Fixed in23.0.1
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

Timeline

dates in UTC
  1. 2026-02-1714:16CVE publishedNVD

Versions per branch

NVD · OSV
Apache arrow
BranchAffectedFixed in
23.0≥ 15.0.0, < 23.0.123.0.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Arrowother versions: not affected
    Affected
    • ≥ 15.0.0, ≤ 23.0.0no fix statedsemver

    Not affected = 23.0.1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • airflow-2MinimOSall versions · fixed in 2.11.2-r0
  • airflow-2Chainguardall versions · fixed in 2.11.2-r27
  • airflow-3MinimOSall versions · fixed in 3.2.0-r0
  • apache-arrowopenSUSE:Tumbleweedall versions · fixed in 26.0.0-1.1
  • apache-arrowDebian:14all versions · fixed in 23.0.1-1
  • dbt-bigqueryChainguardall versions · fixed in 1.10.3-r3
  • label-studioMinimOSall versions · fixed in 0and 2 other packages
  • libarrowAzure Linux:3all versions · fixed in 15.0.0-8

10 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-25087 Red Hat Product Security2 products fixed · 1 known affected

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

    rhoai/odh-feature-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI)

  • RHSA-2026:61628 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat AI Inference Server Model Optimization Tools 3.2.2 (CUDA)

Full record on NVD

Fix

  1. Update Apache arrow to 23.0.1
  2. Vendor fix Red Hat Product Security RHSA-2026:61628 · 2 productsFor more information visit https://access.redhat.com/errata/RHSA-2026:61628
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:61628 · 2 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  4. No fix available, says the vendor Red Hat Product Security CVE-2026-25087 · 1 productFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Published
2026-02-17
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-rgxp-2hwp-jwgg

Frequently asked questions

What is CVE-2026-25087?

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

Is CVE-2026-25087 actively exploited?

Active exploitation of CVE-2026-25087 has not been confirmed. Its EPSS score was 0.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-25087?

CVE-2026-25087 has a CVSS v3 base score of 7 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H.

Running apache-arrow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record