diff --git a/bitnami/jupyterhub/5/debian-12/Dockerfile b/bitnami/jupyterhub/5/debian-12/Dockerfile
index bf00238948d7e..dd9d2e52b93c9 100644
--- a/bitnami/jupyterhub/5/debian-12/Dockerfile
+++ b/bitnami/jupyterhub/5/debian-12/Dockerfile
@@ -8,11 +8,11 @@ ARG TARGETARCH
 
 LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
       org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
-      org.opencontainers.image.created="2024-11-09T21:20:45Z" \
+      org.opencontainers.image.created="2024-11-25T13:11:31Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/jupyterhub/README.md" \
       org.opencontainers.image.licenses="Apache-2.0" \
-      org.opencontainers.image.ref.name="5.2.1-debian-12-r2" \
+      org.opencontainers.image.ref.name="5.2.1-debian-12-r3" \
       org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/jupyterhub" \
       org.opencontainers.image.title="jupyterhub" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -29,8 +29,8 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
 RUN install_packages ca-certificates curl libgcc-s1 libstdc++6 procps zlib1g
 RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
     COMPONENTS=( \
-      "miniforge-24.9.0-1-linux-${OS_ARCH}-debian-12" \
-      "jupyterhub-5.2.1-1-linux-${OS_ARCH}-debian-12" \
+      "miniforge-24.9.2-0-linux-${OS_ARCH}-debian-12" \
+      "jupyterhub-5.2.1-2-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
diff --git a/bitnami/jupyterhub/5/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/jupyterhub/5/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
index b746ae3860760..55baa7d56ffee 100644
--- a/bitnami/jupyterhub/5/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
+++ b/bitnami/jupyterhub/5/debian-12/prebuildfs/opt/bitnami/.bitnami_components.json
@@ -3,12 +3,12 @@
         "arch": "amd64",
         "distro": "debian-12",
         "type": "NAMI",
-        "version": "5.2.1-1"
+        "version": "5.2.1-2"
     },
     "miniforge": {
         "arch": "amd64",
         "distro": "debian-12",
         "type": "NAMI",
-        "version": "24.9.0-1"
+        "version": "24.9.2-0"
     }
 }
\ No newline at end of file
diff --git a/bitnami/jupyterhub/README.md b/bitnami/jupyterhub/README.md
index 99090093e2570..24ed6e0d35de6 100644
--- a/bitnami/jupyterhub/README.md
+++ b/bitnami/jupyterhub/README.md
@@ -24,7 +24,7 @@ Looking to use JupyterHub in production? Try [VMware Tanzu Application Catalog](
 
 ## Supported tags and respective `Dockerfile` links
 
-Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html).
+Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
 
 You can see the equivalence between the different tags by taking a look at the `tags-info.yaml` file present in the branch folder, i.e `bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml`.
 
@@ -54,7 +54,7 @@ docker build -t bitnami/APP:latest .
 
 ## Why use a non-root container?
 
-Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-work-with-non-root-containers-index.html).
+Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
 
 ## Configuration