How severe is CVE-2023-47248?

CVE-2023-47248 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-47248?

CVE-2023-47248 affects the following packages: pyarrow (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2023-47248?

Update pyarrow to 14.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-47248 is resolved across your whole dependency graph.

How do I detect CVE-2023-47248 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyarrow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-47248 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2023-47248 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-47248 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-47248?

CVE-2023-47248 has an EPSS (Exploit Prediction Scoring System) score of 14.5%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2023-47248?

CVE-2023-47248 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2023-47248?

A Nuclei detection template exists for CVE-2023-47248, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-47248 published, and has it been updated?

CVE-2023-47248 was published on November 9, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2023-47248 — pyarrow

CRITICALFix: apache/arrow@f141709

CVE-2023-47248 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in pyarrow. EPSS puts its 30-day exploitation probability at 14.5% (97th percentile). A fix is available for pyarrow — see the affected versions and patch details below.

PyArrow, PyArrow: Arbitrary code execution when loading a malicious data file

Also known asGHSA-5wvp-7f3h-6wmmPYSEC-2023-238

Published

Nov 9, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

14.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍pyarrow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

This vulnerability only affects PyArrow, not other Apache Arrow implementations or bindings.

It is recommended that users of PyArrow upgrade to 14.0.1. Similarly, it is recommended that downstream libraries upgrade their dependency requirements to PyArrow 14.0.1 or later. PyPI packages are already available, and we hope that conda-forge packages will be available soon.

If it is not possible to upgrade, we provide a separate package pyarrow-hotfix that disables the vulnerability on older PyArrow versions. See https://pypi.org/project/pyarrow-hotfix/ for instructions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pyarrow`	≥ 0.14.0&&< 14.0.1	14.0.1`pip install --upgrade 'pyarrow==14.0.1'`

Affected Products

1 product · 1 configurations

Application

pyarrowapache

≥ 0.14.0 && ≤ 14.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyarrow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pyarrow to 14.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-47248 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

How to detect CVE-2023-47248

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-47248 -u https://target

Template: PyArrow Flight RPC - Remote Code Execution
Severity: critical
Impact: Unauthenticated attackers can exploit deserialization vulnerabilities through maliciously crafted Python-defined extension types in Flight RPC to execute arbitrary code and completely compromise PyArrow installations.
Remediation: Upgrade to PyArrow v14.0.1 or later.

Template by ProjectDiscovery nuclei-templates (smolse), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Deserialization of untrusted data in IPC and Parquet readers in PyArrow versions 0.14.0 to 14.0.0 allows arbitrary code execution. An application is vulnerable if it reads Arrow IPC, Feather or Parquet data from untrusted sources (for example user-supplied input files). This vulnerability only affects PyArrow, not other Apache Arrow implementations or bindings. It is recommended that users of PyArrow upgrade to 14.0.1. Similarly, it is recommended that downstream libraries upgrade their dependency requirements to PyArrow 14.0.1 or later. PyPI packages are already available, and we hope that

O3 Security · Impact-Aware SCA

Is CVE-2023-47248 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works