Add a 'Security considerations' documentation page - #330
Merged
Conversation
Explain that the guards only cover attribute access written in the restricted source, and that providing an __import__ implementation hands the security boundary to the import policy of the calling application.
dataflake
approved these changes
Aug 26, 2026
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
2 participants
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.
Follow-up to a report that
operator.attrgetter/itemgetter/methodcallerre-open thestring.Formatterescape patched in 8.4 (CVE-2026-76825).There is nothing to fix in the code: all of it requires a host-provided
__import__, and any import policy permissive enough to reachoperatoralready allowsimport os. So this documents the boundary instead.— Comment created by Claude