fix: ensure Python 3.11.13 is used to address GHSA-4xh5-x5gv-qwph#1197
Merged
Conversation
Signed-off-by: behnazh-w <behnaz.hassanshahi@oracle.com>
nicallen
approved these changes
Oct 1, 2025
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.
Summary
This PR ensures Python
3.11.13is used to mitigate the vulnerability identified in GHSA-4xh5-x5gv-qwph, as this version is not affected by the CVE.Description of changes
3.11.13is used to avoid the vulnerability associated withGHSA-4xh5-x5gv-qwph. Since Python3.11.13is not vulnerable, the changes are intended to avoid unnecessary issues related to the advisory.Related links: