VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pyarrow: vulnerability history, versions and safety

pyarrow is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 65 releases, from Nov 2019 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C1 H5 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 17 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pyarrow vulnerabilities

Vulert verdict on pyarrow 26.0.0 i

Updated on 23 Oct 2026

Action needed: 26.0.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 85/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 26.0.0 — affected i
  • Vulnerabilities on record 11 over 6 years · 2 in the last year i
  • Latest disclosure 17 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 18,074 packages i
  • Stars 17,216 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for pyarrow, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.0.0 09 Oct 2026 U1 Apache-2.0 Yes Details →
25.0.1 10 Aug 2026 U1 Apache-2.0 Yes Details →
25.0.0 10 Jul 2026 U1 Apache-2.0 Yes Details →
24.0.0 21 Apr 2026 U1 Apache-2.0 Yes Details →
23.0.1 16 Feb 2026 U1 Apache-2.0 Yes Details →
23.0.0 18 Jan 2026 H1 U1 Apache-2.0 Yes Details →
22.0.0 24 Oct 2025 H1 U1 non-standard Yes Details →
21.0.0 18 Jul 2025 H1 U1 non-standard Yes Details →
20.0.0 27 Apr 2025 H1 U1 non-standard Yes Details →
19.0.1 18 Feb 2025 H1 U1 non-standard Yes Details →
19.0.0 16 Jan 2025 H1 U1 non-standard Yes Details →
18.1.0 26 Nov 2024 H1 U1 non-standard Yes Details →
18.0.0 28 Oct 2024 H1 U1 non-standard Yes Details →
17.0.0 16 Jul 2024 H1 U1 non-standard Yes Details →
16.1.0 14 May 2024 H1 U2 Apache-2.0 Yes Details →
16.0.0 20 Apr 2024 H1 U2 Apache-2.0 Yes Details →
15.0.2 18 Mar 2024 H1 U2 Apache-2.0 Yes Details →
15.0.1 07 Mar 2024 H1 U2 Apache-2.0 Yes Details →
15.0.0 21 Jan 2024 H1 U2 Apache-2.0 Yes Details →
14.0.2 18 Dec 2023 U1 Apache-2.0 Yes Details →
14.0.1 08 Nov 2023 U1 Apache-2.0 Yes Details →
14.0.0 01 Nov 2023 C1 U2 Apache-2.0 Yes Details →
13.0.0 23 Aug 2023 C1 U2 Apache-2.0 Yes Details →
12.0.1 13 Jun 2023 C1 U2 Apache-2.0 Yes Details →
12.0.0 02 May 2023 C1 U2 Apache-2.0 Yes Details →
11.0.0 27 Jan 2023 C1 U2 Apache-2.0 Yes Details →
10.0.1 22 Nov 2022 C1 U2 Apache-2.0 Yes Details →
10.0.0 27 Oct 2022 C1 U2 Apache-2.0 Yes Details →
9.0.0 03 Aug 2022 C1 U2 Apache-2.0 Yes Details →
8.0.0 06 May 2022 C1 U2 Apache-2.0 Yes Details →
7.0.0 03 Feb 2022 C1 U2 Apache-2.0 Yes Details →
6.0.1 18 Nov 2021 C1 U2 Apache-2.0 Yes Details →
6.0.0 26 Oct 2021 C1 U2 Apache-2.0 Yes Details →
5.0.0 28 Jul 2021 C1 U2 Apache-2.0 Yes Details →
4.0.1 30 May 2021 C1 U2 Apache-2.0 Yes Details →
4.0.0 26 Apr 2021 C1 U2 Apache-2.0 Yes Details →
3.0.0 26 Jan 2021 C1 U1 Apache-2.0 Yes Details →
2.0.0 19 Oct 2020 C1 U1 Apache-2.0 Yes Details →
1.0.1 21 Aug 2020 C1 U1 Apache-2.0 Yes Details →
1.0.0 24 Jul 2020 C1 U1 Apache-2.0 Yes Details →
0.17.1 18 May 2020 C1 U1 Apache-2.0 Yes Details →
0.17.0 20 Apr 2020 C1 U1 Apache-2.0 Yes Details →
0.16.0 11 Feb 2020 C1 U1 Apache-2.0 Yes Details →
0.15.1 01 Nov 2019 C1 U1 Apache-2.0 Yes Details →
0.15.0 05 Oct 2019 C1 H4 U1 Apache-2.0 Yes Details →
0.14.1 22 Jul 2019 C1 H4 U3 Apache-2.0 Yes Details →
0.14.0 04 Jul 2019 C1 H4 U3 Apache-2.0 Yes Details →
0.13.0 31 Mar 2019 H2 U1 Apache-2.0 Yes Details →
0.12.1 25 Feb 2019 H2 U1 Apache-2.0 Yes Details →
0.12.0 20 Jan 2019 H2 U1 Apache-2.0 Yes Details →
0.11.1 24 Oct 2018 U1 Apache-2.0 Yes Details →
0.11.0 11 Oct 2018 U1 Apache-2.0 Yes Details →
0.10.0 06 Aug 2018 U1 Apache-2.0 Yes Details →
0.9.0 06 Apr 2018 U1 Apache-2.0 Yes Details →
0.2.0 — U1 — Yes Details →
0.3.0 — U1 — Yes Details →
0.4.0 — U1 — Yes Details →
0.4.1 — U1 — Yes Details →
0.5.0 — U1 — Yes Details →
0.5.0.post2 — U1 — Yes Details →
0.6.0 — U1 — Yes Details →
0.7.0 — U1 — Yes Details →
0.7.1 — U1 — Yes Details →
0.8.0 — U1 — Yes Details →
0.9.0.post1 — U1 — Yes Details →

All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2022 4
  • 2023 2
  • 2024 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pyarrow

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-47248: PyArrow Arbitrary Code Execution Vulnerability 9.8 critical 14.0.1 09 Nov 2023
CVE-2019-12408: Missing Initialization of Resource in Apache Arrow 7.5 high 0.15.1 24 May 2022
CVE-2019-12410: Missing Initialization of Resource in Apache Arrow 7.5 high 0.15.1 24 May 2022
CVE-2026-25087: Use After Free Vulnerability in pyarrow Package 7.0 high 23.0.1 17 Feb 2026
CVE-2026-25087: Apache Arrow pyarrow Use-After-Free Vulnerability in IPC File Reading 7.0 high 23.0.1 17 Feb 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pyarrow

Is pyarrow safe to use?

Vulert records 11 vulnerabilities for pyarrow in PyPI: 1 critical, 5 high, 0 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pyarrow's Vulert package health score?

Vulert scores pyarrow 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of pyarrow affected?

Yes. 26.0.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of pyarrow should I use?

26.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does pyarrow have?

11 vulnerabilities are recorded for pyarrow in the PyPI ecosystem: 1 critical, 5 high, 0 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pyarrow vulnerabilities disclosed?

2 vulnerabilities were recorded for pyarrow in the last 12 months, and the oldest entry in this database dates to 08 Nov 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pyarrow are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pyarrow for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pyarrow version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.