diff --git a/bitnami/trivy/0/debian-12/Dockerfile b/bitnami/trivy/0/debian-12/Dockerfile
index 1837696f79d6..fd9f82869367 100644
--- a/bitnami/trivy/0/debian-12/Dockerfile
+++ b/bitnami/trivy/0/debian-12/Dockerfile
@@ -17,7 +17,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
     DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
     mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
     COMPONENTS=( \
-      "trivy-0.69.2-0-linux-${OS_ARCH}-debian-12" \
+      "trivy-0.69.3-0-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -42,11 +42,11 @@ ARG TARGETARCH
 ENV OS_ARCH="${TARGETARCH:-amd64}"
 
 LABEL org.opencontainers.image.base.name="scratch" \
-      org.opencontainers.image.created="2026-03-02T10:14:55Z" \
+      org.opencontainers.image.created="2026-03-03T13:19:16Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.title="trivy" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
-      org.opencontainers.image.version="0.69.2"
+      org.opencontainers.image.version="0.69.3"
 
 COPY rootfs /
 COPY --from=builder /opt/bitnami/rootfs /
@@ -55,7 +55,7 @@ COPY --from=builder /opt/bitnami/trivy/bin/trivy /opt/bitnami/trivy/bin/trivy
 COPY --from=builder /opt/bitnami/trivy/contrib /opt/bitnami/trivy/contrib
 COPY --from=builder /opt/bitnami/trivy/licenses /opt/bitnami/trivy/licenses
 
-ENV APP_VERSION="0.69.2" \
+ENV APP_VERSION="0.69.3" \
     BITNAMI_APP_NAME="trivy" \
     IMAGE_REVISION="0" \
     PATH="/opt/bitnami/trivy/bin:$PATH"
diff --git a/bitnami/trivy/README.md b/bitnami/trivy/README.md
index c1267704cbc1..8bd9a20dd978 100644
--- a/bitnami/trivy/README.md
+++ b/bitnami/trivy/README.md
@@ -5,13 +5,13 @@
 [Overview of Trivy](https://github.com/aquasecurity/trivy)
 Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
 
-## <a id="tl-dr"></a> TL;DR
+## TL;DR
 
 ```console
 docker run --name trivy bitnami/trivy:latest
 ```
 
-## <a id="why-use-bitnami-secure-images"></a> Why use Bitnami Secure Images?
+## Why use Bitnami Secure Images?
 
 Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
 
@@ -28,11 +28,11 @@ Each image comes with valuable security metadata. You can view the metadata in [
 
 If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy).
 
-## <a id="supported-tags"></a> Supported tags and respective `Dockerfile` links
+## 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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).
 
-## <a id="get-this-image"></a> Get this image
+## Get this image
 
 The recommended way to get the Bitnami trivy Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/trivy).
 
@@ -54,15 +54,15 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
 docker build -t bitnami/APP:latest .
 ```
 
-## <a id="why-non-root"></a> Why use a non-root container?
+## 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://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).
 
-## <a id="configuration"></a> Configuration
+## Configuration
 
 The following section describes how to run commands
 
-### <a id="running-commands"></a> Running commands
+### Running commands
 
 To run Trivy commands inside this container you can use `docker run` since this container uses the `trivy` binary as entrypoint. For example to execute `trivy --version` you can follow the example below:
 
@@ -72,17 +72,17 @@ docker run --rm --name trivy bitnami/trivy:latest --version
 
 Check the [official Trivy documentation](https://github.com/aquasecurity/trivy#usage) for a list of the available parameters.
 
-## <a id="notable-changes"></a> Notable Changes
+## Notable Changes
 
 ### 0.60.0-debian-12-r2
 
 - This image revision dramatically reduces the image given it removes the existing OS distro. Instead, it simply includes the NATS binary on top of a scratch base image.
 
-### <a id="starting-january-16-2024"></a> Starting January 16, 2024
+### Starting January 16, 2024
 
 - The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
 
-## <a id="license"></a> License
+## License
 
 Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.