litellm/backend
Yuneng Jiang 2fecf995f0
chore(deps): bump pypdf, pyasn1 and the wolfi base pin on 1.91.x
Lock-only for the Python side. pypdf 6.13.3 -> 6.14.2 stays inside the
existing >=6.12.0,<7.0 constraint and pyasn1 0.6.3 -> 0.6.4 is
transitive, so pyproject.toml is unchanged. Resolution moved those two
packages and nothing else.

The wolfi-base pin moves c61ac691 -> 02dab76b across all six
Dockerfiles, two ARG lines each. That base ships glibc 2.43-r11 in
place of 2.43-r8, which is what clears CVE-2026-6791 on glibc,
glibc-locale-posix, ld-linux and libcrypt1. The runtime stage's
apk upgrade cannot do this: no configured repository offers glibc, so
the revision is fixed by whichever base digest is pinned.

The new digest was verified with cosign against the chainguard-images
release workflow identity before pinning.

Covered CVEs: CVE-2026-59935 / 59936 / 59937 / 59938 (pypdf),
CVE-2026-59884 / 59885 / 59886 (pyasn1), CVE-2026-6791 (glibc).
2026-07-21 13:24:07 -07:00
..
routes feat(proxy): add POST /v1/callbacks/logs to replay logging payloads through callbacks (#31134) 2026-06-24 15:25:10 -07:00
Dockerfile chore(deps): bump pypdf, pyasn1 and the wolfi base pin on 1.91.x 2026-07-21 13:24:07 -07:00
main.py chore(oss): litellm oss staging 120626 (#30292) 2026-06-12 09:49:25 -07:00