fix(deps): require XXE-safe lxml - #326
Merged
Merged
Conversation
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.
Fixes #314
What changed
Security evidence
Tether passes user-selected URDF files into yourdfpy.URDF.load from the safety guard and embodiment adapter. With the former locked lxml 6.0.4, an isolated XML probe resolved a local-file external entity. With locked lxml 6.1.2, local_file_resolved=False.
Verification
Lockfile note
The repository lock root metadata is already stale relative to pyproject.toml. A full refresh is independently blocked by current optional-dependency resolution conflicts (ARM64 NumPy/LeRobot, unavailable scservo-sdk registry resolution, and NVIDIA TensorRT placeholder metadata on macOS). This PR keeps #314 narrow and updates only the generated lxml package stanza.