InfraScan Cloud

Repository scan

docker-deployment

dhis2/docker-deployment · branch master · scanned 23 Apr 2026

COverall
FSecurity
–Reliability · N/A
ACost
1,392findings · 0 critical, 470 high
—no cost findings with a savings estimate

High 1,014

High 90 known vulnerabilities in stdlib@1.18.2 (postgis/postgis:16-master) Security · 90 CVEs

How to fix

Update stdlib from 1.18.2 to 1.19.9 or later in postgis/postgis:16-master. 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.19.9); 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-24539 fixed in 1.19.9
  • High CVE-2023-29400 fixed in 1.19.9
  • High CVE-2022-27664 fixed in 1.18.6
  • High CVE-2022-28131 fixed in 1.18.4
  • High CVE-2022-2879 fixed in 1.18.7
  • High CVE-2022-2880 fixed in 1.18.7
  • High CVE-2022-29804 fixed in 1.18.3
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30631 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30633 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • High CVE-2022-41715 fixed in 1.18.7
  • High CVE-2022-41716 fixed in 1.18.8
  • High CVE-2022-41720 fixed in 1.18.9
  • High CVE-2022-41722 fixed in 1.19.6
  • High CVE-2022-41723 fixed in 1.19.6
  • High CVE-2022-41724 fixed in 1.19.6
  • and 70 more
High 70 known vulnerabilities in stdlib@1.19.4 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 70 CVEs

How to fix

Update stdlib from 1.19.4 to 1.19.9 or later in gcr.io/cadvisor/cadvisor:v0.47.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.19.9); 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-24539 fixed in 1.19.9
  • High CVE-2023-29400 fixed in 1.19.9
  • High CVE-2022-30635 fixed in 1.22.7
  • High CVE-2022-41722 fixed in 1.19.6
  • High CVE-2022-41723 fixed in 1.19.6
  • High CVE-2022-41724 fixed in 1.19.6
  • High CVE-2022-41725 fixed in 1.19.6
  • High CVE-2023-24534 fixed in 1.19.8
  • High CVE-2023-24536 fixed in 1.19.8
  • High CVE-2023-24537 fixed in 1.19.8
  • High CVE-2023-39325 fixed in 1.20.10
  • High CVE-2023-44487 fixed in 1.20.10
  • High CVE-2023-45283 fixed in 1.20.11
  • High CVE-2023-45287 fixed in 1.20.0
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • and 50 more
High 57 known vulnerabilities in stdlib@1.20.4 (grafana/grafana:10.0.0) Security · 57 CVEs

How to fix

Update stdlib from 1.20.4 to 1.22.7 or later in grafana/grafana:10.0.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.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-2022-30635 fixed in 1.22.7
  • High CVE-2023-39325 fixed in 1.20.10
  • High CVE-2023-44487 fixed in 1.20.10
  • High CVE-2023-45283 fixed in 1.20.11
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2023-29403 fixed in 1.20.5
  • and 37 more
High 56 known vulnerabilities in stdlib@1.20.5 (prom/prometheus:v2.45.0) Security · 56 CVEs

How to fix

Update stdlib from 1.20.5 to 1.22.7 or later in prom/prometheus:v2.45.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.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-2022-30635 fixed in 1.22.7
  • High CVE-2023-39325 fixed in 1.20.10
  • High CVE-2023-44487 fixed in 1.20.10
  • High CVE-2023-45283 fixed in 1.20.11
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • and 36 more
High 55 known vulnerabilities in stdlib@1.20.6 (prom/node-exporter:v1.6.1) Security · 55 CVEs

How to fix

Update stdlib from 1.20.6 to 1.22.7 or later in prom/node-exporter:v1.6.1. 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-2022-30635 fixed in 1.22.7
  • High CVE-2023-39325 fixed in 1.20.10
  • High CVE-2023-44487 fixed in 1.20.10
  • High CVE-2023-45283 fixed in 1.20.11
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • and 35 more
High 54 known vulnerabilities in stdlib@1.20.7 (grafana/loki:2.9.0) Security · 54 CVEs

How to fix

Update stdlib from 1.20.7 to 1.22.7 or later in grafana/loki:2.9.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.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-2022-30635 fixed in 1.22.7
  • High CVE-2023-39325 fixed in 1.20.10
  • High CVE-2023-44487 fixed in 1.20.10
  • High CVE-2023-45283 fixed in 1.20.11
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • and 34 more
High 50 known vulnerabilities in stdlib@1.21.3 (grafana/tempo:2.3.1) Security · 50 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/tempo:2.3.1. 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-2022-30635 fixed in 1.22.7
  • High CVE-2023-45283 fixed in 1.21.4
  • High CVE-2023-45288 fixed in 1.21.9
  • High CVE-2024-24784 fixed in 1.21.8
  • High CVE-2024-24791 fixed in 1.21.12
  • High CVE-2024-34156 fixed in 1.22.7
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • High CVE-2024-24790 fixed in 1.21.11
  • High CVE-2025-68121 fixed in 1.24.13
  • and 30 more
High 34 known vulnerabilities in stdlib@1.23.3 (rclone/rclone:1.68) Security · 34 CVEs

How to fix

Update stdlib from 1.23.3 to 1.24.9 or later in rclone/rclone:1.68. 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.24.9); 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-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • High CVE-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-22866 fixed in 1.23.6
  • Medium CVE-2025-58183 fixed in 1.24.8
  • Medium CVE-2025-22870 fixed in 1.23.7
  • Medium CVE-2025-47912 fixed in 1.24.8
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-58186 fixed in 1.24.8
  • Medium CVE-2025-58189 fixed in 1.24.8
  • Medium CVE-2025-61724 fixed in 1.24.8
  • and 14 more
High 31 known vulnerabilities in stdlib@1.23.6 (quay.io/prometheuscommunity/postgres-exporter:v0.17.1) Security · 31 CVEs

How to fix

Update stdlib from 1.23.6 to 1.24.9 or later in quay.io/prometheuscommunity/postgres-exporter:v0.17.1. 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.24.9); 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-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-22871 fixed in 1.23.8
  • High CVE-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • Medium CVE-2025-22870 fixed in 1.23.7
  • Medium CVE-2025-47912 fixed in 1.24.8
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-58186 fixed in 1.24.8
  • Medium CVE-2025-58189 fixed in 1.24.8
  • Medium CVE-2025-61724 fixed in 1.24.8
  • Medium CVE-2025-61730 fixed in 1.24.12
  • and 11 more
High 25 known vulnerabilities in openssl@3.0.9-r1 (grafana/grafana:10.0.0) Security · 25 CVEs

How to fix

Update openssl from 3.0.9-r1 to 3.0.19-r0 or later in grafana/grafana:10.0.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 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-2023-5363 fixed in 3.0.12-r0
  • High CVE-2024-4741 fixed in 3.0.14-r0
  • High CVE-2024-6119 fixed in 3.0.15-r0
  • High CVE-2025-69420 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-15467 fixed in 3.0.19-r0
  • High CVE-2024-5535 fixed in 3.0.14-r0
  • Medium CVE-2025-69418 fixed in 3.0.19-r0
  • Medium CVE-2024-13176 fixed in 3.0.19-r0
  • Medium CVE-2024-9143 fixed in 3.0.15-r1
  • Medium CVE-2025-68160 fixed in 3.0.19-r0
  • Medium CVE-2023-2975 fixed in 3.0.9-r2
  • Medium CVE-2023-3446 fixed in 3.0.9-r3
  • Medium CVE-2023-3817 fixed in 3.0.10-r0
  • Medium CVE-2023-5678 fixed in 3.0.12-r1
  • Medium CVE-2024-4603 fixed in 3.0.13-r0
  • Medium CVE-2026-22796 fixed in 3.0.19-r0
  • Medium CVE-2024-0727 fixed in 3.0.12-r4
  • and 5 more
High 21 known vulnerabilities in openssl@3.5.1-1 (tons/docker-compose-docs:2.1.0) Security · 21 CVEs

How to fix

Update openssl from 3.5.1-1 to 3.5.4-1~deb13u2 or later in tons/docker-compose-docs:2.1.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 3.5.4-1~deb13u2); 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.5.4-1~deb13u2
  • High CVE-2025-69420 fixed in 3.5.4-1~deb13u2
  • High CVE-2025-69421 fixed in 3.5.4-1~deb13u2
  • High CVE-2025-9230 fixed in 3.5.1-1+deb13u1
  • High CVE-2026-28388 fixed in 3.5.5-1~deb13u2
  • High CVE-2026-28389 fixed in 3.5.5-1~deb13u2
  • High CVE-2026-28390 fixed in 3.5.5-1~deb13u2
  • Medium CVE-2025-69418 fixed in 3.5.4-1~deb13u2
  • Medium CVE-2025-68160 fixed in 3.5.4-1~deb13u2
  • Medium CVE-2026-22796 fixed in 3.5.4-1~deb13u2
  • Medium CVE-2026-22795 fixed in 3.5.4-1~deb13u2
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2025-11187 fixed in 3.5.4-1~deb13u2
  • Low CVE-2025-15467 fixed in 3.5.4-1~deb13u2
  • Low CVE-2025-15468 fixed in 3.5.4-1~deb13u2
  • Low CVE-2025-15469 fixed in 3.5.4-1~deb13u2
  • Low CVE-2025-66199 fixed in 3.5.4-1~deb13u2
  • Low CVE-2025-9231 fixed in 3.5.1-1+deb13u1
  • Low CVE-2025-9232 fixed in 3.5.1-1+deb13u1
  • Low CVE-2026-2673 fixed in 3.5.5-1~deb13u2
  • and 1 more
High 20 known vulnerabilities in openssl@3.3.2-r0 (curlimages/curl:8.10.1) Security · 20 CVEs

How to fix

Update openssl from 3.3.2-r0 to 3.3.6-r0 or later in curlimages/curl:8.10.1. 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.3.6-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.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2024-13176 fixed in 3.3.2-r2
  • Medium CVE-2024-9143 fixed in 3.3.2-r1
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • Medium CVE-2024-12797 fixed in 3.3.3-r0
  • Medium CVE-2025-9231 fixed in 3.3.5-r0
High 20 known vulnerabilities in openssl@3.3.2-r0 (rclone/rclone:1.68) Security · 20 CVEs

How to fix

Update openssl from 3.3.2-r0 to 3.3.6-r0 or later in rclone/rclone:1.68. 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.3.6-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.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2024-13176 fixed in 3.3.2-r2
  • Medium CVE-2024-9143 fixed in 3.3.2-r1
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • Medium CVE-2024-12797 fixed in 3.3.3-r0
  • Medium CVE-2025-9231 fixed in 3.3.5-r0
High 19 known vulnerabilities in tiff@4.2.0-1%2Bdeb11u7 (postgis/postgis:16-master) Security · 19 CVEs

How to fix

Update tiff from 4.2.0-1%2Bdeb11u7 to 4.2.0-1+deb11u8 or later in postgis/postgis:16-master. 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 4.2.0-1+deb11u8); 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-4775 fixed in 4.2.0-1+deb11u8
  • Low CVE-2017-16232 fixed in no fix yet
  • Low CVE-2017-17973 fixed in no fix yet
  • Low CVE-2018-10126 fixed in no fix yet
  • Low CVE-2022-1056 fixed in no fix yet
  • Low CVE-2023-1916 fixed in no fix yet
  • Low CVE-2023-30775 fixed in no fix yet
  • Low CVE-2023-3164 fixed in no fix yet
  • Low CVE-2023-6228 fixed in no fix yet
  • Low CVE-2024-6716 fixed in no fix yet
  • Low CVE-2025-61143 fixed in no fix yet
  • Low CVE-2025-61144 fixed in no fix yet
  • Low CVE-2025-61145 fixed in no fix yet
  • Low CVE-2025-8176 fixed in no fix yet
  • Low CVE-2025-8177 fixed in no fix yet
  • Low CVE-2025-8534 fixed in no fix yet
  • Low CVE-2025-8851 fixed in no fix yet
  • Low CVE-2025-8961 fixed in no fix yet
  • Low CVE-2025-9165 fixed in no fix yet
High 18 known vulnerabilities in openssl@1.1.1w-0%2Bdeb11u3 (postgis/postgis:16-master) Security · 18 CVEs

How to fix

Update openssl from 1.1.1w-0%2Bdeb11u3 to 1.1.1w-0+deb11u5 or later in postgis/postgis:16-master. 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.1.1w-0+deb11u5); 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 1.1.1w-0+deb11u5
  • High CVE-2025-69420 fixed in 1.1.1w-0+deb11u5
  • High CVE-2025-69421 fixed in 1.1.1w-0+deb11u5
  • High CVE-2025-9230 fixed in 1.1.1w-0+deb11u4
  • High CVE-2026-28388 fixed in no fix yet
  • High CVE-2026-28388 fixed in no fix yet
  • High CVE-2026-28389 fixed in no fix yet
  • High CVE-2026-28389 fixed in no fix yet
  • High CVE-2026-28390 fixed in no fix yet
  • High CVE-2026-28390 fixed in no fix yet
  • Medium CVE-2025-69418 fixed in 1.1.1w-0+deb11u5
  • Medium CVE-2025-68160 fixed in 1.1.1w-0+deb11u5
  • Medium CVE-2026-22796 fixed in 1.1.1w-0+deb11u5
  • Medium CVE-2026-22795 fixed in 1.1.1w-0+deb11u5
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2025-27587 fixed in no fix yet
  • Low CVE-2025-27587 fixed in no fix yet
High 17 known vulnerabilities in openssl@3.5.4-r0 (traefik:v3.5) Security · 17 CVEs

How to fix

Update openssl from 3.5.4-r0 to 3.5.5-r0 or later in traefik:v3.5. 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.5-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.5.5-r0
  • High CVE-2025-69420 fixed in 3.5.5-r0
  • High CVE-2025-69421 fixed in 3.5.5-r0
  • High CVE-2026-2673 fixed in 3.5.6-r0
  • High CVE-2026-28388 fixed in 3.5.6-r0
  • High CVE-2026-28389 fixed in 3.5.6-r0
  • High CVE-2026-28390 fixed in 3.5.6-r0
  • High CVE-2026-31790 fixed in 3.5.6-r0
  • High CVE-2025-15467 fixed in 3.5.5-r0
  • Medium CVE-2025-69418 fixed in 3.5.5-r0
  • Medium CVE-2025-68160 fixed in 3.5.5-r0
  • Medium CVE-2026-22796 fixed in 3.5.5-r0
  • Medium CVE-2025-15469 fixed in 3.5.5-r0
  • Medium CVE-2026-22795 fixed in 3.5.5-r0
  • Medium CVE-2025-15468 fixed in 3.5.5-r0
  • Medium CVE-2025-66199 fixed in 3.5.5-r0
  • Medium CVE-2025-11187 fixed in 3.5.5-r0
High 15 known vulnerabilities in curl@8.2.0-r1 (grafana/grafana:10.0.0) Security · 15 CVEs

How to fix

Update curl from 8.2.0-r1 to 8.3.0-r0 or later in grafana/grafana:10.0.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 8.3.0-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-2023-38039 fixed in 8.3.0-r0
  • High CVE-2024-6197 fixed in 8.9.0-r0
  • High CVE-2024-2398 fixed in 8.7.1-r0
  • High CVE-2023-38545 fixed in 8.4.0-r0
  • Medium CVE-2024-6874 fixed in 8.9.0-r0
  • Medium CVE-2023-46219 fixed in 8.5.0-r0
  • Medium CVE-2024-0853 fixed in no fix yet
  • Medium CVE-2024-2379 fixed in 8.7.1-r0
  • Medium CVE-2023-46218 fixed in 8.5.0-r0
  • Medium CVE-2024-2466 fixed in 8.7.1-r0
  • Medium CVE-2024-7264 fixed in no fix yet
  • Medium CVE-2024-8096 fixed in no fix yet
  • Medium CVE-2024-9681 fixed in no fix yet
  • Low CVE-2024-2004 fixed in 8.7.1-r0
  • Low CVE-2023-38546 fixed in 8.4.0-r0
High 15 known vulnerabilities in openssl@3.1.1-r1 (grafana/loki:2.9.0) Security · 15 CVEs

How to fix

Update openssl from 3.1.1-r1 to 3.1.4-r0 or later in grafana/loki:2.9.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 3.1.4-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-2023-5363 fixed in 3.1.4-r0
  • High CVE-2024-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2023-2975 fixed in 3.1.1-r2
  • Medium CVE-2023-3446 fixed in 3.1.1-r3
  • Medium CVE-2023-3817 fixed in 3.1.2-r0
  • Medium CVE-2023-5678 fixed in 3.1.4-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 15 known vulnerabilities in stdlib@1.24.10 (traefik:v3.5) Security · 15 CVEs

How to fix

Update stdlib from 1.24.10 to 1.24.12 or later in traefik:v3.5. 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.24.12); 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-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-32280 fixed in 1.25.9
  • High CVE-2026-32281 fixed in 1.25.9
  • High CVE-2026-32283 fixed in 1.25.9
  • High CVE-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-61730 fixed in 1.24.12
  • Medium CVE-2026-32288 fixed in 1.25.9
  • Medium CVE-2026-27142 fixed in 1.25.8
  • Medium CVE-2026-32289 fixed in 1.25.9
  • Medium CVE-2026-32282 fixed in 1.25.9
  • Medium CVE-2025-61727 fixed in 1.24.11
  • Medium CVE-2025-61728 fixed in 1.24.12
  • Low CVE-2026-27139 fixed in 1.25.8
High 12 known vulnerabilities in openssl@3.1.3-r0 (grafana/tempo:2.3.1) Security · 12 CVEs

How to fix

Update openssl from 3.1.3-r0 to 3.1.4-r0 or later in grafana/tempo:2.3.1. 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.1.4-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-2023-5363 fixed in 3.1.4-r0
  • High CVE-2024-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2023-5678 fixed in 3.1.4-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 10 known vulnerabilities in docker@20.10.21%2Bincompatible (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 10 CVEs

How to fix

Update docker from 20.10.21%2Bincompatible to 20.10.24 or later in gcr.io/cadvisor/cadvisor:v0.47.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 20.10.24); 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-28840 fixed in 20.10.24
  • High CVE-2026-34040 fixed in no fix yet
  • High CVE-2024-41110 fixed in 23.0.15
  • Medium GHSA-jq35-85cj-fj4p fixed in 20.10.27
  • Medium CVE-2024-29018 fixed in 23.0.11
  • Medium CVE-2023-28841 fixed in 20.10.24
  • Medium CVE-2023-28842 fixed in 20.10.24
  • Medium CVE-2026-33997 fixed in no fix yet
  • Medium CVE-2024-24557 fixed in 24.0.9
  • Low CVE-2025-54410 fixed in 25.0.13
High 10 known vulnerabilities in net@0.4.0 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 10 CVEs

How to fix

Update net from 0.4.0 to 0.7.0 or later in gcr.io/cadvisor/cadvisor:v0.47.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.7.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-41723 fixed in 0.7.0
  • High CVE-2023-39325 fixed in 0.17.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2023-3978 fixed in 0.13.0
  • Medium CVE-2023-44487 fixed in 0.17.0
High 10 known vulnerabilities in openssl@1.1.1s-r0 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 10 CVEs

How to fix

Update openssl from 1.1.1s-r0 to 1.1.1t-r0 or later in gcr.io/cadvisor/cadvisor:v0.47.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.1.1t-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-2023-0286 fixed in 1.1.1t-r0
  • High CVE-2023-0464 fixed in 1.1.1t-r1
  • Medium CVE-2022-4304 fixed in 1.1.1t-r0
  • Medium CVE-2022-4450 fixed in 1.1.1t-r0
  • Medium CVE-2023-0215 fixed in 1.1.1t-r0
  • Medium CVE-2023-0465 fixed in 1.1.1t-r2
  • Medium CVE-2023-3446 fixed in 1.1.1u-r2
  • Medium CVE-2023-3817 fixed in 1.1.1v-r0
  • Medium CVE-2023-5678 fixed in 1.1.1w-r1
  • Medium CVE-2023-2650 fixed in 1.1.1u-r0
High 10 known vulnerabilities in aa_ER@saaho (postgis/postgis:16-master) Security · 10 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether postgis/postgis:16-master needs aa_ER 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-4046 fixed in no fix yet
  • High CVE-2026-5928 fixed in no fix yet
  • High CVE-2026-5450 fixed in no fix yet
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • Low CVE-2019-1010024 fixed in no fix yet
  • Low CVE-2019-1010025 fixed in no fix yet
  • Low CVE-2019-9192 fixed in no fix yet
High 10 known vulnerabilities in glibc@2.41-12 (tons/docker-compose-docs:2.1.0) Security · 10 CVEs

How to fix

Update glibc from 2.41-12 to 2.41-12+deb13u2 or later in tons/docker-compose-docs:2.1.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 2.41-12+deb13u2); 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-15281 fixed in 2.41-12+deb13u2
  • High CVE-2026-0915 fixed in 2.41-12+deb13u2
  • High CVE-2026-0861 fixed in 2.41-12+deb13u2
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • Low CVE-2019-1010024 fixed in no fix yet
  • Low CVE-2019-1010025 fixed in no fix yet
  • Low CVE-2019-9192 fixed in no fix yet
High 9 known vulnerabilities in tomcat-embed-core@11.0.15 (dhis2/core:42) Security · 9 CVEs

How to fix

Update tomcat-embed-core from 11.0.15 to 11.0.18 or later in dhis2/core:42. 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 11.0.18); 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-24734 fixed in 11.0.18
  • High CVE-2026-24880 fixed in 11.0.20
  • High CVE-2026-34483 fixed in 11.0.21
  • High CVE-2026-34487 fixed in 11.0.21
  • High CVE-2026-29146 fixed in 11.0.19
  • High CVE-2026-29145 fixed in 11.0.20
  • Medium CVE-2026-34500 fixed in 11.0.21
  • Medium CVE-2026-25854 fixed in 11.0.20
  • Medium CVE-2026-32990 fixed in 11.0.20
High 9 known vulnerabilities in net@0.9.0 (grafana/grafana:10.0.0) Security · 9 CVEs

How to fix

Update net from 0.9.0 to 0.17.0 or later in grafana/grafana:10.0.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.17.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-2023-39325 fixed in 0.17.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2023-3978 fixed in 0.13.0
  • Medium CVE-2023-44487 fixed in 0.17.0
High 9 known vulnerabilities in net@0.12.0 (grafana/loki:2.9.0) Security · 9 CVEs

How to fix

Update net from 0.12.0 to 0.17.0 or later in grafana/loki:2.9.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.17.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-2023-39325 fixed in 0.17.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2023-3978 fixed in 0.13.0
  • Medium CVE-2023-44487 fixed in 0.17.0
High 9 known vulnerabilities in net@0.10.0 (prom/node-exporter:v1.6.1) Security · 9 CVEs

How to fix

Update net from 0.10.0 to 0.17.0 or later in prom/node-exporter:v1.6.1. 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.17.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-2023-39325 fixed in 0.17.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2023-3978 fixed in 0.13.0
  • Medium CVE-2023-44487 fixed in 0.17.0
High 9 known vulnerabilities in net@0.10.0 (prom/prometheus:v2.45.0) Security · 9 CVEs

How to fix

Update net from 0.10.0 to 0.17.0 or later in prom/prometheus:v2.45.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.17.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-2023-39325 fixed in 0.17.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2023-3978 fixed in 0.13.0
  • Medium CVE-2023-44487 fixed in 0.17.0
High 8 known vulnerabilities in runc@1.1.4 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 8 CVEs

How to fix

Update runc from 1.1.4 to 1.1.5 or later in gcr.io/cadvisor/cadvisor:v0.47.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.1.5); 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-27561 fixed in 1.1.5
  • High CVE-2025-31133 fixed in 1.2.8
  • High CVE-2025-52565 fixed in 1.2.8
  • High CVE-2025-52881 fixed in 1.2.8
  • High CVE-2024-21626 fixed in 1.1.12
  • Medium CVE-2024-45310 fixed in 1.1.14
  • Medium CVE-2023-28642 fixed in 1.1.5
  • Low CVE-2023-25809 fixed in 1.1.5
High 8 known vulnerabilities in go-git@5.4.2#v5 (grafana/grafana:10.0.0) Security · 8 CVEs

How to fix

Update go-git from 5.4.2#v5 to 5.11.0 or later in grafana/grafana:10.0.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 5.11.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-2023-49568 fixed in 5.11.0
  • High CVE-2025-21614 fixed in 5.13.0
  • High CVE-2025-21613 fixed in 5.13.0
  • High CVE-2023-49569 fixed in 5.11.0
  • Medium CVE-2026-25934 fixed in 5.16.5
  • Medium GHSA-3xc5-wrhm-f963 fixed in 5.18.0
  • Medium CVE-2026-34165 fixed in 5.17.1
  • Low CVE-2026-33762 fixed in 5.17.1
High 8 known vulnerabilities in grafana@10.0.0 (grafana/grafana:10.0.0) Security · 8 CVEs

How to fix

Update grafana from 10.0.0 to 10.0.12 or later in grafana/grafana:10.0.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 10.0.12); 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-1442 fixed in 10.0.12
  • High CVE-2024-1313 fixed in 10.0.13
  • Medium CVE-2024-11741 fixed in 10.4.15
  • Medium CVE-2023-6152 fixed in 10.0.11
  • Medium CVE-2026-27877 fixed in no fix yet
  • Medium CVE-2023-4822 fixed in no fix yet
  • Low CVE-2024-10452 fixed in no fix yet
  • Low CVE-2025-1088 fixed in 11.6.2
High 7 known vulnerabilities in tomcat-catalina@10.1.48 (dhis2/core:42) Security · 7 CVEs

How to fix

Update tomcat-catalina from 10.1.48 to 10.1.54 or later in dhis2/core:42. 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 10.1.54); 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-34483 fixed in 10.1.54
  • High CVE-2026-34487 fixed in 10.1.54
  • High CVE-2026-29145 fixed in 10.1.53
  • Medium CVE-2025-66614 fixed in 10.1.49
  • Medium CVE-2026-34500 fixed in 10.1.54
  • Medium CVE-2026-25854 fixed in 10.1.53
  • Low CVE-2026-24733 fixed in 10.1.49
High 6 known vulnerabilities in crypto@0.1.0 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 6 CVEs

How to fix

Update crypto from 0.1.0 to 0.35.0 or later in gcr.io/cadvisor/cadvisor:v0.47.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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.7.0 (grafana/grafana:10.0.0) Security · 6 CVEs

How to fix

Update crypto from 0.7.0 to 0.35.0 or later in grafana/grafana:10.0.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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.11.0 (grafana/loki:2.9.0) Security · 6 CVEs

How to fix

Update crypto from 0.11.0 to 0.35.0 or later in grafana/loki:2.9.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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.14.0 (grafana/tempo:2.3.1) Security · 6 CVEs

How to fix

Update crypto from 0.14.0 to 0.35.0 or later in grafana/tempo:2.3.1. 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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.8.0 (prom/node-exporter:v1.6.1) Security · 6 CVEs

How to fix

Update crypto from 0.8.0 to 0.35.0 or later in prom/node-exporter:v1.6.1. 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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0
High 6 known vulnerabilities in crypto@0.8.0 (prom/prometheus:v2.45.0) Security · 6 CVEs

How to fix

Update crypto from 0.8.0 to 0.35.0 or later in prom/prometheus:v2.45.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.35.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-22869 fixed in 0.35.0
  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2024-45337 fixed in 0.31.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2023-48795 fixed in 0.17.0

and 88 more groups with 158 findings

Medium 207

Medium 14 known vulnerabilities in openssl@3.0.13-0ubuntu3.6 (dhis2/core:42) Security · 14 CVEs

How to fix

Update openssl from 3.0.13-0ubuntu3.6 to 3.0.13-0ubuntu3.7 or later in dhis2/core:42. 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.13-0ubuntu3.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

  • Medium CVE-2025-15467 fixed in 3.0.13-0ubuntu3.7
  • Medium CVE-2026-31790 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2025-68160 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2025-69418 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2025-69419 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2025-69420 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2026-22795 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2026-22796 fixed in 3.0.13-0ubuntu3.7
  • Low CVE-2026-28387 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2026-28388 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2026-28389 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2026-28390 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2026-31789 fixed in 3.0.13-0ubuntu3.9
  • Low CVE-2025-69421 fixed in 3.0.13-0ubuntu3.7
Medium 10 known vulnerabilities in curl@8.5.0-2ubuntu10.6 (dhis2/core:42) Security · 10 CVEs

How to fix

Update curl from 8.5.0-2ubuntu10.6 to 8.5.0-2ubuntu10.7 or later in dhis2/core:42. 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 8.5.0-2ubuntu10.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

  • Medium CVE-2025-14017 fixed in 8.5.0-2ubuntu10.7
  • Medium CVE-2026-1965 fixed in 8.5.0-2ubuntu10.8
  • Medium CVE-2026-3783 fixed in 8.5.0-2ubuntu10.8
  • Low CVE-2025-0167 fixed in 8.5.0-2ubuntu10.8
  • Low CVE-2025-10148 fixed in 8.5.0-2ubuntu10.7
  • Low CVE-2025-14524 fixed in 8.5.0-2ubuntu10.7
  • Low CVE-2025-14819 fixed in 8.5.0-2ubuntu10.7
  • Low CVE-2025-15079 fixed in 8.5.0-2ubuntu10.7
  • Low CVE-2025-15224 fixed in 8.5.0-2ubuntu10.7
  • Low CVE-2026-3784 fixed in 8.5.0-2ubuntu10.8
Medium 10 known vulnerabilities in libpng1.6@1.6.43-5build1 (dhis2/core:42) Security · 10 CVEs

How to fix

Update libpng1.6 from 1.6.43-5build1 to 1.6.43-5ubuntu0.4 or later in dhis2/core:42. 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.6.43-5ubuntu0.4); 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-2025-28162 fixed in 1.6.43-5ubuntu0.4
  • Medium CVE-2025-28164 fixed in 1.6.43-5ubuntu0.4
  • Medium CVE-2025-64505 fixed in 1.6.43-5ubuntu0.1
  • Medium CVE-2025-64506 fixed in 1.6.43-5ubuntu0.1
  • Medium CVE-2025-64720 fixed in 1.6.43-5ubuntu0.1
  • Medium CVE-2025-65018 fixed in 1.6.43-5ubuntu0.1
  • Medium CVE-2025-66293 fixed in 1.6.43-5ubuntu0.3
  • Medium CVE-2026-22695 fixed in 1.6.43-5ubuntu0.3
  • Medium CVE-2026-22801 fixed in 1.6.43-5ubuntu0.3
  • Medium CVE-2026-25646 fixed in 1.6.43-5ubuntu0.5
Medium 10 known vulnerabilities in openjpeg2@2.4.0-3%2Bdeb11u2 (postgis/postgis:16-master) Security · 10 CVEs

How to fix

No fixed version of openjpeg2 is available yet. Check whether postgis/postgis:16-master needs openjpeg2 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-2026-6192 fixed in no fix yet
  • Low CVE-2016-10505 fixed in no fix yet
  • Low CVE-2016-9113 fixed in no fix yet
  • Low CVE-2016-9114 fixed in no fix yet
  • Low CVE-2016-9115 fixed in no fix yet
  • Low CVE-2016-9116 fixed in no fix yet
  • Low CVE-2016-9117 fixed in no fix yet
  • Low CVE-2016-9580 fixed in no fix yet
  • Low CVE-2016-9581 fixed in no fix yet
  • Low CVE-2018-16376 fixed in no fix yet
Medium 10 known vulnerabilities in systemd@247.3-7%2Bdeb11u6 (postgis/postgis:16-master) Security · 10 CVEs

How to fix

Update systemd from 247.3-7%2Bdeb11u6 to 247.3-7+deb11u7 or later in postgis/postgis:16-master. 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 247.3-7+deb11u7); 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-2025-4598 fixed in 247.3-7+deb11u7
  • Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
  • Medium CVE-2026-40225 fixed in 247.3-7+deb11u8
  • Medium CVE-2026-40226 fixed in 247.3-7+deb11u8
  • Medium CVE-2026-4105 fixed in 247.3-7+deb11u8
  • Low CVE-2013-4392 fixed in no fix yet
  • Low CVE-2020-13529 fixed in no fix yet
  • Low CVE-2023-31437 fixed in no fix yet
  • Low CVE-2023-31438 fixed in no fix yet
  • Low CVE-2023-31439 fixed in no fix yet
Medium 7 known vulnerabilities in libssh@0.10.6-2ubuntu0.2 (dhis2/core:42) Security · 7 CVEs

How to fix

Update libssh from 0.10.6-2ubuntu0.2 to 0.10.6-2ubuntu0.3 or later in dhis2/core:42. 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.10.6-2ubuntu0.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

  • Medium CVE-2026-0964 fixed in 0.10.6-2ubuntu0.3
  • Medium CVE-2026-0968 fixed in 0.10.6-2ubuntu0.3
  • Medium CVE-2026-0967 fixed in 0.10.6-2ubuntu0.3
  • Medium CVE-2026-3731 fixed in 0.10.6-2ubuntu0.4
  • Low CVE-2025-8277 fixed in 0.10.6-2ubuntu0.3
  • Low CVE-2026-0965 fixed in 0.10.6-2ubuntu0.3
  • Low CVE-2026-0966 fixed in 0.10.6-2ubuntu0.3
Medium 6 known vulnerabilities in be_BY@latin (dhis2/core:42) Security · 6 CVEs

How to fix

Update be_BY from latin to 2.39-0ubuntu8.7 or later in dhis2/core:42. 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 2.39-0ubuntu8.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

  • Medium CVE-2025-15281 fixed in 2.39-0ubuntu8.7
  • Medium CVE-2026-0861 fixed in 2.39-0ubuntu8.7
  • Medium CVE-2026-0915 fixed in 2.39-0ubuntu8.7
  • Medium CVE-2026-4046 fixed in no fix yet
  • Medium CVE-2026-4437 fixed in no fix yet
  • Medium CVE-2026-4438 fixed in no fix yet
Medium 6 known vulnerabilities in net@0.17.0 (grafana/tempo:2.3.1) Security · 6 CVEs

How to fix

Update net from 0.17.0 to 0.36.0 or later in grafana/tempo:2.3.1. 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.36.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-2025-22870 fixed in 0.36.0
  • Medium CVE-2023-45288 fixed in 0.23.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
Medium 6 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u7 (postgis/postgis:16-master) Security · 6 CVEs

How to fix

Update gnutls28 from 3.7.1-5%2Bdeb11u7 to 3.7.1-5+deb11u9 or later in postgis/postgis:16-master. 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.7.1-5+deb11u9); 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-2025-9820 fixed in 3.7.1-5+deb11u9
  • Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
  • Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
  • Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
  • Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
  • Low CVE-2011-3389 fixed in no fix yet
Medium 5 known vulnerabilities in bcprov-jdk15on@1.70 (dhis2/core:42) Security · 5 CVEs

How to fix

No fixed version of bcprov-jdk15on is available yet. Check whether dhis2/core:42 needs bcprov-jdk15on 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-2023-33201 fixed in no fix yet
  • Medium CVE-2024-29857 fixed in 1.78
  • Medium CVE-2024-30172 fixed in 1.78
  • Medium CVE-2024-30171 fixed in 1.78
  • Medium CVE-2024-34447 fixed in 1.78
Medium 5 known vulnerabilities in net@0.27.0 (rclone/rclone:1.68) Security · 5 CVEs

How to fix

Update net from 0.27.0 to 0.36.0 or later in rclone/rclone:1.68. 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.36.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-2025-22870 fixed in 0.36.0
  • Medium CVE-2024-45338 fixed in 0.33.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
Medium 4 known vulnerabilities in busybox@1.35.0-r29 (grafana/grafana:10.0.0) Security · 4 CVEs

How to fix

Update busybox from 1.35.0-r29 to 1.35.0-r31 or later in grafana/grafana:10.0.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.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 4 known vulnerabilities in busybox@1.36.1-r2 (grafana/tempo:2.3.1) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r2 to 1.36.1-r7 or later in grafana/tempo:2.3.1. 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.36.1-r7); 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.36.1-r7
  • Medium CVE-2023-42364 fixed in 1.36.1-r7
  • Medium CVE-2023-42365 fixed in 1.36.1-r7
  • Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium 4 known vulnerabilities in net@0.33.0 (quay.io/prometheuscommunity/postgres-exporter:v0.17.1) Security · 4 CVEs

How to fix

Update net from 0.33.0 to 0.36.0 or later in quay.io/prometheuscommunity/postgres-exporter:v0.17.1. 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.36.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-2025-22870 fixed in 0.36.0
  • Medium CVE-2025-22872 fixed in 0.38.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (curlimages/curl:8.10.1) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether curlimages/curl:8.10.1 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-r31
  • Low CVE-2025-46394 fixed in 1.36.1-r31
Medium 3 known vulnerabilities in expat@2.6.1-2ubuntu0.3 (dhis2/core:42) Security · 3 CVEs

How to fix

Update expat from 2.6.1-2ubuntu0.3 to 2.6.1-2ubuntu0.4 or later in dhis2/core:42. 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 2.6.1-2ubuntu0.4); 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-24515 fixed in 2.6.1-2ubuntu0.4
  • Medium CVE-2025-66382 fixed in no fix yet
  • Medium CVE-2026-25210 fixed in 2.6.1-2ubuntu0.4
Medium 3 known vulnerabilities in log4j-core@2.25.3 (dhis2/core:42) Security · 3 CVEs

How to fix

Update log4j-core from 2.25.3 to 2.25.4 or later in dhis2/core:42. 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 2.25.4); 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-34477 fixed in 2.25.4
  • Medium CVE-2026-34478 fixed in 2.25.4
  • Medium CVE-2026-34480 fixed in 2.25.4
Medium 3 known vulnerabilities in spring-webmvc@6.2.8 (dhis2/core:42) Security · 3 CVEs

How to fix

Update spring-webmvc from 6.2.8 to 6.2.10 or later in dhis2/core:42. 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.2.10); 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-2025-41242 fixed in 6.2.10
  • Medium CVE-2026-22737 fixed in 6.2.17
  • Low CVE-2026-22735 fixed in 6.2.17
Medium 3 known vulnerabilities in perl@5.32.1-4%2Bdeb11u4 (postgis/postgis:16-master) Security · 3 CVEs

How to fix

Update perl from 5.32.1-4%2Bdeb11u4 to 5.32.1-4+deb11u5 or later in postgis/postgis:16-master. 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 5.32.1-4+deb11u5); 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-2025-40909 fixed in 5.32.1-4+deb11u5
  • Low CVE-2011-4116 fixed in no fix yet
  • Low CVE-2023-31486 fixed in no fix yet
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (rclone/rclone:1.68) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether rclone/rclone:1.68 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-r31
  • Low CVE-2025-46394 fixed in 1.36.1-r31
Medium 3 known vulnerabilities in busybox@1.37.0-r19 (traefik:v3.5) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether traefik:v3.5 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.37.0-r20
  • Low CVE-2025-46394 fixed in 1.37.0-r20
Medium 3 known vulnerabilities in exporters@1.38.0#otlp/otlptrace/otlptracehttp (traefik:v3.5) Security · 3 CVEs

How to fix

Update exporters from 1.38.0#otlp/otlptrace/otlptracehttp to 1.43.0 or later in traefik:v3.5. 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.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

  • Medium CVE-2026-39882 fixed in 1.43.0
  • Medium CVE-2026-39882 fixed in 1.43.0
  • Medium CVE-2026-39882 fixed in 0.19.0
Medium 2 known vulnerabilities in zlib@1.3.1-r1 (curlimages/curl:8.10.1) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r1 to 1.3.2-r0 or later in curlimages/curl:8.10.1. 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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 2 known vulnerabilities in gnutls28@3.8.3-1.1ubuntu3.4 (dhis2/core:42) Security · 2 CVEs

How to fix

Update gnutls28 from 3.8.3-1.1ubuntu3.4 to 3.8.3-1.1ubuntu3.5 or later in dhis2/core:42. 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.8.3-1.1ubuntu3.5); 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-2025-14831 fixed in 3.8.3-1.1ubuntu3.5
  • Low CVE-2025-9820 fixed in 3.8.3-1.1ubuntu3.5
Medium 2 known vulnerabilities in spring-webflux@6.2.8 (dhis2/core:42) Security · 2 CVEs

How to fix

Update spring-webflux from 6.2.8 to 6.2.17 or later in dhis2/core:42. 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.2.17); 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-22737 fixed in 6.2.17
  • Low CVE-2026-22735 fixed in 6.2.17
Medium 2 known vulnerabilities in aws-sdk-go@1.35.24 (gcr.io/cadvisor/cadvisor:v0.47.0) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether gcr.io/cadvisor/cadvisor:v0.47.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go@1.44.234 (grafana/grafana:10.0.0) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether grafana/grafana:10.0.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go@1.44.315 (grafana/loki:2.9.0) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether grafana/loki:2.9.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go@1.44.321 (grafana/tempo:2.3.1) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether grafana/tempo:2.3.1 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in exporters@0.41.0#otlp/otlpmetric/otlpmetrichttp (grafana/tempo:2.3.1) Security · 2 CVEs

How to fix

Update exporters from 0.41.0#otlp/otlpmetric/otlpmetrichttp to 1.43.0 or later in grafana/tempo:2.3.1. 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.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

  • Medium CVE-2026-39882 fixed in 1.43.0
  • Medium CVE-2026-39882 fixed in 1.43.0
Medium 2 known vulnerabilities in aws-sdk-go@1.44.276 (prom/prometheus:v2.45.0) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether prom/prometheus:v2.45.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go-v2@1.6.3#aws/protocol/eventstream (rclone/rclone:1.68) Security · 2 CVEs

How to fix

Update aws-sdk-go-v2 from 1.6.3#aws/protocol/eventstream to 1.7.8 or later in rclone/rclone:1.68. 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.7.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

  • Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.7.8
  • Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.97.3
Medium 2 known vulnerabilities in zlib@1.3.1-r1 (rclone/rclone:1.68) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r1 to 1.3.2-r0 or later in rclone/rclone:1.68. 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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 2 known vulnerabilities in pip@25.0.1 (tons/docker-compose-docs:2.1.0) Security · 2 CVEs

How to fix

Update pip from 25.0.1 to 25.3 or later in tons/docker-compose-docs:2.1.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 25.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

  • Medium CVE-2025-8869 fixed in 25.3
  • Low CVE-2026-1703 fixed in 26.0
Medium 2 known vulnerabilities in tar@1.35%2Bdfsg-3.1 (tons/docker-compose-docs:2.1.0) Security · 2 CVEs

How to fix

No fixed version of tar is available yet. Check whether tons/docker-compose-docs:2.1.0 needs tar 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-45582 fixed in no fix yet
  • Low CVE-2005-2541 fixed in no fix yet
Medium 2 known vulnerabilities in crypto@0.43.0 (traefik:v3.5) Security · 2 CVEs

How to fix

Update crypto from 0.43.0 to 0.45.0 or later in traefik:v3.5. 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.45.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-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (traefik:v3.5) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in traefik:v3.5. 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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 1 known vulnerability in busybox@1.37.0-r20 (alpine:3.22) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether alpine:3.22 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 dpkg@1.22.6ubuntu6.5 (dhis2/core:42) Security · 1 CVE

How to fix

No fixed version of dpkg is available yet. Check whether dhis2/core:42 needs dpkg 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-2026-2219 fixed in no fix yet
Medium 1 known vulnerability in freetype@2.13.2%2Bdfsg-1build3 (dhis2/core:42) Security · 1 CVE

How to fix

Update freetype from 2.13.2%2Bdfsg-1build3 to 2.13.2+dfsg-1ubuntu0.1 or later in dhis2/core:42. 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 2.13.2+dfsg-1ubuntu0.1); 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-23865 fixed in 2.13.2+dfsg-1ubuntu0.1

and 49 more groups with 49 findings

Low 171

Low 102 known vulnerabilities in hdf5@1.10.6%2Brepack-4%2Bdeb11u1 (postgis/postgis:16-master) Security · 102 CVEs

How to fix

No fixed version of hdf5 is available yet. Check whether postgis/postgis:16-master needs hdf5 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-2017-17507 fixed in no fix yet
  • Low CVE-2018-13869 fixed in no fix yet
  • Low CVE-2018-13870 fixed in no fix yet
  • Low CVE-2018-14031 fixed in no fix yet
  • Low CVE-2018-14033 fixed in no fix yet
  • Low CVE-2018-14034 fixed in no fix yet
  • Low CVE-2018-14035 fixed in no fix yet
  • Low CVE-2018-14460 fixed in no fix yet
  • Low CVE-2018-15671 fixed in no fix yet
  • Low CVE-2018-16438 fixed in no fix yet
  • Low CVE-2018-17432 fixed in no fix yet
  • Low CVE-2018-17433 fixed in no fix yet
  • Low CVE-2018-17435 fixed in no fix yet
  • Low CVE-2018-17436 fixed in no fix yet
  • Low CVE-2018-17439 fixed in no fix yet
  • Low CVE-2019-8396 fixed in no fix yet
  • Low CVE-2019-8397 fixed in no fix yet
  • Low CVE-2019-8398 fixed in no fix yet
  • Low CVE-2019-9151 fixed in no fix yet
  • Low CVE-2019-9152 fixed in no fix yet
  • and 82 more
Low 9 known vulnerabilities in curl@7.74.0-1.3%2Bdeb11u16 (postgis/postgis:16-master) Security · 9 CVEs

How to fix

No fixed version of curl is available yet. Check whether postgis/postgis:16-master needs curl 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-2021-22922 fixed in no fix yet
  • Low CVE-2021-22923 fixed in no fix yet
  • Low CVE-2023-28320 fixed in no fix yet
  • Low CVE-2024-2379 fixed in no fix yet
  • Low CVE-2025-0725 fixed in no fix yet
  • Low CVE-2025-10966 fixed in no fix yet
  • Low CVE-2025-14017 fixed in no fix yet
  • Low CVE-2025-15079 fixed in no fix yet
  • Low CVE-2025-15224 fixed in no fix yet
Low 5 known vulnerabilities in openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (postgis/postgis:16-master) Security · 5 CVEs

How to fix

No fixed version of openldap is available yet. Check whether postgis/postgis:16-master needs openldap 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-2015-3276 fixed in no fix yet
  • Low CVE-2017-14159 fixed in no fix yet
  • Low CVE-2017-17740 fixed in no fix yet
  • Low CVE-2020-15719 fixed in no fix yet
  • Low CVE-2026-22185 fixed in no fix yet
Low 5 known vulnerabilities in pcre3@2%3A8.39-13 (postgis/postgis:16-master) Security · 5 CVEs

How to fix

No fixed version of pcre3 is available yet. Check whether postgis/postgis:16-master needs pcre3 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-2017-11164 fixed in no fix yet
  • Low CVE-2017-16231 fixed in no fix yet
  • Low CVE-2017-7245 fixed in no fix yet
  • Low CVE-2017-7246 fixed in no fix yet
  • Low CVE-2019-20838 fixed in no fix yet
Low 5 known vulnerabilities in sqlite3@3.34.1-3%2Bdeb11u1 (postgis/postgis:16-master) Security · 5 CVEs

How to fix

No fixed version of sqlite3 is available yet. Check whether postgis/postgis:16-master needs sqlite3 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-2021-45346 fixed in no fix yet
  • Low CVE-2022-35737 fixed in no fix yet
  • Low CVE-2025-29088 fixed in no fix yet
  • Low CVE-2025-52099 fixed in no fix yet
  • Low CVE-2025-70873 fixed in no fix yet
Low 4 known vulnerabilities in systemd@257.8-1~deb13u1 (tons/docker-compose-docs:2.1.0) Security · 4 CVEs

How to fix

No fixed version of systemd is available yet. Check whether tons/docker-compose-docs:2.1.0 needs systemd 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-2013-4392 fixed in no fix yet
  • Low CVE-2023-31437 fixed in no fix yet
  • Low CVE-2023-31438 fixed in no fix yet
  • Low CVE-2023-31439 fixed in no fix yet
Low 3 known vulnerabilities in expat@2.2.10-2%2Bdeb11u7 (postgis/postgis:16-master) Security · 3 CVEs

How to fix

No fixed version of expat is available yet. Check whether postgis/postgis:16-master needs expat 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-2013-0340 fixed in no fix yet
  • Low CVE-2023-52426 fixed in no fix yet
  • Low CVE-2024-28757 fixed in no fix yet
Low 3 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u7 (postgis/postgis:16-master) Security · 3 CVEs

How to fix

No fixed version of krb5 is available yet. Check whether postgis/postgis:16-master needs krb5 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-2018-5709 fixed in no fix yet
  • Low CVE-2024-26458 fixed in no fix yet
  • Low CVE-2024-26461 fixed in no fix yet
Low 3 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u9 (postgis/postgis:16-master) Security · 3 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether postgis/postgis:16-master needs libxml2 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-2025-12863 fixed in no fix yet
  • Low CVE-2025-8732 fixed in no fix yet
  • Low CVE-2026-1757 fixed in no fix yet
Low 3 known vulnerabilities in sqlite3@3.46.1-7 (tons/docker-compose-docs:2.1.0) Security · 3 CVEs

How to fix

No fixed version of sqlite3 is available yet. Check whether tons/docker-compose-docs:2.1.0 needs sqlite3 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-2021-45346 fixed in no fix yet
  • Low CVE-2025-70873 fixed in no fix yet
  • Low CVE-2025-7709 fixed in 3.46.1-7+deb13u1
Low 2 known vulnerabilities in coreutils@8.32-4%2Bb1 (postgis/postgis:16-master) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether postgis/postgis:16-master needs coreutils 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-2017-18018 fixed in no fix yet
  • Low CVE-2025-5278 fixed in no fix yet
Low 2 known vulnerabilities in libgcrypt20@1.8.7-6 (postgis/postgis:16-master) Security · 2 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether postgis/postgis:16-master needs libgcrypt20 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-2018-6829 fixed in no fix yet
  • Low CVE-2024-2236 fixed in no fix yet
Low 2 known vulnerabilities in shadow@1%3A4.8.1-1%2Bdeb11u1 (postgis/postgis:16-master) Security · 2 CVEs

How to fix

No fixed version of shadow is available yet. Check whether postgis/postgis:16-master 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-2007-5686 fixed in no fix yet
  • Low CVE-2013-4235 fixed in no fix yet
Low 2 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u2 (postgis/postgis:16-master) Security · 2 CVEs

How to fix

No fixed version of util-linux is available yet. Check whether postgis/postgis:16-master needs util-linux 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-2022-0563 fixed in no fix yet
  • Low CVE-2025-14104 fixed in no fix yet
Low 2 known vulnerabilities in circl@1.3.7 (rclone/rclone:1.68) Security · 2 CVEs

How to fix

Update circl from 1.3.7 to 1.6.3 or later in rclone/rclone:1.68. 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.6.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

  • Low CVE-2026-1229 fixed in 1.6.3
  • Low CVE-2025-8556 fixed in 1.6.1
Low 2 known vulnerabilities in coreutils@9.7-3 (tons/docker-compose-docs:2.1.0) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether tons/docker-compose-docs:2.1.0 needs coreutils 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-2017-18018 fixed in no fix yet
  • Low CVE-2025-5278 fixed in no fix yet
Low 2 known vulnerabilities in util-linux@2.41-5 (tons/docker-compose-docs:2.1.0) Security · 2 CVEs

How to fix

No fixed version of util-linux is available yet. Check whether tons/docker-compose-docs:2.1.0 needs util-linux 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-2022-0563 fixed in no fix yet
  • Low CVE-2025-14104 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (dhis2/core:42) Security · 1 CVE

How to fix

No fixed version of libgcrypt20 is available yet. Check whether dhis2/core:42 needs libgcrypt20 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-2024-2236 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (dhis2/core:42) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether dhis2/core:42 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-2024-56433 fixed in no fix yet
Low 1 known vulnerability in go-redis@9.0.2#v9 (grafana/grafana:10.0.0) Security · 1 CVE

How to fix

Update go-redis from 9.0.2#v9 to 9.6.3 or later in grafana/grafana:10.0.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 9.6.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

  • Low CVE-2025-29923 fixed in 9.6.3
Low 1 known vulnerability in apt@2.2.4 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether postgis/postgis:16-master needs apt 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-2011-3374 fixed in no fix yet
Low 1 known vulnerability in gcc-10@10.2.1-6 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of gcc-10 is available yet. Check whether postgis/postgis:16-master needs gcc-10 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-4039 fixed in no fix yet
Low 1 known vulnerability in gcc-9@9.3.0-22 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of gcc-9 is available yet. Check whether postgis/postgis:16-master needs gcc-9 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-4039 fixed in no fix yet
Low 1 known vulnerability in jbigkit@2.1-3.1 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of jbigkit is available yet. Check whether postgis/postgis:16-master needs jbigkit 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-2017-9937 fixed in no fix yet
Low 1 known vulnerability in llvm-toolchain-16@1%3A16.0.6-15~deb11u2 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of llvm-toolchain-16 is available yet. Check whether postgis/postgis:16-master needs llvm-toolchain-16 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-2024-31852 fixed in no fix yet
Low 1 known vulnerability in pcre2@10.36-2%2Bdeb11u1 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of pcre2 is available yet. Check whether postgis/postgis:16-master needs pcre2 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-2022-41409 fixed in no fix yet
Low 1 known vulnerability in sed@4.7-1 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of sed is available yet. Check whether postgis/postgis:16-master needs sed 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-5958 fixed in no fix yet
Low 1 known vulnerability in tar@1.34%2Bdfsg-1%2Bdeb11u1 (postgis/postgis:16-master) Security · 1 CVE

How to fix

No fixed version of tar is available yet. Check whether postgis/postgis:16-master needs tar 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-2005-2541 fixed in no fix yet
Low 1 known vulnerability in apt@3.0.3 (tons/docker-compose-docs:2.1.0) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether tons/docker-compose-docs:2.1.0 needs apt 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-2011-3374 fixed in no fix yet
Low 1 known vulnerability in dpkg@1.22.21 (tons/docker-compose-docs:2.1.0) Security · 1 CVE

How to fix

Update dpkg from 1.22.21 to 1.22.22 or later in tons/docker-compose-docs:2.1.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.22.22); 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

  • Low CVE-2026-2219 fixed in 1.22.22
Low 1 known vulnerability in perl@5.40.1-6 (tons/docker-compose-docs:2.1.0) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether tons/docker-compose-docs:2.1.0 needs perl 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-2011-4116 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.17.4-2 (tons/docker-compose-docs:2.1.0) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether tons/docker-compose-docs:2.1.0 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-2007-5686 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 23 Apr 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.