Repository navigation
chore(deps): bump anyio 4.13.0 to 4.14.2 (CVE-2026-63374) - #6
Merged
Merged
Conversation
## Summary Bumps the transitive `anyio` dependency in `uv.lock` from **4.13.0** to **4.14.2**, the first release carrying the fix for **CVE-2026-63374** (CVSS 9.3): TLSStream's IDNA 2003 host-name encoding left a certificate-spoofing window. `anyio` comes in through `httpx`, so this touches the generated client's transport stack. ## Change `uv lock --upgrade-package anyio==4.14.2` - only the `anyio` entries change (version plus sdist and wheel URL/hash). The unrelated `zipp` marker churn that `uv` also produced was reverted, so the diff is a single package bump. ## Verification (on top of current `main`, pyproject 0.128.37) - `uv sync --frozen --python 3.11` -> `anyio 4.14.2` installed - `uv run ruff check src/ tests/` -> All checks passed - `uv run ruff format --check src/ tests/` -> 283 files already formatted - `uv run mypy src/ tests/` -> Success: no issues found in 283 source files - `uv run pytest -q` -> **58 passed, 1 skipped** (the skip is the pre-existing openapi.yaml-absent smoke check) - `uv lock --check` -> consistent No source changes and no API surface change. Note: the `build wheel + sdist` job fails on the openapi.yaml-vs-pyproject version check. That is pre-existing and unrelated - current `main` (pyproject `0.128.37`) already fails it because upstream `openapi.yaml` is now `0.128.41`. The `lint + mypy + pytest` matrix passes.
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
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
Bumps the transitive
anyiodependency inuv.lockfrom 4.13.0 to 4.14.2, the first releasecarrying the fix for CVE-2026-63374 (CVSS 9.3): TLSStream's IDNA 2003 host-name encoding left a
certificate-spoofing window.
anyiocomes in throughhttpx, so this touches the generated client's transport stack.Change
uv lock --upgrade-package anyio==4.14.2- only theanyioentries change (version plus sdist and wheelURL/hash). The unrelated
zippmarker churn thatuvalso produced was reverted, so the diff is a singlepackage bump.
Verification (on top of current
main, pyproject 0.128.37)uv sync --frozen --python 3.11->anyio 4.14.2installeduv run ruff check src/ tests/-> All checks passeduv run ruff format --check src/ tests/-> 283 files already formatteduv run mypy src/ tests/-> Success: no issues found in 283 source filesuv run pytest -q-> 58 passed, 1 skipped (the skip is the pre-existing openapi.yaml-absent smoke check)uv lock --check-> consistentNo source changes and no API surface change.
Note: the
build wheel + sdistjob fails on the openapi.yaml-vs-pyproject version check. That ispre-existing and unrelated - current
main(pyproject0.128.37) already fails it because upstreamopenapi.yamlis now0.128.41. Thelint + mypy + pytestmatrix passes.