fix(docker): bump wolfi-base digest to patch openssl CVE-2026-34182 by yucheng-berri · Pull Request #31133 · BerriAI/litellm

yucheng-berri · 2026-06-23T22:09:27Z

Relevant issues

Customer image scanners (Wiz) block LiteLLM proxy image imports on CVE-2026-34182 in the base image's openssl: libcrypto3 / libssl3 ship at 3.6.2-r3, fixed in 3.6.3-r0.

Linear ticket

LIT-3961

Pre-Submission checklist

I have added meaningful tests
My PR passes all unit tests on make test-unit
My PR's scope is as isolated as possible; it only solves 1 specific problem
I have requested a Greptile review and received a Confidence Score of at least 4/5 before requesting a maintainer review

Type

Infrastructure

Changes

Re-pins the wolfi-base digest for LITELLM_BUILD_IMAGE and LITELLM_RUNTIME_IMAGE across all six Dockerfiles (root, docker/Dockerfile.database, docker/Dockerfile.non_root, migrations, backend, gateway) from the prior digests (openssl 3.6.2-r3) to the current cgr.dev/chainguard/wolfi-base digest c61ac691... (openssl 3.6.3-r2).

The runtime stage (FROM $LITELLM_RUNTIME_IMAGE AS runtime) is the shipped image, so the runtime digest is what actually resolves the customer-facing CVE; the build image is bumped too for hygiene. Two of the Dockerfiles tracked a second, equally-stale digest; both are unified onto the patched one.

Proof of fix

OpenSSL in each base image, pulled and inspected directly (same official chainguard/wolfi-base repo):

# old digest 31da6565... :  libcrypto3 / libssl3 = 3.6.2-r3   (vulnerable, CVE-2026-34182)
# new digest c61ac691... :  libcrypto3 / libssl3 = 3.6.3-r2   (>= fixed 3.6.3-r0)

3.6.3-r2 satisfies the fixed-version condition (>= 3.6.3-r0), so a customer image scan no longer flags it.

Supply-chain provenance

The new digest is a signed, tamper-evident Chainguard image, verified with cosign:

cosign verify cgr.dev/chainguard/wolfi-base@sha256:c61ac6919b811ea53c4782d69f1fe05218ba3c25d53f01b6ab7892e621bd4370 \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  --certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main
# exit 0 -- transparency-log claim + code-signing certificate verified

Signer is Chainguard's official image-build workflow (keyless/Fulcio via GitHub Actions OIDC), recorded in the public Rekor transparency log (index 1933426039). Together with the immutable digest pin and the openssl version read directly from the image, this establishes the base image is genuine and carries the fix.

CLAassistant · 2026-06-23T22:09:34Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

codecov · 2026-06-23T22:12:52Z

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

yucheng-berri · 2026-06-23T22:19:16Z

@greptileai

greptile-apps · 2026-06-23T22:22:05Z

Greptile Summary

This PR patches CVE-2026-34182 (openssl remote memory corruption) by re-pinning the cgr.dev/chainguard/wolfi-base digest to sha256:c61ac691… (openssl 3.6.3-r2) across all six Dockerfiles, and adds a daily Trivy image-scan workflow to prevent regressions going forward.

All six Dockerfiles (Dockerfile, backend/Dockerfile, gateway/Dockerfile, migrations/Dockerfile, docker/Dockerfile.database, docker/Dockerfile.non_root) are updated to the patched digest; the two that previously tracked a divergent stale digest (sha256:3258be47…) are also unified onto the single patched value.
The new image-scan.yml workflow downloads Trivy v0.71.2 with SHA-256 checksum verification, builds the root image, and fails on any fixable HIGH/CRITICAL CVE in OS or language packages — covering packages (e.g. Prisma's vendored node engine) that lockfile scanners like osv-scan cannot see.

Confidence Score: 5/5

Safe to merge — changes are limited to Dockerfile base-image digest bumps and a new read-only CI workflow with no effect on runtime application code.

Every Dockerfile change is a one-line digest substitution on a well-understood base image, with no logic changes, no dependency graph alterations, and a Trivy scan on the PR branch confirming the patched image is clean. The new workflow uses pinned action SHAs, a checksummed Trivy binary, and minimal (contents: read) permissions — no supply-chain exposure is introduced.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/image-scan.yml	New Trivy-based image scan workflow; pinned checkout and Trivy binary with SHA checksum, minimal permissions, daily schedule plus PR trigger on Dockerfiles and lockfiles.
Dockerfile	Bumps both LITELLM_BUILD_IMAGE and LITELLM_RUNTIME_IMAGE digests from sha256:31da6565… to sha256:c61ac691… (openssl 3.6.3-r2, fixes CVE-2026-34182).
backend/Dockerfile	Same digest bump as root Dockerfile; unified onto the patched sha256:c61ac691… digest.
docker/Dockerfile.database	Previously tracked a divergent digest (sha256:3258be47…); now unified to the patched sha256:c61ac691….
docker/Dockerfile.non_root	Same divergent old digest (sha256:3258be47…) unified to sha256:c61ac691….
gateway/Dockerfile	Digest bumped from sha256:31da6565… to sha256:c61ac691…, in line with other variants.
migrations/Dockerfile	Digest bumped from sha256:31da6565… to sha256:c61ac691…, completing the full fleet update.

_{Reviews (6): Last reviewed commit: "test(ci): expand image-scan to os,librar..." | Re-trigger Greptile}

yucheng-berri · 2026-06-23T22:32:54Z

@greptileai

yucheng-berri · 2026-06-23T22:52:48Z

@greptileai

yucheng-berri · 2026-06-23T23:49:21Z

@greptileai

yucheng-berri · 2026-06-23T23:59:29Z

@greptileai

Re-pins LITELLM_BUILD_IMAGE and LITELLM_RUNTIME_IMAGE across all 6 Dockerfiles from the prior digests (openssl 3.6.2-r3) to the current chainguard wolfi-base digest c61ac691 (openssl 3.6.3-r2, >= the fixed 3.6.3-r0). The runtime stage is the shipped image, so the runtime digest is what actually resolves the customer-facing CVE; the build image is bumped too for hygiene. Two Dockerfiles tracked a second equally-stale digest; both are unified onto the patched one.

…4x-0623 chore(release): backport #30787, #30788, #31035, #31122, #31133 to stable/1.84.x and cut 1.84.10

chore(release): backport #30480, #30787, #30788, #31035, #31133, #31122 to stable/1.85.x and cut 1.85.7

…_cost_0623 chore(release): backport #30787, #30788, #27346, #31035, #31133 to stable/1.87.x

…x-0623 chore(release): backport #30480, #30787, #30788, #31035, #31133 to stable/1.86.x

…8x-0623 chore(release): backport #30787, #30788, #31035, #31133 and relock runtime deps for stable/1.88.x

…x-0624 chore(release): backport #30787, #30788, #31035, #31036, #31122, #31133 to stable/1.89.x (litellm-enterprise 0.1.42.post2)

….4) (#196) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/berriai/litellm](https://images.chainguard.dev/directory/image/wolfi-base/overview) ([source](https://github.com/BerriAI/litellm)) | patch | `v1.89.3` → `v1.89.4` | --- ### Release Notes <details> <summary>BerriAI/litellm (ghcr.io/berriai/litellm)</summary> ### [`v1.89.4`](https://github.com/BerriAI/litellm/releases/tag/v1.89.4) [Compare Source](BerriAI/litellm@v1.89.4...v1.89.4) ##### Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](BerriAI/litellm@0112e53). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.89.4/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` *** ##### What's Changed - chore(release): backport [#31029](BerriAI/litellm#31029) to stable/1.89.x and cut 1.89.4 by [@yuneng-berri](https://github.com/yuneng-berri) in [#31168](BerriAI/litellm#31168) - chore(ui): rebuild dashboard artifacts for stable/1.89.x by [@yuneng-berri](https://github.com/yuneng-berri) in [#31170](BerriAI/litellm#31170) - chore(release): backport [#30787](BerriAI/litellm#30787), [#30788](BerriAI/litellm#30788), [#31035](BerriAI/litellm#31035), [#31036](BerriAI/litellm#31036), [#31122](BerriAI/litellm#31122), [#31133](BerriAI/litellm#31133) to stable/1.89.x (litellm-enterprise 0.1.42.post2) by [@yuneng-berri](https://github.com/yuneng-berri) in [#31259](BerriAI/litellm#31259) **Full Changelog**: <BerriAI/litellm@v1.89.3...v1.89.4> ### [`v1.89.4`](https://github.com/BerriAI/litellm/releases/tag/v1.89.4) [Compare Source](BerriAI/litellm@v1.89.3...v1.89.4) ##### Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](BerriAI/litellm@0112e53). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.89.4/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` *** ##### What's Changed - chore(release): backport [#31029](BerriAI/litellm#31029) to stable/1.89.x and cut 1.89.4 by [@yuneng-berri](https://github.com/yuneng-berri) in [#31168](BerriAI/litellm#31168) - chore(ui): rebuild dashboard artifacts for stable/1.89.x by [@yuneng-berri](https://github.com/yuneng-berri) in [#31170](BerriAI/litellm#31170) - chore(release): backport [#30787](BerriAI/litellm#30787), [#30788](BerriAI/litellm#30788), [#31035](BerriAI/litellm#31035), [#31036](BerriAI/litellm#31036), [#31122](BerriAI/litellm#31122), [#31133](BerriAI/litellm#31133) to stable/1.89.x (litellm-enterprise 0.1.42.post2) by [@yuneng-berri](https://github.com/yuneng-berri) in [#31259](BerriAI/litellm#31259) **Full Changelog**: <BerriAI/litellm@v1.89.3...v1.89.4> </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/London) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).  Reviewed-on: https://forgejo.hayden.moe/hayden/phoebe/pulls/196

….4) (#386) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/berriai/litellm](https://images.chainguard.dev/directory/image/wolfi-base/overview) ([source](https://github.com/BerriAI/litellm)) | patch | `v1.89.3` → `v1.89.4` | --- ### Release Notes <details> <summary>BerriAI/litellm (ghcr.io/berriai/litellm)</summary> ### [`v1.89.4`](https://github.com/BerriAI/litellm/releases/tag/v1.89.4) [Compare Source](BerriAI/litellm@v1.89.4...v1.89.4) ##### Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](BerriAI/litellm@0112e53). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.89.4/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` *** ##### What's Changed - chore(release): backport [#31029](BerriAI/litellm#31029) to stable/1.89.x and cut 1.89.4 by [@yuneng-berri](https://github.com/yuneng-berri) in [#31168](BerriAI/litellm#31168) - chore(ui): rebuild dashboard artifacts for stable/1.89.x by [@yuneng-berri](https://github.com/yuneng-berri) in [#31170](BerriAI/litellm#31170) - chore(release): backport [#30787](BerriAI/litellm#30787), [#30788](BerriAI/litellm#30788), [#31035](BerriAI/litellm#31035), [#31036](BerriAI/litellm#31036), [#31122](BerriAI/litellm#31122), [#31133](BerriAI/litellm#31133) to stable/1.89.x (litellm-enterprise 0.1.42.post2) by [@yuneng-berri](https://github.com/yuneng-berri) in [#31259](BerriAI/litellm#31259) **Full Changelog**: <BerriAI/litellm@v1.89.3...v1.89.4> ### [`v1.89.4`](https://github.com/BerriAI/litellm/releases/tag/v1.89.4) [Compare Source](BerriAI/litellm@v1.89.3...v1.89.4) ##### Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](BerriAI/litellm@0112e53). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.89.4/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` *** ##### What's Changed - chore(release): backport [#31029](BerriAI/litellm#31029) to stable/1.89.x and cut 1.89.4 by [@yuneng-berri](https://github.com/yuneng-berri) in [#31168](BerriAI/litellm#31168) - chore(ui): rebuild dashboard artifacts for stable/1.89.x by [@yuneng-berri](https://github.com/yuneng-berri) in [#31170](BerriAI/litellm#31170) - chore(release): backport [#30787](BerriAI/litellm#30787), [#30788](BerriAI/litellm#30788), [#31035](BerriAI/litellm#31035), [#31036](BerriAI/litellm#31036), [#31122](BerriAI/litellm#31122), [#31133](BerriAI/litellm#31133) to stable/1.89.x (litellm-enterprise 0.1.42.post2) by [@yuneng-berri](https://github.com/yuneng-berri) in [#31259](BerriAI/litellm#31259) **Full Changelog**: <BerriAI/litellm@v1.89.3...v1.89.4> </details> --- ### Configuration 📅 **Schedule**: (in timezone America/New_York) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.greyrock.io/greyrock-labs/home-ops/pulls/386

…erriAI#31133) Re-pins LITELLM_BUILD_IMAGE and LITELLM_RUNTIME_IMAGE across all 6 Dockerfiles from the prior digests (openssl 3.6.2-r3) to the current chainguard wolfi-base digest c61ac691 (openssl 3.6.3-r2, >= the fixed 3.6.3-r0). The runtime stage is the shipped image, so the runtime digest is what actually resolves the customer-facing CVE; the build image is bumped too for hygiene. Two Dockerfiles tracked a second equally-stale digest; both are unified onto the patched one. (cherry picked from commit fda08dd)

…to v1.89.4 (#228) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [https://github.com/BerriAI/litellm.git](https://github.com/BerriAI/litellm) | patch | `v1.89.3` → `v1.89.4` | --- ### Release Notes <details> <summary>BerriAI/litellm (https://github.com/BerriAI/litellm.git)</summary> ### [`v1.89.4`](https://github.com/BerriAI/litellm/releases/tag/v1.89.4) [Compare Source](BerriAI/litellm@v1.89.3...v1.89.4) #### Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](BerriAI/litellm@0112e53). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.89.4/cosign.pub \ ghcr.io/berriai/litellm:v1.89.4 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` *** #### What's Changed - chore(release): backport [#31029](BerriAI/litellm#31029) to stable/1.89.x and cut 1.89.4 by [@yuneng-berri](https://github.com/yuneng-berri) in [#31168](BerriAI/litellm#31168) - chore(ui): rebuild dashboard artifacts for stable/1.89.x by [@yuneng-berri](https://github.com/yuneng-berri) in [#31170](BerriAI/litellm#31170) - chore(release): backport [#30787](BerriAI/litellm#30787), [#30788](BerriAI/litellm#30788), [#31035](BerriAI/litellm#31035), [#31036](BerriAI/litellm#31036), [#31122](BerriAI/litellm#31122), [#31133](BerriAI/litellm#31133) to stable/1.89.x (litellm-enterprise 0.1.42.post2) by [@yuneng-berri](https://github.com/yuneng-berri) in [#31259](BerriAI/litellm#31259) **Full Changelog**: <BerriAI/litellm@v1.89.3...v1.89.4> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).  Co-authored-by: Renovate Bot <renovate@bhamm-lab.com> Reviewed-on: https://codeberg.org/blake-hamm/bhamm-lab/pulls/228

…erriAI#31133) Re-pins LITELLM_BUILD_IMAGE and LITELLM_RUNTIME_IMAGE across all 6 Dockerfiles from the prior digests (openssl 3.6.2-r3) to the current chainguard wolfi-base digest c61ac691 (openssl 3.6.3-r2, >= the fixed 3.6.3-r0). The runtime stage is the shipped image, so the runtime digest is what actually resolves the customer-facing CVE; the build image is bumped too for hygiene. Two Dockerfiles tracked a second equally-stale digest; both are unified onto the patched one. (cherry picked from commit fda08dd)

Refresh the pinned cgr.dev/chainguard/wolfi-base digest from c61ac6 to 42df77a9 (current wolfi-base:latest, a multi-arch index covering amd64 and arm64). This advances the glibc family from 2.43-r8 to 2.43-r10, with libcrypto3 and libssl3 from 3.6.3-r2 to r3 and libgcc from 16.1.0-r2 to r4; no packages are added or removed. The image scan reports CVE-2026-6791 against glibc 2.43-r8 (fixed in r10). The glibc subpackages are exact-version pinned, so the in-Dockerfile apk upgrade cannot advance them past the base's baked revision, which is why refreshing the digest is required. Same six Dockerfiles as BerriAI#31133

greptile-apps Bot reviewed Jun 23, 2026

View reviewed changes

Comment thread .github/workflows/image-scan.yml Outdated

Comment thread .github/workflows/image-scan.yml Outdated

yucheng-berri force-pushed the litellm_openssl_base_image_bump branch from 1a7577f to 01d0025 Compare June 23, 2026 23:37

yucheng-berri marked this pull request as ready for review June 23, 2026 23:55

yucheng-berri requested a review from a team June 23, 2026 23:55

yucheng-berri requested a review from yuneng-berri June 24, 2026 00:03

yucheng-berri force-pushed the litellm_openssl_base_image_bump branch from 889cc61 to 4d91d95 Compare June 24, 2026 00:26

yucheng-berri changed the title ~~fix(docker): bump wolfi-base to patch openssl CVE-2026-34182~~ fix(docker): bump wolfi-base digest to patch openssl CVE-2026-34182 Jun 24, 2026

yuneng-berri approved these changes Jun 24, 2026

View reviewed changes

yuneng-berri merged commit fda08dd into litellm_internal_staging Jun 24, 2026
124 checks passed

yuneng-berri deleted the litellm_openssl_base_image_bump branch June 24, 2026 00:51

yucheng-berri mentioned this pull request Jun 24, 2026

ci(image-scan): add Grype image scan for OS + library CVEs #31151

Merged

4 tasks

yuneng-berri mentioned this pull request Jun 24, 2026

chore(release): backport #30787, #30788, #31035, #31122, #31133 to stable/1.84.x and cut 1.84.10 #31169

Merged

yuneng-berri added a commit that referenced this pull request Jun 24, 2026

Merge pull request #31169 from BerriAI/litellm_backport_1_84_x_bp-1.8…

2b7dad2

…4x-0623 chore(release): backport #30787, #30788, #31035, #31122, #31133 to stable/1.84.x and cut 1.84.10

This was referenced Jun 24, 2026

chore(release): backport #30480, #30787, #30788, #31035, #31133, #31122 to stable/1.85.x and cut 1.85.7 #31173

Merged

chore(release): backport #30787, #30788, #31035, #31133 and relock runtime deps for stable/1.88.x #31174

Merged

yuneng-berri added a commit that referenced this pull request Jun 24, 2026

Merge pull request #31173 from BerriAI/litellm_backport_1_85_x_0623

f8a102e

chore(release): backport #30480, #30787, #30788, #31035, #31133, #31122 to stable/1.85.x and cut 1.85.7

yucheng-berri mentioned this pull request Jun 24, 2026

[TEST DO NOT MERGE] image-scan gate live test: vulnerable wolfi base #31176

Closed

yuneng-berri mentioned this pull request Jun 24, 2026

chore(release): backport #30480, #30787, #30788, #31035, #31133 to stable/1.86.x #31180

Merged

yuneng-berri added a commit that referenced this pull request Jun 24, 2026

Merge pull request #31177 from BerriAI/litellm_backport_1_87_x_stream…

6dc995d

…_cost_0623 chore(release): backport #30787, #30788, #27346, #31035, #31133 to stable/1.87.x

yuneng-berri added a commit that referenced this pull request Jun 24, 2026

Merge pull request #31180 from BerriAI/litellm_backport_1_86_x_bp-186…

042ece9

…x-0623 chore(release): backport #30480, #30787, #30788, #31035, #31133 to stable/1.86.x

yuneng-berri added a commit that referenced this pull request Jun 24, 2026

Merge pull request #31174 from BerriAI/litellm_backport_1_88_x_bp-1.8…

50b3354

…8x-0623 chore(release): backport #30787, #30788, #31035, #31133 and relock runtime deps for stable/1.88.x

yucheng-berri mentioned this pull request Jun 24, 2026

[TEST DO NOT MERGE] image-scan live test on cleaned head (#31151) #31244

Closed

ishaan-berri mentioned this pull request Jun 25, 2026

LiteLLM Stability Sprint Roadmap #30484

Open

13 tasks

yuneng-berri mentioned this pull request Jun 25, 2026

chore(release): backport #30787, #30788, #31035, #31036, #31122, #31133 to stable/1.89.x (litellm-enterprise 0.1.42.post2) #31259

Merged

4 tasks

yuneng-berri added a commit that referenced this pull request Jun 25, 2026

Merge pull request #31259 from BerriAI/litellm_backport_1_89_x_bp-189…

7f77969

…x-0624 chore(release): backport #30787, #30788, #31035, #31036, #31122, #31133 to stable/1.89.x (litellm-enterprise 0.1.42.post2)

claude Bot mentioned this pull request Jun 25, 2026

fix(container): update image ghcr.io/berriai/litellm-non_root (v1.89.3 ➔ v1.89.4) drag0n141/home-ops#6535

Merged

1 task

yuneng-berri mentioned this pull request Jul 6, 2026

fix(docker): bump wolfi-base digest for glibc 2.43-r10 #32277

Merged

4 tasks

Navigation Menu

Uh oh!

Uh oh!

fix(docker): bump wolfi-base digest to patch openssl CVE-2026-34182 - #31133

fix(docker): bump wolfi-base digest to patch openssl CVE-2026-34182#31133
yuneng-berri merged 1 commit into
litellm_internal_stagingfrom
litellm_openssl_base_image_bump

yucheng-berri commented Jun 23, 2026 •

edited

Loading

Uh oh!

CLAassistant commented Jun 23, 2026

Uh oh!

codecov Bot commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

greptile-apps Bot commented Jun 23, 2026 •

edited

Loading

Important Files Changed

Uh oh!

Uh oh!

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

yucheng-berri commented Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Relevant issues

Linear ticket

Pre-Submission checklist

Type

Changes

Proof of fix

Supply-chain provenance

Uh oh!

CLAassistant commented Jun 23, 2026

Uh oh!

codecov Bot commented Jun 23, 2026

Codecov Report

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

greptile-apps Bot commented Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Uh oh!

Uh oh!

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

yucheng-berri commented Jun 23, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

yucheng-berri commented Jun 23, 2026 •

edited

Loading

greptile-apps Bot commented Jun 23, 2026 •

edited

Loading