How severe is GHSA-pph8-gcv7-4qj5?

No CVSS score has been assigned to GHSA-pph8-gcv7-4qj5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pph8-gcv7-4qj5?

GHSA-pph8-gcv7-4qj5 affects the following packages: pyo3 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-pph8-gcv7-4qj5?

Update pyo3 to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pph8-gcv7-4qj5 is resolved across your whole dependency graph.

How do I detect GHSA-pph8-gcv7-4qj5 in my crates.io dependencies?

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

How do I mitigate GHSA-pph8-gcv7-4qj5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pph8-gcv7-4qj5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pph8-gcv7-4qj5 can be triaged on real exposure rather than presence alone.

Is GHSA-pph8-gcv7-4qj5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pph8-gcv7-4qj5 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-pph8-gcv7-4qj5 published, and has it been updated?

GHSA-pph8-gcv7-4qj5 was published on April 2, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-pph8-gcv7-4qj5 — pyo3

Fix: PyO3/pyo3#5008

GHSA-pph8-gcv7-4qj5 is a remote code execution vulnerability in pyo3. A fix is available for pyo3 — see the affected versions and patch details below.

PyO3 Risk of buffer overflow in `PyString::from_object`

Also known asRUSTSEC-2025-0020

Published

Apr 2, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀pyo3

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

Description

PyString::from_object took &str arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the &str data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow).

In PyO3 0.24.1 this function will now allocate a CString to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes &CStr arguments.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`pyo3`	≥ 0.1.0&&< 0.24.1	0.24.1`cargo update -p pyo3 --precise 0.24.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyo3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pyo3 to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pph8-gcv7-4qj5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pph8-gcv7-4qj5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pph8-gcv7-4qj5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`PyString::from_object` took `&str` arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the `&str` data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow). In PyO3 0.24.1 this function will now allocate a `CString` to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes `&CStr` arguments.

O3 Security · Impact-Aware SCA

Is GHSA-pph8-gcv7-4qj5 in your dependencies?

O3 Security finds GHSA-pph8-gcv7-4qj5 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works