chore(deps): bump idna 3.11 -> 3.17 (fix CVE-2026-45409)#33
Merged
Conversation
Transitive bump via `uv lock --upgrade-package idna`. Patches GHSA-65pc-fj4g-8rjx (idna < 3.15) — `idna.encode()` ran the valid_contexto regex pass on oversized inputs before the length cap, allowing CPU-DoS via crafted strings. No source changes; only uv.lock updated. Closes #25 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
OjusWiZard
approved these changes
May 29, 2026
LOCKhart07
approved these changes
May 29, 2026
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
3 participants
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
idnafrom 3.11 to 3.17 inuv.lockviauv lock --upgrade-package idna.idna.encode()ranvalid_contextovalidation on oversized inputs before the length cap, allowing CPU-DoS via crafted strings (e.g."٠" * N). Fixed in idna 3.15.uv.lockupdated.Why bump rather than dismiss
idnais pulled transitively viarequests,anyio, andyarl(throughopen-autonomy[all]). This repo is a scaffold with no direct callers, so the practical risk here is low. But forks of this template inherit the lockfile and do make HTTP calls (RPC, IPFS) in agent code. Bumping is a one-line lock change with no API impact; dismissing would push the bump onto every downstream fork.Test plan
uv lock --check— lockfile consistent withpyproject.tomluv sync --all-groups— resolves and installs cleanly;idna.__version__ == "3.17"confirmedcheck-dependencies,check-hash,liccheck, py3.10/3.11/3.12 test matrixCloses #25
🤖 Generated with Claude Code