withdraw [GHSA-29qp-crvh-w22m] github.com/hashicorp/yamux's DefaultConfig has dangerous defaults causing hung Read #5250
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.
Updates
Comments
👋 from HashiCorp Security. The original source of this, GO-2025-3408 , has been withdrawn with context on links below. Please update the GHSA entry accordingly.
(Note that the changes on this PR do not reflect the actual request. Your "advisory feedback form" didn't have a withdrawal option. I'd also be interested to hear if there is automation in place that would have taken care of bringing this update in from Go's vulndb for us.)
refs:
golang/vulndb#3453
https://pkg.go.dev/vuln/GO-2025-3408
hashicorp/yamux#142 (comment)
hashicorp/yamux#143 (comment)