fix(deps): require anyio>=4.14.2 (GHSA-82r6-8w77-94w6)

[ulziibay-kernel]

Summary

• Mitigates GHSA-82r6-8w77-94w6 / CVE-2026-63374 (critical, CVSS 9.3): AnyIO's IDNA 2003 host name encoding can allow TLS certificate spoofing when a connection is redirected to a malicious server that obtained a cert for the IDNA 2003-encoded form of an internationalized domain.
• Raises the anyio floor to >=4.14.2 (first patched release) for python >= 3.10, via a marker so installs keep working on older interpreters.
• Pins anyio==4.14.2 in requirements.lock and requirements-dev.lock so dev/CI environments are on the patched release and the Socket scan clears.
• Moves .python-version from 3.9.18 to 3.10.16 (required: anyio dropped python 3.9 in 4.13, so the patched pin cannot resolve on 3.9) and bumps the filelock dev pin to 3.32.7 (virtualenv requires filelock>=3.20.1 on python >= 3.10).

Why a marker split

AnyIO 4.13+ requires python >= 3.10, so no patched anyio release can ever install on 3.9. Keeping 3.9 installs working while forcing the patched floor everywhere a fix exists:

• python >= 3.10 resolves anyio >= 4.14.2 (verified: resolves to 4.15.1 on 3.13)
• python < 3.10 keeps the previous >=3.5.0, <5 constraint (resolves to 4.12.1 — unpatchable)

Dropping python 3.9 entirely (as the OpenAI and Anthropic SDKs have done) is the follow-up that closes the remaining gap; it changes the support matrix so it's left as a separate decision.

Testing

• Full suite under python 3.10.16 with the exact locked pins: 758 passed, 3864 skipped
• Pydantic v1 leg (pytest --ignore=tests/functional with pydantic<2): 745 passed
• ruff check, mypy (479 files), pyright --pythonpath .venv/bin/python: all clean
• Built the wheel and verified Requires-Dist markers render correctly
• uv pip compile on 3.9 and 3.13 to confirm both sides of the marker resolve as intended
• Did not run CI's rye sync path locally (rye cannot download its toolchain in this environment); lockfile installability under 3.10.16 was verified with uv pip install -r requirements-dev.lock against the same pins

---

Note

Medium Risk
Dependency-only change in the HTTP/async stack that fixes a critical TLS validation issue on supported Python versions; Python 3.9 installs remain on an unpatchable anyio floor until support is dropped.

Overview
Addresses GHSA-82r6-8w77-94w6 (AnyIO IDNA host encoding / TLS certificate spoofing on redirect) by requiring anyio>=4.14.2 on Python ≥ 3.10, while leaving anyio>=3.5.0 for Python < 3.10 where patched AnyIO cannot install (4.13+ drops 3.9).

Locks anyio==4.14.2 in requirements.lock and requirements-dev.lock, bumps .python-version to 3.10.16 so local/CI resolution matches the patched constraint, and updates filelock in the dev lock for Python 3.10+ virtualenv compatibility.

^{Reviewed by Cursor Bugbot for commit 92535f7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[masnwilliams]

lgtm