I have read the SECURITY.md. I understand that this repo tracks debian package releases and cannot fix debian CVEs on its own. This CVE shows a fix is available in the appropriate debian version (trixie) and channel (security).
cc-debian13 and python3-debian13 currently ship libssl3t64 3.5.6-1deb13u1. CVE-2026-45447 (HIGH) is fixed in 3.5.6-1deb13u2, which has been available in debian-security for more than 48 hours. Debian Security Tracker: https://security-tracker.debian.org/tracker/CVE-2026-45447
Current index digest observed for gcr.io/distroless/cc-debian13:nonroot: sha256:e1fd250ce83d94603e9887ec991156a6c26905a6b0001039b7a43699018c0733
Please rebuild the debian13 base images to pull the latest security updates.
I have read the SECURITY.md. I understand that this repo tracks debian package releases and cannot fix debian CVEs on its own. This CVE shows a fix is available in the appropriate debian version (trixie) and channel (security).
cc-debian13 and python3-debian13 currently ship libssl3t64 3.5.6-1
deb13u1. CVE-2026-45447 (HIGH) is fixed in 3.5.6-1deb13u2, which has been available in debian-security for more than 48 hours. Debian Security Tracker: https://security-tracker.debian.org/tracker/CVE-2026-45447Current index digest observed for gcr.io/distroless/cc-debian13:nonroot: sha256:e1fd250ce83d94603e9887ec991156a6c26905a6b0001039b7a43699018c0733
Please rebuild the debian13 base images to pull the latest security updates.