Bump aiohttp to 3.13.5 in lockfile (CVE-2026-22815)#630
Merged
Conversation
Fixes Dependabot alert #65: aiohttp <= 3.13.3 allows unlimited trailer headers, leading to possible uncapped memory usage.
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
aiohttpfrom 3.13.3 to 3.13.5 inuv.lockTest plan
Note
Low Risk
Lockfile-only dependency bump; runtime behavior changes are limited to
aiohttppatch updates, with low risk aside from potential upstream regressions.Overview
Updates the
uv.lockpinnedaiohttpversion from3.13.3to3.13.5, refreshing the associated sdist/wheel hashes and artifacts.No application code changes; this is a dependency lock update intended to pick up the patched
aiohttprelease (CVE-related).Written by Cursor Bugbot for commit 9b6efce. This will update automatically on new commits. Configure here.