InfraScan Cloud

Repository scan

ci-infra

pytorch/ci-infra · branch main · scanned 25 Jun 2026 · 313 resources

COverall
CSecurity
–Reliability · N/A
CCost
509findings · 0 critical, 226 high
$7.30–$41.50estimated savings per month, from the code

High 467

High 264 known vulnerabilities in unknown@unknown (docker:24.0.0-rc.1-dind) Security · 264 CVEs

How to fix

No fixed version of unknown is available yet. Check whether docker:24.0.0-rc.1-dind needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2023-27561 fixed in no fix yet
  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2022-2989 fixed in no fix yet
  • High CVE-2022-2990 fixed in no fix yet
  • High CVE-2022-2995 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2024-25621 fixed in no fix yet
  • High CVE-2024-25621 fixed in no fix yet
  • High CVE-2025-31133 fixed in no fix yet
  • High CVE-2025-31133 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • and 244 more
High 53 known vulnerabilities in openssl@3.0.8-r3 (docker:24.0.0-rc.1-dind) Security · 53 CVEs

How to fix

Update openssl from 3.0.8-r3 to 3.0.19-r0 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.19-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-69419 fixed in 3.0.19-r0
  • High CVE-2025-69419 fixed in 3.0.19-r0
  • High CVE-2023-5363 fixed in 3.0.12-r0
  • High CVE-2023-5363 fixed in 3.0.12-r0
  • High CVE-2024-4741 fixed in 3.0.14-r0
  • High CVE-2024-4741 fixed in 3.0.14-r0
  • High CVE-2024-6119 fixed in 3.0.15-r0
  • High CVE-2024-6119 fixed in 3.0.15-r0
  • High CVE-2025-69420 fixed in 3.0.19-r0
  • High CVE-2025-69420 fixed in 3.0.19-r0
  • High CVE-2025-69421 fixed in 3.0.19-r0
  • High CVE-2025-69421 fixed in 3.0.19-r0
  • High CVE-2025-9230 fixed in 3.0.19-r0
  • High CVE-2025-9230 fixed in 3.0.19-r0
  • High CVE-2025-15467 fixed in 3.0.19-r0
  • High CVE-2025-15467 fixed in 3.0.19-r0
  • High CVE-2024-5535 fixed in 3.0.14-r0
  • High CVE-2024-5535 fixed in 3.0.14-r0
  • Medium CVE-2025-69418 fixed in 3.0.19-r0
  • Medium CVE-2025-69418 fixed in 3.0.19-r0
  • and 33 more
High 51 known vulnerabilities in unknown@unknown (nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless) Security · 51 CVEs

How to fix

No fixed version of unknown is available yet. Check whether nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-39829 fixed in no fix yet
  • High CVE-2026-33186 fixed in no fix yet
  • High CVE-2026-39830 fixed in no fix yet
  • High CVE-2026-39831 fixed in no fix yet
  • High CVE-2026-39832 fixed in no fix yet
  • High CVE-2026-39833 fixed in no fix yet
  • High CVE-2026-39834 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • and 31 more
High 22 known vulnerabilities in unknown@unknown (nvcr.io/nvidia/k8s-device-plugin:v0.19.0) Security · 22 CVEs

How to fix

No fixed version of unknown is available yet. Check whether nvcr.io/nvidia/k8s-device-plugin:v0.19.0 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-33810 fixed in no fix yet
  • High CVE-2026-33186 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • Medium CVE-2026-41579 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • Medium CVE-2026-32288 fixed in no fix yet
  • Medium CVE-2026-25681 fixed in no fix yet
  • Medium CVE-2026-27136 fixed in no fix yet
  • Medium CVE-2026-32289 fixed in no fix yet
  • Medium CVE-2026-39823 fixed in no fix yet
  • Medium CVE-2026-39826 fixed in no fix yet
  • Medium CVE-2026-42502 fixed in no fix yet
  • Medium CVE-2026-42506 fixed in no fix yet
  • Medium CVE-2026-32282 fixed in no fix yet
  • and 2 more
High 16 known vulnerabilities in stdlib@1.19.6 (docker:24.0.0-rc.1-dind) Security · 16 CVEs

How to fix

Update stdlib from 1.19.6 to 1.22.7 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
  • Medium CVE-2025-4673 fixed in 1.23.10
High 15 known vulnerabilities in openssl@3.5.6-r0 (haproxy:3.1-alpine) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in haproxy:3.1-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.5.7-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-34181 fixed in 3.5.7-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 10 known vulnerabilities in stdlib@1.25.5 (nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless) Security · 10 CVEs

How to fix

Update stdlib from 1.25.5 to 1.25.8 or later in nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.25.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • High CVE-2026-42504 fixed in 1.25.11
High 7 known vulnerabilities in openssh@9.1_p1-r2 (docker:24.0.0-rc.1-dind) Security · 7 CVEs

How to fix

No fixed version of openssh is available yet. Check whether docker:24.0.0-rc.1-dind needs openssh at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2023-51767 fixed in no fix yet
  • High CVE-2024-6387 fixed in 9.1_p1-r6
  • High CVE-2023-28531 fixed in 9.1_p1-r3
  • High CVE-2023-38408 fixed in 9.1_p1-r4
  • Medium CVE-2023-51384 fixed in 9.1_p1-r5
  • Medium CVE-2023-48795 fixed in 9.1_p1-r5
  • Medium CVE-2023-51385 fixed in 9.1_p1-r5
High 5 known vulnerabilities in crypto@0.2.0 (docker:24.0.0-rc.1-dind) Security · 5 CVEs

How to fix

Update crypto from 0.2.0 to 0.43.0 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 4 known vulnerabilities in stdlib@1.26.1 (nvcr.io/nvidia/k8s-device-plugin:v0.19.0) Security · 4 CVEs

How to fix

Update stdlib from 1.26.1 to 1.26.3 or later in nvcr.io/nvidia/k8s-device-plugin:v0.19.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33811 fixed in 1.26.3
  • High CVE-2026-39836 fixed in 1.26.3
  • High CVE-2026-42499 fixed in 1.26.3
  • High CVE-2026-42504 fixed in 1.26.4
High 3 known vulnerabilities in krb5@1.20.1-r0 (docker:24.0.0-rc.1-dind) Security · 3 CVEs

How to fix

Update krb5 from 1.20.1-r0 to 1.20.2-r1 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.20.2-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-37370 fixed in 1.20.2-r1
  • High CVE-2024-37371 fixed in 1.20.2-r1
  • Medium CVE-2023-36054 fixed in 1.20.2-r0
High 3 known vulnerabilities in crypto@0.45.0 (nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless) Security · 3 CVEs

How to fix

Update crypto from 0.45.0 to 0.52.0 or later in nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.52.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
High 2 known vulnerabilities in otelhttp@0.29.0 (docker:24.0.0-rc.1-dind) Security · 2 CVEs

How to fix

Update otelhttp from 0.29.0 to 0.44.0 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.44.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-21698 fixed in 0.44.0
  • High CVE-2023-25151 fixed in 0.44.0
High 2 known vulnerabilities in otelhttptrace@0.29.0 (docker:24.0.0-rc.1-dind) Security · 2 CVEs

How to fix

Update otelhttptrace from 0.29.0 to 0.44.0 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.44.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-21698 fixed in 0.44.0
  • High CVE-2023-25151 fixed in 0.44.0
High 2 known vulnerabilities in net@0.48.0 (nvcr.io/nvidia/k8s-device-plugin:v0.19.0) Security · 2 CVEs

How to fix

Update net from 0.48.0 to 0.53.0 or later in nvcr.io/nvidia/k8s-device-plugin:v0.19.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.53.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33814 fixed in 0.53.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 2 known vulnerabilities in net@0.47.0 (nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless) Security · 2 CVEs

How to fix

Update net from 0.47.0 to 0.53.0 or later in nvcr.io/nvidia/k8s/dcgm-exporter:4.5.2-4.8.1-distroless. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.53.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33814 fixed in 0.53.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 2 known vulnerabilities in musl@1.2.4_git20230717-r5 (public.ecr.aws/docker/library/alpine:3.19) Security · 2 CVEs

How to fix

Update musl from 1.2.4_git20230717-r5 to 1.2.4_git20230717-r6 or later in public.ecr.aws/docker/library/alpine:3.19. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.4_git20230717-r6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-40200 fixed in 1.2.4_git20230717-r6
  • Medium CVE-2026-6042 fixed in 1.2.4_git20230717-r6
High 1 known vulnerability in musl@1.2.3-r4 (docker:24.0.0-rc.1-dind) Security · 1 CVE

How to fix

Update musl from 1.2.3-r4 to 1.2.3-r6 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.3-r6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-26519 fixed in 1.2.3-r6
High 1 known vulnerability in ncurses@6.3_p20221119-r0 (docker:24.0.0-rc.1-dind) Security · 1 CVE

How to fix

Update ncurses from 6.3_p20221119-r0 to 6.3_p20221119-r1 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.3_p20221119-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-29491 fixed in 6.3_p20221119-r1
High 1 known vulnerability in openssl@3.1.8-r1 (public.ecr.aws/docker/library/alpine:3.19) Security · 1 CVE

How to fix

No fixed version of openssl is available yet. Check whether public.ecr.aws/docker/library/alpine:3.19 needs openssl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-15467 fixed in no fix yet
High Expensive NAT Gateway Cost · 1 place

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

Medium 24

Medium Missing Cost and Usage Report Cost · 11 places
Medium 4 known vulnerabilities in busybox@1.35.0-r29 (docker:24.0.0-rc.1-dind) Security · 4 CVEs

How to fix

Update busybox from 1.35.0-r29 to 1.35.0-r31 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.35.0-r31); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-42363 fixed in 1.35.0-r31
  • Medium CVE-2023-42364 fixed in 1.35.0-r31
  • Medium CVE-2023-42365 fixed in 1.35.0-r31
  • Medium CVE-2023-42366 fixed in 1.35.0-r30
Medium 3 known vulnerabilities in busybox@1.36.1-r20 (public.ecr.aws/docker/library/alpine:3.19) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether public.ecr.aws/docker/library/alpine:3.19 needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
  • Low CVE-2024-58251 fixed in 1.36.1-r21
  • Low CVE-2025-46394 fixed in 1.36.1-r21
Medium 2 known vulnerabilities in net@0.7.0 (docker:24.0.0-rc.1-dind) Security · 2 CVEs

How to fix

Update net from 0.7.0 to 0.55.0 or later in docker:24.0.0-rc.1-dind. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.55.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-25680 fixed in 0.55.0
  • Medium CVE-2026-25680 fixed in 0.55.0
Medium 1 known vulnerability in linux-pam@1.5.2-r1 (docker:24.0.0-rc.1-dind) Security · 1 CVE

How to fix

No fixed version of linux-pam is available yet. Check whether docker:24.0.0-rc.1-dind needs linux-pam at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2024-22365 fixed in no fix yet
Medium 1 known vulnerability in xz@5.2.9-r0 (docker:24.0.0-rc.1-dind) Security · 1 CVE

How to fix

No fixed version of xz is available yet. Check whether docker:24.0.0-rc.1-dind needs xz at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2024-47611 fixed in no fix yet
Medium 1 known vulnerability in busybox@1.37.0-r30 (haproxy:3.1-alpine) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether haproxy:3.1-alpine needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
Medium 1 known vulnerability in busybox@1.37.0-r14 (public.ecr.aws/docker/library/alpine:3.21) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether public.ecr.aws/docker/library/alpine:3.21 needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet

Low 18

Low Missing AWS Budget Cost · 11 places
Low Large Root Volume Cost · 3 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

Low Unassociated Elastic IP Cost · 2 places

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

Where

Low 1 known vulnerability in shadow@4.13-r0 (docker:24.0.0-rc.1-dind) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether docker:24.0.0-rc.1-dind needs shadow at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2023-29383 fixed in no fix yet
Low 1 known vulnerability in zlib@1.3.1-r0 (public.ecr.aws/docker/library/alpine:3.19) Security · 1 CVE

How to fix

No fixed version of zlib is available yet. Check whether public.ecr.aws/docker/library/alpine:3.19 needs zlib at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2026-27171 fixed in no fix yet

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 25 Jun 2026; it may have changed since.

Scan your own repository

InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.