Report memory exposure in PyO3 nth_back iterator methods#2958
Merged
Conversation
nth_back iterator methodsnth_back iterator methods
This was referenced Jun 11, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Affected crate(s)
pyo3(40M recent downloads per crates.io)Links to upstream issue(s) or PR(s)
PyO3/pyo3#6086
Severity
Code that uses
BoundListIteratorandBoundTupleIterator'snth_backmethods with attacker-controlled N are vulnerable to out-of-bound reads if the iterators have already yielded items.My assessment is that this is a relatively niche iterator method with a couple of conditions to make it a problem, but code meeting the vulnerable combination could easily go undetected and deserves both a fix and an advisory.
Checklist
RUSTSEC-0000-0000as the IDdatefield is set to the public disclosure date