Skip to content

fix(deps): bump aiohttp to 3.14.4 for three security advisories - #428

Merged
spalen0 merged 1 commit into
mainfrom
fix/aiohttp-3.14.4
Oct 19, 2026
Merged

spalen0 merged 1 commit into
mainfrom
fix/aiohttp-3.14.4

Conversation

@spalen0

@spalen0 spalen0 commented Oct 19, 2026

Copy link
Copy Markdown
Collaborator

Why

CI's audit job (uv audit) started failing on aiohttp 3.14.3, which pyproject.toml pins directly. main pins the same version, so its next run will fail too; it surfaced on #427. Three advisories were published, all fixed in 3.14.4:

Change

aiohttp==3.14.3 → 3.14.4 in pyproject.toml, and uv lock --upgrade-package aiohttp. No other package changes in uv.lock.

Verification

  • uv audit --preview-features audit-command: no known vulnerabilities.
  • prek run --all-files passes, and uv run pytest tests/ passes. The 4 TestSafeApiQuota tests fail only locally, when a real SAFE_API_KEY is in .env; they fail the same way on main.

🤖 Generated with Claude Code

uv audit now fails CI on aiohttp 3.14.3:
- GHSA-494j-54xm-rwp3: Secure attribute not enforced for a shared cookie
- GHSA-5wr8-gcqf-gqf3: server lacks an initial request/header timeout
- GHSA-2g87-pp6c-29x5: excessive or unbounded memory/CPU use

All three are fixed in 3.14.4. Only aiohttp changes in the lockfile.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@spalen0
spalen0 merged commit 6a5fa53 into main Oct 19, 2026
3 checks passed
@spalen0
spalen0 deleted the fix/aiohttp-3.14.4 branch October 19, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant