fix: resolve CVE-2025-21614 vulnerability in CLI #5653
+18
−18
Conversation
This file contains 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
j-luong
force-pushed
the
fix/CVE-2025-21614
branch
2 times, most recently
from
0e5188e to
a431888
Compare
As a result of this change within goproxy elazarl/goproxy@a4e2f5c Is this failure a result of our test fixture, or does it represent a more significant regression that affects legitimate user scenarios?
thisislawatts
force-pushed
the
fix/CVE-2025-21614
branch
from
a9a3281 to
8e834fe
Compare
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.
Pull Request Submission Checklist
What does this PR do?
Where should the reviewer start?
How should this be manually tested?