Updating setuptools to patch CVE-2025-47273 #26219
Draft
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
github-actions
bot
added
the
awaiting-review
Author
|
Okay, so I was able to find where this gets generated from — https://github.com/protocolbuffers/protobuf/blob/v29.0/MODULE.bazel#L122 I have filed protocolbuffers/protobuf#22094 to update this in Protobuf. If / when that gets merged, the proper solution would likely be to update the version of Protobuf that is being pinned, which in turn should update the setuptools version in the lock file. |
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.
Updating setuptools to patch CVE-2025-47273.
I manually updated this in the lock file, since it wasn't clear to me how this particular configuration was originally generated. e.g. nothing in https://github.com/bazel-contrib/rules_python is specifically pinning to "70.3.0" .
Let me know if there is a different / better way to make this change.