Advisory

GHSA-chgr-c6px-7xpp

Also known as: RUSTSEC-2026-0177

Summary

PyO3 has a missing Sync bound on PyCFunction::new_closure closures

Details

PyCFunction::new_closure (and the temporary new_closure_bound complement in the 0.21–0.22 series) required the supplied closure to be Send + 'static but not Sync. The resulting PyCFunction is a Python callable that can be invoked from any Python thread, which means the closure may be called concurrently from multiple threads, and needs a Sync bound to prevent possible data races.

The problem exists under all Python versions but is particularly vulnerable under the newer free-threaded Python variant, which do not have serial execution imposed by the Global Interpreter Lock. Under releases protected by the GIL, the ability to "detach" from the Python interpreter temporarily inside the closure (e.g. by Python::detach) makes it possible for interleaved and/or concurrent execution of various portions of the closure.

PyO3 0.29.0 added a Sync bound to close this thread-safety bug.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-12 20:09 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

pyo3

crates.io · All systems

Affected

  • introduced 0, fixed 0.29.0 (semver)

Fixed versions

0.29.0

Fix

  • Fixed version 0.29.0
    cargo update -p pyo3 --precise 0.29.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences