diff --git a/docs/my-website/blog/security_townhall_updates/index.md b/docs/my-website/blog/security_townhall_updates/index.md
index 5f5f1954f33..633e97df3e7 100644
--- a/docs/my-website/blog/security_townhall_updates/index.md
+++ b/docs/my-website/blog/security_townhall_updates/index.md
@@ -143,11 +143,11 @@ This will ensure, your releases are safe, even when:
 - Tampered registry artifacts are published
 - Tag mutations are made after the release is published
 
-We believe that [Cosign](https://github.com/sigstore/cosign) is a good fit for this, and have already begun working on it [PR](https://github.com/BerriAI/litellm/pull/24683).
+We believe that [Cosign](https://github.com/sigstore/cosign) is a good fit for this, and have shipped it in [PR #24683](https://github.com/BerriAI/litellm/pull/24683).
 
 #### How to verify a Docker image with Cosign
 
-All LiteLLM Docker images are now signed with [cosign](https://docs.sigstore.dev/cosign/overview/). To verify the integrity of an image before deploying:
+Starting from `v1.83.0-nightly`, all LiteLLM Docker images published to GHCR are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). To verify the integrity of an image before deploying:
 
 ```bash
 cosign verify \
diff --git a/docs/my-website/blog/security_update_march_2026/index.md b/docs/my-website/blog/security_update_march_2026/index.md
index a175b59829b..628e26f0c65 100644
--- a/docs/my-website/blog/security_update_march_2026/index.md
+++ b/docs/my-website/blog/security_update_march_2026/index.md
@@ -710,7 +710,7 @@ The LiteLLM AI Gateway team has already taken the following steps:
 
 ## Verify Docker image signatures
 
-All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). To verify the integrity of an image before deploying:
+Starting from `v1.83.0-nightly`, all LiteLLM Docker images published to GHCR are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). To verify the integrity of an image before deploying:
 
 ```bash
 cosign verify \