chole(deps): bump aiohttp to 3.14.3 - #448
Conversation
Clears alerts #63, #64 and #65. aiohttp 3.14.1 is affected by an out-of-bounds heap read in the C HTTP response parser error path on malformed chunked responses, WebSocket clients accepting compressed frames without negotiated permessage-deflate, and request smuggling via WebSocket upgrade. 3.14.3 is the first release patching all three. `runner/pyproject.toml` already allows it via `aiohttp>=3.14.1`, so only the lockfile moves, as a single-package upgrade. The runner declares aiohttp directly but does not import it anywhere in its own source — it is reached through provider SDKs as an HTTP client, which is the direction the response-parser advisory applies to. The full runner suite passes: 1247 passed, 2 skipped. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
callumreid
left a comment
There was a problem hiding this comment.
Approving. Lockfile-only aiohttp 3.14.1 → 3.14.3, matching backend#6437 so the two repos stay on the same version of a security-relevant dependency rather than drifting.
Single file, hashes and wheel URLs regenerated by the resolver rather than hand-edited, green.
Clears alerts #63, #64 and #65 — the same aiohttp advisory trio patched in backend#6437, which surfaced here too.
3.14.3 is the first release patching all three.
Scope
runner/pyproject.tomlalready permits it (aiohttp>=3.14.1), so onlyrunner/uv.lockmoves — 3.14.1 → 3.14.3, resolved as a single-package upgrade with nothing else shifting.The runner declares
aiohttpdirectly but does not import it anywhere in its own source; it is reached through provider SDKs acting as HTTP clients, which is the direction the response-parser advisory applies to.Verification
uv lock --upgrade-package aiohttp→ 3.14.3, single package changeduv sync+import aiohttpconfirms 3.14.3 installedgoogle-stt/google-ttsextras not installed)Not in this PR
benchmarksalso has near-deadline npm alerts in a different manifest — #48sharp(→0.35.0, ~17 days) and #58postcss(→8.5.18, ~19 days), plus #38dompurify. Those are a separate lockfile and a separate change.Co-Authored-By: Claude Opus 5 noreply@anthropic.com
🤖 Generated with Claude Code