Repository navigation
[UPDATED] Docker Image Signing: Keyless Signing and Key Rotation #48242
yuneng-berri
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Important
Update, November 15, 2026: we have moved to keyless signing. Starting with
v1.111.0-dev.3, every release is signed with Sigstore keyless signing (GitHub OIDC). There is no signing key any more, socosign verify --keycannot be used with these releases. Use the keyless command below insteadThis applies to every release published from November 15, 2026 on, whatever its version number, including patch releases on older lines. The Helm chart at
ghcr.io/berriai/litellm/chart/litellmis signed the same way. If you pincosign.pubin CI or in an admission policy, add a rule for the identity above before you deploy one of these releasesThis is part of our effort to move away from long-lived credentials. Apart from
v1.107.0(see below), we do not believe the old key or the new key was ever used to sign anything other than our own, uncompromised releasesReleases published earlier keep the signature they were published with:
v1.111.0-dev.3and everything published after itv1.103.8tov1.111.0-dev.2, listed below--keywithcosign.pubat commite82a3c6v1.106.2, listed below--keywithcosign.pubat commit0112e53It went through our release pipeline, so it carries a valid old signature and will pass
cosign verify. The same applies tolatest,main-latestandmain-stablefloating tags if you pulled them between 11:46 and 14:20 UTC on October 21. Digests are in the incident postThe
v1.107.0tag and its digest have been removed from GHCR and Docker Hub. Thev1.107.0-rc.*andv1.107.0-dev.*pre-releases are different images and appear in the lists belowThe October key rotation
We have reason to believe the private half of our old cosign signing key was exposed in the October incident (details). We replaced it with a new key on October 23
New key. It's at commit
e82a3c6, andcosign.pubhas sha256e3fe3e08c44b16407fe0b37c43b4f8b603b3a0f4ee74c29e647bc022d762c2c0Old key. It's at commit
0112e53: https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pubImages signed with the new key
All 54 releases
v1.111.0-dev.1,v1.111.0-dev.2v1.110.0-dev.1,v1.110.0-dev.2,v1.110.0-rc.1,v1.110.0-rc.2,v1.110.0-rc.3v1.109.0,v1.109.0-dev.1,v1.109.0-dev.2,v1.109.0-rc.1,v1.109.1v1.108.0,v1.108.0-rc.1,v1.108.1,v1.108.1-lts,v1.108.2,v1.108.2-lts,v1.108.3,v1.108.3-lts,v1.108.4,v1.108.4-lts,v1.108.5,v1.108.5-lts,v1.108.6,v1.108.6-lts,v1.108.7,v1.108.7-lts,v1.108.8,v1.108.8-lts,v1.108.9,v1.108.9-ltsv1.107.0-rc.3,v1.107.0-rc.4v1.106.3,v1.106.4,v1.106.5,v1.106.6,v1.106.7,v1.106.8,v1.106.9,v1.106.10v1.105.4,v1.105.5,v1.105.6,v1.105.7v1.104.6,v1.104.7,v1.104.8,v1.104.9v1.103.8,v1.103.9,v1.103.10,v1.103.11Images signed with the old key
All 256 releases
v1.107.0-dev.1,v1.107.0-dev.2,v1.107.0-dev.3,v1.107.0-rc.1,v1.107.0-rc.2v1.106.0,v1.106.0-dev.1,v1.106.0-dev.2,v1.106.0-dev.3,v1.106.0-rc.1,v1.106.0-rc.2,v1.106.0-rc.3,v1.106.0-rc.4,v1.106.1,v1.106.2v1.105.0,v1.105.0-dev.1,v1.105.0-dev.2,v1.105.0-rc.1,v1.105.0-rc.2,v1.105.0-rc.3,v1.105.1,v1.105.2,v1.105.3v1.104.0,v1.104.0-dev.1,v1.104.0-dev.2,v1.104.0-rc.1,v1.104.0-rc.2,v1.104.1,v1.104.2,v1.104.3,v1.104.4,v1.104.5v1.103.0,v1.103.0-dev.1,v1.103.0-dev.2,v1.103.0-rc.1,v1.103.1,v1.103.2,v1.103.3,v1.103.4,v1.103.5,v1.103.6,v1.103.7v1.102.0,v1.102.0-dev.1,v1.102.0-dev.2,v1.102.0-rc.1,v1.102.0-rc.2,v1.102.1,v1.102.2,v1.102.3,v1.102.4v1.101.0,v1.101.0-dev.1,v1.101.0-dev.2,v1.101.0-rc.1,v1.101.0-rc.2,v1.101.1,v1.101.2,v1.101.3,v1.101.4,v1.101.5,v1.101.6v1.100.0,v1.100.0-dev.1,v1.100.0-dev.2,v1.100.0-rc.1,v1.100.1,v1.100.2,v1.100.3,v1.100.4,v1.100.5v1.99.0,v1.99.0-dev.1,v1.99.0-dev.2,v1.99.0-rc.1,v1.99.0-rc.2,v1.99.1,v1.99.2,v1.99.3,v1.99.4v1.98.0,v1.98.0-dev.1,v1.98.0-dev.2,v1.98.0-rc.1,v1.98.1v1.97.0,v1.97.0-dev.1,v1.97.0-dev.2,v1.97.0-rc.1,v1.97.1,v1.97.2v1.96.0,v1.96.0-dev.1,v1.96.0-dev.2,v1.96.0-rc.1,v1.96.2v1.95.0,v1.95.0-dev.1,v1.95.0-dev.2,v1.95.0-dev.3,v1.95.0-rc.1,v1.95.0-rc.2,v1.95.0-rc.3,v1.95.1v1.94.0,v1.94.0-dev.1,v1.94.0-dev.2,v1.94.0-dev.3,v1.94.0-rc.1,v1.94.0-rc.2,v1.94.0-rc.3,v1.94.1,v1.94.2,v1.94.3v1.93.0,v1.93.0-dev.1,v1.93.0-dev.2,v1.93.0-dev.3,v1.93.0-rc.1,v1.93.0-rc.2,v1.93.1,v1.93.2v1.92.0,v1.92.0-dev.1,v1.92.0-dev.2,v1.92.0-rc.1,v1.92.0-rc.2,v1.92.1,v1.92.2v1.91.0,v1.91.0-dev.1,v1.91.0-dev.2,v1.91.0-rc.1,v1.91.1,v1.91.2,v1.91.3,v1.91.4,v1.91.5v1.90.0,v1.90.0-rc.1,v1.90.1,v1.90.2,v1.90.3,v1.90.4,v1.90.5,v1.90.6,v1.90.7v1.89.0,v1.89.0-rc.1,v1.89.0-rc.2,v1.89.1,v1.89.2,v1.89.3,v1.89.4,v1.89.5,v1.89.6,v1.89.7v1.88.0,v1.88.0-dev.1,v1.88.0-rc.1,v1.88.0-rc.2,v1.88.0-rc.3,v1.88.1,v1.88.2,v1.88.3,v1.88.4,v1.88.5,v1.88.6v1.87.0,v1.87.0-dev.1,v1.87.0-rc.1,v1.87.0-rc.2,v1.87.1,v1.87.2,v1.87.3,v1.87.4,v1.87.5v1.86.0,v1.86.0-rc.1,v1.86.1,v1.86.2,v1.86.3,v1.86.4,v1.86.5,v1.86.6,v1.86.7v1.85.0,v1.85.0-rc.1,v1.85.0-rc.2,v1.85.1,v1.85.2,v1.85.3,v1.85.4,v1.85.5,v1.85.6,v1.85.7v1.84.0,v1.84.1,v1.84.2,v1.84.3,v1.84.4,v1.84.5,v1.84.6,v1.84.7,v1.84.8,v1.84.9,v1.84.10v1.83.2-nightly,v1.83.3-stable,v1.83.3-stable.opus-4.7,v1.83.3-stable.patch.2,v1.83.3-stable.patch.3,v1.83.3.dev.1,v1.83.3.rc.1,v1.83.5-nightly,v1.83.6-nightly,v1.83.7-stable,v1.83.7-stable.patch.1,v1.83.7.dev.1,v1.83.7.dev.2,v1.83.7.rc.1,v1.83.8-nightly,v1.83.9-nightly,v1.83.10-nightly,v1.83.10-stable,v1.83.10-stable.patch.1,v1.83.10-stable.patch.2,v1.83.10-stable.patch.3,v1.83.10.dev.1,v1.83.10.dev.2,v1.83.10.rc.1,v1.83.10.rc.2,v1.83.11-nightly,v1.83.12-nightly,v1.83.13-nightly,v1.83.14-stable,v1.83.14-stable.patch.1,v1.83.14-stable.patch.2,v1.83.14-stable.patch.3,v1.83.14.dev.1,v1.83.14.dev.2,v1.83.14.rc.1v1.82.0.dev.8,v1.82.3-stable.patch.3,v1.82.3-stable.patch.4,v1.82.3.dev.10,v1.82.3.dev.7,v1.82.3.dev.9,v1.82.6.dev.3,v1.82.6.rc.4v1.81.12-stable.patch.1,v1.81.12-stable.patch.2,v1.81.12-stable.patch.3All reactions