{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-25087", "tracking": { "current_release_date": "2026-03-21T15:39:15.601750Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-25087", "initial_release_date": "2026-02-17T14:25:14.921923Z", "revision_history": [ { "date": "2026-02-17T14:25:14.921923Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| References created (2).| CWES updated (1)." }, { "date": "2026-02-17T14:25:16.558519Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-02-17T14:39:04.712463Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| Products created (2).| References created (2).| CWES updated (1)." }, { "date": "2026-02-17T14:39:16.944811Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-02-17T15:28:33.477548Z", "number": "5", "summary": "CVSS created." }, { "date": "2026-02-17T15:28:39.709226Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-02-17T15:35:16.686121Z", "number": "7", "summary": "NCSC Score updated." }, { "date": "2026-02-17T15:46:19.135347Z", "number": "8", "summary": "CVSS created.| Unknown change." }, { "date": "2026-02-17T15:46:21.622675Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-02-17T17:31:21.871254Z", "number": "10", "summary": "NCSC Score updated." }, { "date": "2026-02-17T19:26:07.409512Z", "number": "11", "summary": "References created (1)." }, { "date": "2026-02-17T20:16:10.936148Z", "number": "12", "summary": "References created (1)." }, { "date": "2026-02-18T00:27:49.304009Z", "number": "13", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (2).| Product Identifiers created (1).| Product Remediations created (2).| References created (4).| CWES updated (1).| Vendor_assessment created." }, { "date": "2026-02-18T00:27:59.202040Z", "number": "14", "summary": "NCSC Score updated." }, { "date": "2026-02-18T00:42:50.316292Z", "number": "15", "summary": "Source created.| CVE status created. (valid)" }, { "date": "2026-02-18T06:42:53.661276Z", "number": "16", "summary": "Description created for source." }, { "date": "2026-02-18T15:04:49.812455Z", "number": "17", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-02-18T15:04:56.910924Z", "number": "18", "summary": "NCSC Score updated." }, { "date": "2026-02-26T17:30:18.724814Z", "number": "19", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (3)." }, { "date": "2026-02-26T17:30:23.825984Z", "number": "20", "summary": "NCSC Score updated." }, { "date": "2026-03-11T15:25:18.597771Z", "number": "21", "summary": "Products created (1).| Product Identifiers created (1)." }, { "date": "2026-03-11T15:25:29.769722Z", "number": "22", "summary": "NCSC Score updated." }, { "date": "2026-03-12T15:06:58.521994Z", "number": "23", "summary": "EPSS updated." }, { "date": "2026-03-12T15:07:00.249214Z", "number": "24", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:48:59.196210Z", "number": "25", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-21T15:39:04.788082Z", "number": "26", "summary": "EPSS updated." }, { "date": "2026-03-21T15:39:12.135786Z", "number": "27", "summary": "NCSC Score updated." } ], "status": "interim", "version": "27" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:semver/15.0.0|<=23.0.0", "product": { "name": "vers:semver/15.0.0|<=23.0.0", "product_id": "CSAFPID-5623114" } }, { "category": "product_version_range", "name": "vers:semver/23.0.1", "product": { "name": "vers:semver/23.0.1", "product_id": "CSAFPID-5623115" } } ], "category": "product_name", "name": "Apache Arrow" } ], "category": "vendor", "name": "Apache Software Foundation" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:rpm/unknown", "product": { "name": "vers:rpm/unknown", "product_id": "CSAFPID-1439279", "product_identification_helper": { "cpe": "cpe:/a:redhat:openshift_ai" } } } ], "category": "product_name", "name": "Red Hat OpenShift AI (RHOAI)" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:rpm/unknown", "product": { "name": "vers:rpm/unknown", "product_id": "CSAFPID-2976378" } } ], "category": "product_name", "name": "odh-feature-server-rhel9" } ], "category": "product_family", "name": "Red Hat OpenShift AI (RHOAI)" } ], "category": "vendor", "name": "Red Hat" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=15.0.0|<23.0.1", "product": { "name": "vers:unknown/>=15.0.0|<23.0.1", "product_id": "CSAFPID-5795204", "product_identification_helper": { "cpe": "cpe:2.3:a:apache:arrow:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "arrow" } ], "category": "vendor", "name": "Apache" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-25087", "cwe": { "id": "CWE-416", "name": "Use After Free" }, "notes": [ { "category": "description", "text": "Use After Free vulnerability in Apache Arrow C++.\n\nThis 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` object) that is written to the dangling pointer is not under direct control of the attacker.\n\nPre-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.\n\nThe 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.\n\nAdvice for users of Arrow C++:\n\n1. check whether you enable pre-buffering on the IPC file reader (using `RecordBatchFileReader::PreBufferMetadata`)\n\n2. if so, either disable pre-buffering (which may have adverse performance consequences), or switch to Arrow 23.0.1 which is not vulnerable", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-25087" }, { "category": "description", "text": "Use After Free vulnerability in Apache Arrow C++.\n\nThis 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` object) that is written to the dangling pointer is not under direct control of the attacker.\n\nPre-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.\n\nThe 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.\n\nAdvice for users of Arrow C++:\n\n1. check whether you enable pre-buffering on the IPC file reader (using `RecordBatchFileReader::PreBufferMetadata`)\n\n2. if so, either disable pre-buffering (which may have adverse performance consequences), or switch to Arrow 23.0.1 which is not vulnerable", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-25087" }, { "category": "description", "text": "No description is available for this CVE.", "title": "redhat - https://access.redhat.com/security/cve/CVE-2026-25087" }, { "category": "description", "text": "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` 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", "title": "debian - https://security-tracker.debian.org/tracker/CVE-2026-25087" }, { "category": "description", "text": "Use After Free vulnerability in Apache Arrow C++.\n\nThis 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` object) that is written to the dangling pointer is not under direct control of the attacker.\n\nPre-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.\n\nThe 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.\n\nAdvice for users of Arrow C++:\n\n1. check whether you enable pre-buffering on the IPC file reader (using `RecordBatchFileReader::PreBufferMetadata`)\n\n2. if so, either disable pre-buffering (which may have adverse performance consequences), or switch to Arrow 23.0.1 which is not vulnerable", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-25087.json?alt=media" }, { "category": "other", "text": "0.00058", "title": "EPSS" }, { "category": "other", "text": "4.2", "title": "NCSC Score" }, { "category": "other", "text": "Is related to a product by vendor Apache", "title": "NCSC Score top decreasing factors" }, { "category": "details", "text": "Severity: 2\n", "title": "Vendor assessment" } ], "product_status": { "known_affected": [ "CSAFPID-5623114", "CSAFPID-1439279", "CSAFPID-2976378", "CSAFPID-5795204" ], "known_not_affected": [ "CSAFPID-5623115" ] }, "references": [ { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25087" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-25087" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-25087" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/25xxx/CVE-2026-25087.json" }, { "category": "external", "summary": "Source - redhat", "url": "https://access.redhat.com/security/cve/CVE-2026-25087" }, { "category": "external", "summary": "Source raw - redhat", "url": "https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-25087.json" }, { "category": "external", "summary": "Source - debian", "url": "https://security-tracker.debian.org/tracker/CVE-2026-25087" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-25087" }, { "category": "external", "summary": "Source raw - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-25087.json?alt=media" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd; osv; redhat", "url": "https://github.com/apache/arrow/pull/48925" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd; osv; redhat", "url": "https://lists.apache.org/thread/mpm4ld1qony30tchfpjtk5b11tcyvmwh" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd; osv", "url": "http://www.openwall.com/lists/oss-security/2026/02/17/4" }, { "category": "external", "summary": "Reference - redhat", "url": "https://www.cve.org/CVERecord?id=CVE-2026-25087" }, { "category": "external", "summary": "Reference - redhat", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25087" } ], "remediations": [ { "category": "mitigation", "details": "Mitigation 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.", "product_ids": [ "CSAFPID-1439279", "CSAFPID-2976378" ] } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H", "baseScore": 7.0, "baseSeverity": "HIGH" }, "products": [ "CSAFPID-1439279", "CSAFPID-2976378", "CSAFPID-5623114", "CSAFPID-5795204" ] } ], "title": "CVE-2026-25087" } ] }