Upgrade quinn-proto and PyJWT to fix security vulnerabilities#218
Merged
Upgrade quinn-proto and PyJWT to fix security vulnerabilities#218
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.
Summary
quinn-protofrom 0.11.13 to 0.11.14 inCargo.lockto fix an unauthenticated remote DoS via panic in QUIC transport parameter parsing (GHSA-6xvm-j4wr-6v98 / CVE-2026-31812)PyJWTfrom 2.11.0 to 2.12.1 inuv.lockto fix acceptance of unknowncritheader extensions that could bypass JWT validation (GHSA-752w-5fwx-jx9f / CVE-2026-32597)Both are transitive lockfile-only changes.
Cargo.tomlandpyproject.tomlare unchanged.Test plan
cargo testpasses (all Rust tests green)uv run pytest tests/ -vpasses (53 Python tests)make build,make checkpass