Skip to content

v2.37.1 — three advisories opened minutes after v2.37.0 shipped

Released 2026-09-19. Upgrade:

sudo snap refresh yazses     # snap
pipx upgrade yazses          # or: uv tool upgrade yazses
scoop update yazses          # Windows

A patch release, not a feature one. Pushing v2.37.0 triggered GitHub's Dependabot scan of the updated uv.lock, which surfaced three advisories against anyio 4.14.1 — a transitive dependency pulled in by httpx, mcp, httpcore2 and starlette, all under the opt-in agent extra — one of them critical:

  • CVE-2026-63349 (high) — run_process/open_process can retain a parent process's supplementary groups instead of honouring extra_groups.
  • CVE-2026-63374 (critical) — TLSStream's IDNA 2003 hostname encoding can let a crafted hostname be accepted for the wrong certificate.
  • CVE-2026-64847 (medium) — a process-pool worker can block indefinitely on undrained stderr.

All three are patched upstream in anyio 4.14.2. uv.lock now resolves anyio 4.15.1, the current stable release.

The same scan also re-flagged lightning (CVE-2026-58659) against uv.lock — that one was already patched to lightning>=2.6.6 in v2.37.0; Dependabot had not yet rescanned the lockfile when the alert fired, and it closes on its own.

diskcache (CVE-2025-69872) remains an open advisory with no upstream patch. It was already assessed as unreachable in SECURITY.md before this release, and that assessment is unchanged: diskcache reaches this project only as a transitive dependency of the opt-in llama-cpp-python, and nothing here ever constructs the object that would unpickle a cache file.

Upgrading

Your config, models and learning corpus are untouched.