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
1 participant
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.
Description
CVE patch for HIGH CVE-2026-61544 (GHSA-5hq8-qhww-jm7q): remote panic in
libp2p-quicvia a certificate-expiry race during QUIC handshake. Companion forward-port of #152 so the fix is not lost when thekaleido-node-op-rethpin advances fromrelease-op-reth/v2.2.0tov2.2.3.Details
libp2p-quic0.13.00.13.1Same lockfile-only change as #152:
cargo update -p libp2p-quic --precise 0.13.1inrust/.libp2p 0.56.0constrainslibp2p-quic ^0.13.0, so 0.13.1 is the compatible patched release.The shipping image currently builds
release-op-reth/v2.2.0(#152). This PR is the forward-port only.