Email me

Rust advisories / pyo3

Vulnerability MediumRUSTSEC-2026-0177 · pyo3

RUSTSEC-2026-0177: Missing `Sync` bound on `PyCFunction::new_closure` closures

Short answerA security vulnerability in the pyo3 crate: Missing `Sync` bound on `PyCFunction::new_closure` closures. GitHub rates it Medium. Fixed in 0.29.0: update to a fixed version.

Cratepyo3
TypeVulnerability (thread-safety)
Affected versionsBefore 0.29.0.
Fixed in0.29.0
SeverityMedium (GitHub rating)
Published2026-06-11
Last changed2026-06-13
Also known asGHSA-chgr-c6px-7xpp
Affected functionspyo3::types::PyCFunction::new_closure, pyo3::types::PyCFunction::new_closure_bound

What to do

  1. See which version you have: cargo tree -i pyo3 (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p pyo3. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example pyo3 = "0.29.0") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

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.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for pyo3

Full security history of pyo3

Up next

Same cratepyo3: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ