Email me

Rust advisories / pyo3

Vulnerability HighRUSTSEC-2026-0176 · pyo3

RUSTSEC-2026-0176: Out-of-bounds read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators

Short answerA security vulnerability in the pyo3 crate: Out-of-bounds read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators. GitHub rates it High. Fixed in 0.29.0: update to a fixed version.

Cratepyo3
TypeVulnerability (memory-exposure)
Affected versionsFrom 0.24.0 before 0.29.0.
Fixed in0.29.0
SeverityHigh (GitHub rating)
Published2026-06-11
Last changed2026-06-13
Also known asGHSA-36hh-v3qg-5jq4
Affected functionspyo3::types::list::BoundListIterator::nth, pyo3::types::list::BoundListIterator::nth_back, pyo3::types::tuple::BoundTupleIterator::nth, pyo3::types::tuple::BoundTupleIterator::nth_back

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

PyO3 0.24.0 added optimized implementations of Iterator::nth and DoubleEndedIterator::nth_back for the BoundListIterator and BoundTupleIterator types. These implementations computed the target index using unchecked usize addition (index + n) before bounds-checking against the sequence length, then read the element via get_item_unchecked.

In nth methods, a sufficiently large n (combined with a non-zero internal index) could cause the addition to overflow and wrap around, producing a small "target index" that passed the bounds check and enabling reads at the front of the list or tuple of elements previously yielded by the iterator.

In nth_back methods, a sufficiently large n could cause underflow in a similar fashion, however would instead allow reads of arbitrary memory past the end of the list or tuple storage.

PyO3 0.29.0 has corrected these methods to use checked arithmetic at the positions which could be at risk of overflow.

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