How severe is GHSA-x563-6hqv-26mr?

No CVSS score has been assigned to GHSA-x563-6hqv-26mr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x563-6hqv-26mr?

GHSA-x563-6hqv-26mr affects the following packages: ibis-framework (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-x563-6hqv-26mr?

Update ibis-framework to 7.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x563-6hqv-26mr is resolved across your whole dependency graph.

How do I detect GHSA-x563-6hqv-26mr in my PyPI dependencies?

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

How do I mitigate GHSA-x563-6hqv-26mr 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 GHSA-x563-6hqv-26mr actively exploited in the wild?

No public exploit code has been indexed for GHSA-x563-6hqv-26mr 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.

When was GHSA-x563-6hqv-26mr published, and has it been updated?

GHSA-x563-6hqv-26mr was published on November 17, 2023 and was last updated on November 30, 2024. 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

Ibis PyArrow dependency allows arbitrary code execution when loading a malicious data fileGHSA-x563-6hqv-26mr

Fix: ibis-project/ibis@0fa1e5d

GHSA-x563-6hqv-26mr is a remote code execution vulnerability in ibis-framework. A fix is available for ibis-framework — see the affected versions and patch details below.

Published

Nov 17, 2023

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍ibis-framework

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

Impact

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.

Note that Ibis itself makes extremely limited use of pyarrow.parquet.read_table:

read_table is used in tests, where the input file is entirely controlled by the Ibis developers
read_table is used in the ibis/examples/__init__.py as a fallback for backends that don't support reading Parquet directly. Parquet data used in ibis.examples are also managed by the Ibis developers. This Parquet data is generated from CSV files and SQLite databases.
The Pandas and Dask backends both use PyArrow to read Parquet files and are therefore affected.

Ibis does not make use of APIs that directly read from either Arrow IPC files or Feather files.

Patches

Ibis imports the pyarrow_hotfix package wherever pyarrow is used, as of version 7.1.0.

Upgrading to Arrow 14.0.1 is also a possible solution, starting in Ibis 7.1.0.

Workarounds

Install pyarrow_hotfix and run import pyarrow_hotfix ahead of any and all import ibis statements.

For example:

import ibis

becomes

import pyarrow_hotfix
import ibis

References

https://www.cve.org/CVERecord?id=CVE-2023-47248 https://nvd.nist.gov/vuln/detail/CVE-2023-47248

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ibis-framework`	all versions	7.1.0`pip install --upgrade 'ibis-framework==7.1.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibis-framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibis-framework to 7.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x563-6hqv-26mr 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.

Frequently Asked Questions

### Impact 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. Note that Ibis itself makes **extremely limited** use of `pyarrow.parquet.read_table`: 1. `read_table` is used in tests, where the input file is entirely controlled by the Ibis developers 2. `read_table` is used in the `ib

O3 Security · Impact-Aware SCA

Is GHSA-x563-6hqv-26mr in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works