InfraScan Cloud

Repository scan

your-priorities-app

CitizensFoundation/your-priorities-app · branch master · scanned 1 Jun 2026

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

High 472

High 34 known vulnerabilities in stdlib@1.24.5 (maxmindinc/geoipupdate) Security · 34 CVEs

How to fix

Update stdlib from 1.24.5 to 1.24.9 or later in maxmindinc/geoipupdate. 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-2026-33811 fixed in 1.25.10
  • High CVE-2026-33814 fixed in 1.25.10
  • High CVE-2026-39820 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-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • 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
  • and 14 more
High 33 known vulnerabilities in stdlib@1.24.6 (minio/mc:latest) Security · 33 CVEs

How to fix

Update stdlib from 1.24.6 to 1.24.9 or later in minio/mc:latest. 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-2026-33811 fixed in 1.25.10
  • High CVE-2026-33814 fixed in 1.25.10
  • High CVE-2026-39820 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-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • 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
  • and 13 more
High 33 known vulnerabilities in stdlib@1.24.6 (minio/minio) Security · 33 CVEs

How to fix

Update stdlib from 1.24.6 to 1.24.9 or later in minio/minio. 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-2026-33811 fixed in 1.25.10
  • High CVE-2026-33814 fixed in 1.25.10
  • High CVE-2026-39820 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-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • 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
  • and 13 more
High 33 known vulnerabilities in stdlib@1.24.6 (postgres:13) Security · 33 CVEs

How to fix

Update stdlib from 1.24.6 to 1.24.9 or later in postgres:13. 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-2026-33811 fixed in 1.25.10
  • High CVE-2026-33814 fixed in 1.25.10
  • High CVE-2026-39820 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-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • 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
  • and 13 more
High 32 known vulnerabilities in crypto@0.40.0 (minio/minio) Security · 32 CVEs

How to fix

Update crypto from 0.40.0 to 0.43.0 or later in minio/minio. 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-2025-47913 fixed in 0.43.0
  • High CVE-2026-39829 fixed in 0.52.0
  • High CVE-2026-39829 fixed in 0.52.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-39830 fixed in 0.52.0
  • High CVE-2026-39830 fixed in 0.52.0
  • High CVE-2026-39831 fixed in 0.52.0
  • High CVE-2026-39831 fixed in 0.52.0
  • High CVE-2026-39832 fixed in 0.52.0
  • High CVE-2026-39832 fixed in 0.52.0
  • High CVE-2026-39833 fixed in 0.52.0
  • High CVE-2026-39833 fixed in 0.52.0
  • High CVE-2026-39834 fixed in 0.52.0
  • High CVE-2026-39834 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • High CVE-2026-46595 fixed in 0.52.0
  • High CVE-2026-46595 fixed in 0.52.0
  • and 12 more
High 24 known vulnerabilities in openssl@1.1.1f-1ubuntu2.2 (yandex/clickhouse-server:21.3.2.5) Security · 24 CVEs

How to fix

Update openssl from 1.1.1f-1ubuntu2.2 to 1.1.1f-1ubuntu2.3 or later in yandex/clickhouse-server:21.3.2.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.1.1f-1ubuntu2.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-2021-3449 fixed in 1.1.1f-1ubuntu2.3
  • High CVE-2023-0286 fixed in 1.1.1f-1ubuntu2.17
  • High CVE-2022-0778 fixed in 1.1.1f-1ubuntu2.12
  • High CVE-2021-3711 fixed in 1.1.1f-1ubuntu2.8
  • Medium CVE-2022-2097 fixed in 1.1.1f-1ubuntu2.16
  • Medium CVE-2022-4304 fixed in 1.1.1f-1ubuntu2.17
  • Medium CVE-2023-2650 fixed in 1.1.1f-1ubuntu2.19
  • Medium CVE-2022-1292 fixed in 1.1.1f-1ubuntu2.13
  • Medium CVE-2022-2068 fixed in 1.1.1f-1ubuntu2.15
  • Medium CVE-2021-3712 fixed in 1.1.1f-1ubuntu2.8
  • Medium CVE-2022-4450 fixed in 1.1.1f-1ubuntu2.17
  • Medium CVE-2023-0215 fixed in 1.1.1f-1ubuntu2.17
  • Low CVE-2024-13176 fixed in 1.1.1f-1ubuntu2.24
  • Low CVE-2024-2511 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-4741 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-5535 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-9143 fixed in 1.1.1f-1ubuntu2.24
  • Low CVE-2023-0465 fixed in 1.1.1f-1ubuntu2.18
  • Low CVE-2023-0466 fixed in 1.1.1f-1ubuntu2.18
  • Low CVE-2023-3446 fixed in 1.1.1f-1ubuntu2.20
  • and 4 more
High 23 known vulnerabilities in openssl@3.5.0-r0 (maxmindinc/geoipupdate) Security · 23 CVEs

How to fix

Update openssl from 3.5.0-r0 to 3.5.5-r0 or later in maxmindinc/geoipupdate. 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-2025-9230 fixed in 3.5.4-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-2026-28387 fixed in 3.5.6-r0
  • High CVE-2025-15467 fixed in 3.5.5-r0
  • High CVE-2026-31789 fixed in 3.5.6-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-9232 fixed in 3.5.4-r0
  • Medium CVE-2025-11187 fixed in 3.5.5-r0
  • and 3 more
High 20 known vulnerabilities in openssl@1.1.1f-1ubuntu2.12 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 20 CVEs

How to fix

Update openssl from 1.1.1f-1ubuntu2.12 to 1.1.1f-1ubuntu2.17 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1f-1ubuntu2.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

  • High CVE-2023-0286 fixed in 1.1.1f-1ubuntu2.17
  • Medium CVE-2022-2097 fixed in 1.1.1f-1ubuntu2.16
  • Medium CVE-2022-4304 fixed in 1.1.1f-1ubuntu2.17
  • Medium CVE-2023-2650 fixed in 1.1.1f-1ubuntu2.19
  • Medium CVE-2022-1292 fixed in 1.1.1f-1ubuntu2.13
  • Medium CVE-2022-2068 fixed in 1.1.1f-1ubuntu2.15
  • Medium CVE-2022-4450 fixed in 1.1.1f-1ubuntu2.17
  • Medium CVE-2023-0215 fixed in 1.1.1f-1ubuntu2.17
  • Low CVE-2024-13176 fixed in 1.1.1f-1ubuntu2.24
  • Low CVE-2024-2511 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-4741 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-5535 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-9143 fixed in 1.1.1f-1ubuntu2.24
  • Low CVE-2023-0465 fixed in 1.1.1f-1ubuntu2.18
  • Low CVE-2023-0466 fixed in 1.1.1f-1ubuntu2.18
  • Low CVE-2023-3446 fixed in 1.1.1f-1ubuntu2.20
  • Low CVE-2023-3817 fixed in 1.1.1f-1ubuntu2.20
  • Low CVE-2023-5678 fixed in 1.1.1f-1ubuntu2.21
  • Low CVE-2024-0727 fixed in 1.1.1f-1ubuntu2.21
  • Low CVE-2023-0464 fixed in 1.1.1f-1ubuntu2.18
High 20 known vulnerabilities in openssl@3.5.1-1%2Bdeb13u1 (postgres:13) Security · 20 CVEs

How to fix

Update openssl from 3.5.1-1%2Bdeb13u1 to 3.5.4-1~deb13u2 or later in postgres:13. 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-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
  • High CVE-2026-28387 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-2026-2673 fixed in 3.5.5-1~deb13u2
  • Low CVE-2026-31789 fixed in 3.5.5-1~deb13u2
  • Low CVE-2026-31790 fixed in 3.5.5-1~deb13u2
High 18 known vulnerabilities in net@0.39.0 (minio/minio) Security · 18 CVEs

How to fix

Update net from 0.39.0 to 0.53.0 or later in minio/minio. 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
  • High CVE-2026-33814 fixed in 0.53.0
  • High CVE-2026-39821 fixed in 0.55.0
  • High CVE-2026-39821 fixed in 0.55.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2026-25681 fixed in 0.55.0
  • Medium CVE-2026-25681 fixed in 0.55.0
  • Medium CVE-2026-27136 fixed in 0.55.0
  • Medium CVE-2026-27136 fixed in 0.55.0
  • Medium CVE-2026-42502 fixed in 0.55.0
  • Medium CVE-2026-42502 fixed in 0.55.0
  • Medium CVE-2026-42506 fixed in 0.55.0
  • Medium CVE-2026-42506 fixed in 0.55.0
  • Medium CVE-2026-25680 fixed in 0.55.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 16 known vulnerabilities in crypto@0.40.0 (minio/mc:latest) Security · 16 CVEs

How to fix

Update crypto from 0.40.0 to 0.43.0 or later in minio/mc:latest. 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-39829 fixed in 0.52.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-39830 fixed in 0.52.0
  • High CVE-2026-39831 fixed in 0.52.0
  • High CVE-2026-39832 fixed in 0.52.0
  • High CVE-2026-39833 fixed in 0.52.0
  • High CVE-2026-39834 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • High CVE-2026-46595 fixed in 0.52.0
  • Medium CVE-2025-47914 fixed in 0.45.0
  • Medium CVE-2025-58181 fixed in 0.45.0
  • Medium CVE-2026-39835 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
  • Medium CVE-2026-39828 fixed in 0.52.0
  • Medium CVE-2026-39827 fixed in 0.52.0
High 15 known vulnerabilities in gnutls28@3.8.9-3 (postgres:13) Security · 15 CVEs

How to fix

Update gnutls28 from 3.8.9-3 to 3.8.9-3+deb13u4 or later in postgres:13. 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.9-3+deb13u4); 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-42010 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-42012 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-42011 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-33845 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-33846 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-42009 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-42013 fixed in 3.8.9-3+deb13u4
  • High CVE-2026-5260 fixed in 3.8.9-3+deb13u4
  • Medium CVE-2025-9820 fixed in 3.8.9-3+deb13u1
  • Medium CVE-2025-14831 fixed in 3.8.9-3+deb13u2
  • Medium CVE-2026-42015 fixed in 3.8.9-3+deb13u4
  • Medium CVE-2026-3833 fixed in 3.8.9-3+deb13u4
  • Low CVE-2011-3389 fixed in no fix yet
  • Low CVE-2026-3832 fixed in 3.8.9-3+deb13u4
  • Low CVE-2026-5419 fixed in 3.8.9-3+deb13u4
High 13 known vulnerabilities in elasticsearch@7.17.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 13 CVEs

How to fix

Update elasticsearch from 7.17.2 to 7.17.13 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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 7.17.13); 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-31418 fixed in 7.17.13
  • Medium CVE-2023-31417 fixed in 7.17.13
  • Medium CVE-2023-49921 fixed in 7.17.16
  • Medium CVE-2024-23450 fixed in 7.17.19
  • Medium CVE-2024-52981 fixed in 7.17.24
  • Medium CVE-2025-37727 fixed in 8.18.8
  • Medium CVE-2023-31419 fixed in 7.17.13
  • Medium CVE-2023-46673 fixed in 7.17.14
  • Medium CVE-2024-43709 fixed in 7.17.21
  • Medium CVE-2024-52979 fixed in 7.17.25
  • Medium CVE-2024-52980 fixed in 8.15.1
  • Medium CVE-2025-37731 fixed in 8.19.8
  • Medium CVE-2024-23444 fixed in 7.17.23
High 13 known vulnerabilities in glibc@2.41-12 (postgres:13) Security · 13 CVEs

How to fix

Update glibc from 2.41-12 to 2.41-12+deb13u2 or later in postgres:13. 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-4046 fixed in 2.41-12+deb13u3
  • 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
  • Low CVE-2026-4437 fixed in 2.41-12+deb13u3
  • Low CVE-2026-4438 fixed in 2.41-12+deb13u3
High 12 known vulnerabilities in netty-codec-http@4.1.66.Final (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 12 CVEs

How to fix

Update netty-codec-http from 4.1.66.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1.133.Final); 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-42584 fixed in 4.1.133.Final
  • High CVE-2026-33870 fixed in 4.1.132.Final
  • High CVE-2026-42587 fixed in 4.1.133.Final
  • Medium CVE-2024-29025 fixed in 4.1.108.Final
  • Medium CVE-2026-41417 fixed in 4.1.133.Final
  • Medium CVE-2022-24823 fixed in 4.1.77.Final
  • Medium CVE-2026-42581 fixed in 4.1.133.Final
  • Medium CVE-2021-43797 fixed in 4.1.71.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Medium CVE-2026-42580 fixed in 4.1.133.Final
  • Medium CVE-2026-42585 fixed in 4.1.133.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
High 12 known vulnerabilities in jq@1.8.0-r0 (maxmindinc/geoipupdate) Security · 12 CVEs

How to fix

No fixed version of jq is available yet. Check whether maxmindinc/geoipupdate needs jq 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-32316 fixed in no fix yet
  • Medium CVE-2026-43895 fixed in no fix yet
  • Medium CVE-2026-40612 fixed in no fix yet
  • Medium CVE-2026-44777 fixed in no fix yet
  • Medium CVE-2025-49014 fixed in 1.8.1-r0
  • Medium CVE-2026-41256 fixed in no fix yet
  • Medium CVE-2026-33947 fixed in no fix yet
  • Medium CVE-2026-43894 fixed in no fix yet
  • Medium CVE-2026-43896 fixed in no fix yet
  • Medium CVE-2026-41257 fixed in no fix yet
  • Medium CVE-2026-39979 fixed in no fix yet
  • Low CVE-2026-33948 fixed in no fix yet
High 10 known vulnerabilities in openssl@1.1.1q-r0 (plausible/analytics:master) Security · 10 CVEs

How to fix

Update openssl from 1.1.1q-r0 to 1.1.1t-r0 or later in plausible/analytics: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.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-r2
  • 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 9 known vulnerabilities in net@0.42.0 (minio/mc:latest) Security · 9 CVEs

How to fix

Update net from 0.42.0 to 0.53.0 or later in minio/mc:latest. 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
  • High CVE-2026-39821 fixed in 0.55.0
  • Medium CVE-2025-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
  • Medium CVE-2026-25681 fixed in 0.55.0
  • Medium CVE-2026-27136 fixed in 0.55.0
  • Medium CVE-2026-42502 fixed in 0.55.0
  • Medium CVE-2026-42506 fixed in 0.55.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 9 known vulnerabilities in minio@0.0.0-20250907161309-07c3a429bfed%2Bdirty (minio/minio) Security · 9 CVEs

How to fix

No fixed version of minio is available yet. Check whether minio/minio needs minio 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-34204 fixed in no fix yet
  • High CVE-2026-39414 fixed in no fix yet
  • High CVE-2018-1000538 fixed in v2018.05.16
  • High CVE-2025-62506 fixed in 0.0.0-20251015170045-c1a49490c78e
  • High CVE-2026-40344 fixed in no fix yet
  • High CVE-2026-41145 fixed in no fix yet
  • High CVE-2026-33419 fixed in no fix yet
  • High CVE-2026-33322 fixed in no fix yet
  • Medium CVE-2026-42600 fixed in 0.0.0-20260414213245
High 8 known vulnerabilities in binutils@2.45.1-r0 (certbot/certbot) Security · 8 CVEs

How to fix

No fixed version of binutils is available yet. Check whether certbot/certbot needs binutils 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-69649 fixed in no fix yet
  • High CVE-2025-69650 fixed in no fix yet
  • High CVE-2026-6846 fixed in no fix yet
  • Medium CVE-2025-69644 fixed in no fix yet
  • Medium CVE-2025-69651 fixed in no fix yet
  • Medium CVE-2025-69647 fixed in no fix yet
  • Medium CVE-2025-69648 fixed in no fix yet
  • Medium CVE-2025-69652 fixed in no fix yet
High 8 known vulnerabilities in perl@5.40.1-6 (postgres:13) Security · 8 CVEs

How to fix

No fixed version of perl is available yet. Check whether postgres:13 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

  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-42497 fixed in no fix yet
  • High CVE-2026-48959 fixed in no fix yet
  • High CVE-2026-9538 fixed in no fix yet
  • High CVE-2026-42496 fixed in no fix yet
  • Medium CVE-2025-15649 fixed in no fix yet
  • Low CVE-2011-4116 fixed in no fix yet
  • Low CVE-2026-48961 fixed in no fix yet
High 7 known vulnerabilities in snakeyaml@1.26 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 7 CVEs

How to fix

Update snakeyaml from 1.26 to 1.31 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.31); 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-25857 fixed in 1.31
  • High CVE-2022-1471 fixed in 2.0
  • Medium CVE-2022-38750 fixed in 1.31
  • Medium CVE-2022-38749 fixed in 1.31
  • Medium CVE-2022-38751 fixed in 1.31
  • Medium CVE-2022-38752 fixed in 1.32
  • Medium CVE-2022-41854 fixed in 1.32
High 5 known vulnerabilities in jackson-databind@2.10.4 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 5 CVEs

How to fix

Update jackson-databind from 2.10.4 to 2.10.5.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.10.5.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

  • High CVE-2020-25649 fixed in 2.10.5.1
  • High CVE-2020-36518 fixed in 2.12.6.1
  • High CVE-2021-46877 fixed in 2.12.6
  • High CVE-2022-42003 fixed in 2.12.7.1
  • High CVE-2022-42004 fixed in 2.12.7.1
High 5 known vulnerabilities in systemd@245.4-4ubuntu3.4 (yandex/clickhouse-server:21.3.2.5) Security · 5 CVEs

How to fix

Update systemd from 245.4-4ubuntu3.4 to 245.4-4ubuntu3.10 or later in yandex/clickhouse-server:21.3.2.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 245.4-4ubuntu3.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

  • High CVE-2021-33910 fixed in 245.4-4ubuntu3.10
  • Medium CVE-2021-3997 fixed in 245.4-4ubuntu3.15
  • Medium CVE-2022-3821 fixed in 245.4-4ubuntu3.20
  • Medium CVE-2022-4415 fixed in 245.4-4ubuntu3.20
  • Low CVE-2020-13529 fixed in 245.4-4ubuntu3.10
High 4 known vulnerabilities in json-smart@2.4.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 4 CVEs

How to fix

Update json-smart from 2.4.2 to 2.4.4 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.4.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

  • High CVE-2021-31684 fixed in 2.4.4
  • High CVE-2021-31684 fixed in 1.3.3
  • High CVE-2023-1370 fixed in 2.4.9
  • High CVE-2023-1370 fixed in 2.4.9
High 4 known vulnerabilities in netty-codec@4.1.66.Final (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 4 CVEs

How to fix

Update netty-codec from 4.1.66.Final to 4.1.68.Final or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1.68.Final); 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-2021-37136 fixed in 4.1.68.Final
  • High CVE-2021-37137 fixed in 4.1.68.Final
  • High CVE-2026-42583 fixed in 4.1.133.Final
  • Medium CVE-2025-58057 fixed in 4.1.125.Final
High 4 known vulnerabilities in protobuf-java@3.16.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 4 CVEs

How to fix

Update protobuf-java from 3.16.1 to 3.16.3 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.16.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-2022-3509 fixed in 3.16.3
  • High CVE-2022-3510 fixed in 3.16.3
  • High CVE-2024-7254 fixed in 3.25.5
  • Medium CVE-2022-3171 fixed in 3.16.3
High 4 known vulnerabilities in glibc@2.34-168.el9_6.23 (minio/mc:latest) Security · 4 CVEs

How to fix

No fixed version of glibc is available yet. Check whether minio/mc:latest needs glibc 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-0861 fixed in no fix yet
  • Medium CVE-2026-0915 fixed in no fix yet
  • Low CVE-2025-15281 fixed in no fix yet
High 4 known vulnerabilities in prometheus@0.303.0 (minio/mc:latest) Security · 4 CVEs

How to fix

Update prometheus from 0.303.0 to 0.311.3 or later in minio/mc:latest. 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.311.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-42151 fixed in 0.311.3
  • High CVE-2026-42154 fixed in 0.311.3
  • Medium CVE-2026-44903 fixed in 0.311.3
  • Medium CVE-2026-40179 fixed in 0.311.2-0.20260410083055-07c6232d159b
High 4 known vulnerabilities in glibc@2.34-168.el9_6.23 (minio/minio) Security · 4 CVEs

How to fix

No fixed version of glibc is available yet. Check whether minio/minio needs glibc 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-0861 fixed in no fix yet
  • Medium CVE-2026-0915 fixed in no fix yet
  • Low CVE-2025-15281 fixed in no fix yet
High 4 known vulnerabilities in prometheus@0.303.0 (minio/minio) Security · 4 CVEs

How to fix

Update prometheus from 0.303.0 to 0.311.3 or later in minio/minio. 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.311.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-42151 fixed in 0.311.3
  • High CVE-2026-42154 fixed in 0.311.3
  • Medium CVE-2026-44903 fixed in 0.311.3
  • Medium CVE-2026-40179 fixed in 0.311.2-0.20260410083055-07c6232d159b
High 3 known vulnerabilities in jackson-core@2.10.4 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update jackson-core from 2.10.4 to 2.15.0 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.15.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-52999 fixed in 2.15.0
  • Medium CVE-2025-49128 fixed in 2.13.0
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
High 3 known vulnerabilities in nghttp2@1.40.0-1build1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update nghttp2 from 1.40.0-1build1 to 1.40.0-1ubuntu0.2 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.40.0-1ubuntu0.2); 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-44487 fixed in 1.40.0-1ubuntu0.2
  • Medium CVE-2024-28182 fixed in 1.40.0-1ubuntu0.3
  • Medium CVE-2020-11080 fixed in 1.40.0-1ubuntu0.1
High 2 known vulnerabilities in urllib3@2.6.3 (certbot/certbot) Security · 2 CVEs

How to fix

Update urllib3 from 2.6.3 to 2.7.0 or later in certbot/certbot. 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.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-2026-44431 fixed in 2.7.0
  • High CVE-2026-44432 fixed in 2.7.0
High 2 known vulnerabilities in lz4-java@1.8.0 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

No fixed version of lz4-java is available yet. Check whether docker.elastic.co/elasticsearch/elasticsearch:7.17.2 needs lz4-java 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-66566 fixed in no fix yet
  • High CVE-2025-12183 fixed in 1.8.1
High 2 known vulnerabilities in nimbus-jose-jwt@9.8.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update nimbus-jose-jwt from 9.8.1 to 9.37.2 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.37.2); 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-52428 fixed in 9.37.2
  • Medium CVE-2025-53864 fixed in 10.0.2
High 2 known vulnerabilities in xmlsec@2.1.4 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update xmlsec from 2.1.4 to 2.1.7 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1.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-2021-40690 fixed in 2.1.7
  • Medium CVE-2023-44483 fixed in 2.2.6
High 2 known vulnerabilities in musl@1.2.5-r10 (maxmindinc/geoipupdate) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r10 to 1.2.5-r12 or later in maxmindinc/geoipupdate. 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.5-r12); 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.5-r12
  • Medium CVE-2026-6042 fixed in 1.2.5-r11
High 2 known vulnerabilities in grpc@1.72.0 (minio/minio) Security · 2 CVEs

How to fix

Update grpc from 1.72.0 to 1.79.3 or later in minio/minio. 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.79.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-33186 fixed in 1.79.3
  • High CVE-2026-33186 fixed in 1.79.3
High 2 known vulnerabilities in sdk@1.35.0 (minio/minio) Security · 2 CVEs

How to fix

Update sdk from 1.35.0 to 1.40.0 or later in minio/minio. 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.40.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-24051 fixed in 1.40.0
  • High CVE-2026-39883 fixed in 1.43.0

and 10 more groups with 12 findings

Medium 369

Medium 120 known vulnerabilities in vim@2%3A8.1.2269-1ubuntu5.7 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 120 CVEs

How to fix

Update vim from 2%3A8.1.2269-1ubuntu5.7 to 2:8.1.2269-1ubuntu5.25 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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:8.1.2269-1ubuntu5.25); 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-2024-43802 fixed in 2:8.1.2269-1ubuntu5.25
  • Medium CVE-2025-26603 fixed in 2:8.1.2269-1ubuntu5.32
  • Medium CVE-2023-48231 fixed in 2:8.1.2269-1ubuntu5.21
  • Medium CVE-2024-43374 fixed in 2:8.1.2269-1ubuntu5.24
  • Medium CVE-2024-41957 fixed in 2:8.1.2269-1ubuntu5.24
  • Medium CVE-2022-0319 fixed in 2:8.1.2269-1ubuntu5.14
  • Medium CVE-2022-0714 fixed in 2:8.1.2269-1ubuntu5.14
  • Medium CVE-2022-1420 fixed in 2:8.1.2269-1ubuntu5.8
  • Medium CVE-2022-1674 fixed in 2:8.1.2269-1ubuntu5.13
  • Medium CVE-2022-2923 fixed in 2:8.1.2269-1ubuntu5.13
  • Medium CVE-2022-2980 fixed in 2:8.1.2269-1ubuntu5.13
  • Medium CVE-2023-1264 fixed in 2:8.1.2269-1ubuntu5.12
  • Medium CVE-2023-2609 fixed in 2:8.1.2269-1ubuntu5.15
  • Medium CVE-2023-46246 fixed in 2:8.1.2269-1ubuntu5.21
  • Medium CVE-2023-5441 fixed in 2:8.1.2269-1ubuntu5.20
  • Medium CVE-2025-22134 fixed in 2:8.1.2269-1ubuntu5.30
  • Medium CVE-2025-24014 fixed in 2:8.1.2269-1ubuntu5.31
  • Medium CVE-2022-0213 fixed in 2:8.1.2269-1ubuntu5.14
  • Medium CVE-2023-1170 fixed in 2:8.1.2269-1ubuntu5.12
  • Medium CVE-2023-1175 fixed in 2:8.1.2269-1ubuntu5.12
  • and 100 more
Medium 25 known vulnerabilities in curl@7.68.0-1ubuntu2.7 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 25 CVEs

How to fix

Update curl from 7.68.0-1ubuntu2.7 to 7.68.0-1ubuntu2.22 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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 7.68.0-1ubuntu2.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

  • Medium CVE-2024-2398 fixed in 7.68.0-1ubuntu2.22
  • Medium CVE-2024-8096 fixed in 7.68.0-1ubuntu2.24
  • Medium CVE-2022-27774 fixed in 7.68.0-1ubuntu2.10
  • Medium CVE-2022-32208 fixed in 7.68.0-1ubuntu2.12
  • Medium CVE-2022-43552 fixed in 7.68.0-1ubuntu2.15
  • Medium CVE-2023-27535 fixed in 7.68.0-1ubuntu2.18
  • Medium CVE-2022-32206 fixed in 7.68.0-1ubuntu2.12
  • Medium CVE-2023-23916 fixed in 7.68.0-1ubuntu2.16
  • Medium CVE-2023-46218 fixed in 7.68.0-1ubuntu2.21
  • Medium CVE-2024-7264 fixed in 7.68.0-1ubuntu2.23
  • Medium CVE-2022-27782 fixed in 7.68.0-1ubuntu2.11
  • Medium CVE-2022-22576 fixed in 7.68.0-1ubuntu2.10
  • Medium CVE-2022-32221 fixed in 7.68.0-1ubuntu2.14
  • Low CVE-2024-11053 fixed in 7.68.0-1ubuntu2.25
  • Low CVE-2022-35252 fixed in 7.68.0-1ubuntu2.13
  • Low CVE-2023-28322 fixed in 7.68.0-1ubuntu2.19
  • Low CVE-2023-38546 fixed in 7.68.0-1ubuntu2.20
  • Low CVE-2023-27538 fixed in 7.68.0-1ubuntu2.18
  • Low CVE-2023-27536 fixed in 7.68.0-1ubuntu2.18
  • Low CVE-2023-28321 fixed in 7.68.0-1ubuntu2.19
  • and 5 more
Medium 20 known vulnerabilities in aa_ER@saaho (yandex/clickhouse-server:21.3.2.5) Security · 20 CVEs

How to fix

Update aa_ER from saaho to 2.31-0ubuntu9.15 or later in yandex/clickhouse-server:21.3.2.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 2.31-0ubuntu9.15); 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-2024-2961 fixed in 2.31-0ubuntu9.15
  • Medium CVE-2024-33599 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33600 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33601 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33602 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2025-0395 fixed in 2.31-0ubuntu9.17
  • Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
  • Medium CVE-2021-3999 fixed in 2.31-0ubuntu9.7
  • Low CVE-2021-27645 fixed in 2.31-0ubuntu9.7
  • Low CVE-2020-29562 fixed in 2.31-0ubuntu9.7
  • Low CVE-2020-27618 fixed in 2.31-0ubuntu9.7
  • Low CVE-2016-10228 fixed in 2.31-0ubuntu9.7
  • Low CVE-2019-25013 fixed in 2.31-0ubuntu9.7
  • Low CVE-2023-4806 fixed in 2.31-0ubuntu9.14
  • Low CVE-2023-4813 fixed in 2.31-0ubuntu9.14
  • Low CVE-2021-3326 fixed in 2.31-0ubuntu9.7
  • Low CVE-2020-6096 fixed in 2.31-0ubuntu9.7
  • Low CVE-2021-35942 fixed in 2.31-0ubuntu9.7
  • Low CVE-2022-23218 fixed in 2.31-0ubuntu9.7
  • Low CVE-2022-23219 fixed in 2.31-0ubuntu9.7
Medium 11 known vulnerabilities in krb5@1.17-6ubuntu4.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 11 CVEs

How to fix

Update krb5 from 1.17-6ubuntu4.1 to 1.17-6ubuntu4.9 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.17-6ubuntu4.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

  • Medium CVE-2025-24528 fixed in 1.17-6ubuntu4.9
  • Medium CVE-2025-3576 fixed in 1.17-6ubuntu4.11
  • Medium CVE-2021-37750 fixed in 1.17-6ubuntu4.3
  • Medium CVE-2023-36054 fixed in 1.17-6ubuntu4.4
  • Medium CVE-2021-36222 fixed in 1.17-6ubuntu4.3
  • Medium CVE-2024-37370 fixed in 1.17-6ubuntu4.6
  • Medium CVE-2022-42898 fixed in 1.17-6ubuntu4.2
  • Medium CVE-2024-3596 fixed in 1.17-6ubuntu4.8
  • Medium CVE-2024-37371 fixed in 1.17-6ubuntu4.6
  • Low CVE-2024-26458 fixed in 1.17-6ubuntu4.9
  • Low CVE-2024-26461 fixed in 1.17-6ubuntu4.9
Medium 9 known vulnerabilities in glibc@2.31-0ubuntu9.7 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 9 CVEs

How to fix

Update glibc from 2.31-0ubuntu9.7 to 2.31-0ubuntu9.15 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.31-0ubuntu9.15); 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-2024-2961 fixed in 2.31-0ubuntu9.15
  • Medium CVE-2024-33599 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33600 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33601 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2024-33602 fixed in 2.31-0ubuntu9.16
  • Medium CVE-2025-0395 fixed in 2.31-0ubuntu9.17
  • Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
  • Low CVE-2023-4806 fixed in 2.31-0ubuntu9.14
  • Low CVE-2023-4813 fixed in 2.31-0ubuntu9.14
Medium 9 known vulnerabilities in gnutls28@3.6.13-2ubuntu1.3 (yandex/clickhouse-server:21.3.2.5) Security · 9 CVEs

How to fix

Update gnutls28 from 3.6.13-2ubuntu1.3 to 3.6.13-2ubuntu1.12 or later in yandex/clickhouse-server:21.3.2.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.6.13-2ubuntu1.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

  • Medium CVE-2024-12243 fixed in 3.6.13-2ubuntu1.12
  • Medium CVE-2024-28834 fixed in 3.6.13-2ubuntu1.11
  • Medium CVE-2023-5981 fixed in 3.6.13-2ubuntu1.9
  • Medium CVE-2023-0361 fixed in 3.6.13-2ubuntu1.8
  • Medium CVE-2022-2509 fixed in 3.6.13-2ubuntu1.7
  • Medium CVE-2024-0553 fixed in 3.6.13-2ubuntu1.10
  • Low CVE-2021-4209 fixed in 3.6.13-2ubuntu1.7
  • Low CVE-2021-20231 fixed in 3.6.13-2ubuntu1.6
  • Low CVE-2021-20232 fixed in 3.6.13-2ubuntu1.6
Medium 8 known vulnerabilities in heimdal@7.7.0%2Bdfsg-1ubuntu1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 8 CVEs

How to fix

Update heimdal from 7.7.0%2Bdfsg-1ubuntu1 to 7.7.0+dfsg-1ubuntu1.3 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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 7.7.0+dfsg-1ubuntu1.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-2022-3437 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2021-44758 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2022-3116 fixed in 7.7.0+dfsg-1ubuntu1.1
  • Medium CVE-2022-41916 fixed in 7.7.0+dfsg-1ubuntu1.2
  • Medium CVE-2022-45142 fixed in 7.7.0+dfsg-1ubuntu1.4
  • Medium CVE-2022-42898 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2022-44640 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Low CVE-2021-3671 fixed in 7.7.0+dfsg-1ubuntu1.1
Medium 8 known vulnerabilities in sqlite3@3.31.1-4ubuntu0.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 8 CVEs

How to fix

Update sqlite3 from 3.31.1-4ubuntu0.2 to 3.31.1-4ubuntu0.7 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.31.1-4ubuntu0.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-52099 fixed in 3.31.1-4ubuntu0.7
  • Medium CVE-2025-29088 fixed in 3.31.1-4ubuntu0.7
  • Medium CVE-2023-7104 fixed in 3.31.1-4ubuntu0.6
  • Medium CVE-2020-35525 fixed in 3.31.1-4ubuntu0.4
  • Medium CVE-2022-35737 fixed in 3.31.1-4ubuntu0.5
  • Medium CVE-2020-35527 fixed in 3.31.1-4ubuntu0.4
  • Medium CVE-2021-20223 fixed in 3.31.1-4ubuntu0.4
  • Low CVE-2021-36690 fixed in 3.31.1-4ubuntu0.3
Medium 8 known vulnerabilities in systemd@257.8-1~deb13u2 (postgres:13) Security · 8 CVEs

How to fix

Update systemd from 257.8-1~deb13u2 to 257.13-1~deb13u1 or later in postgres:13. 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 257.13-1~deb13u1); 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-29111 fixed in 257.13-1~deb13u1
  • Medium CVE-2026-40225 fixed in 257.13-1~deb13u1
  • Medium CVE-2026-40226 fixed in 257.13-1~deb13u1
  • Medium CVE-2026-4105 fixed in 257.13-1~deb13u1
  • 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
Medium 8 known vulnerabilities in heimdal@7.7.0%2Bdfsg-1ubuntu1 (yandex/clickhouse-server:21.3.2.5) Security · 8 CVEs

How to fix

Update heimdal from 7.7.0%2Bdfsg-1ubuntu1 to 7.7.0+dfsg-1ubuntu1.3 or later in yandex/clickhouse-server:21.3.2.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 7.7.0+dfsg-1ubuntu1.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-2022-3437 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2021-44758 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2022-3116 fixed in 7.7.0+dfsg-1ubuntu1.1
  • Medium CVE-2022-41916 fixed in 7.7.0+dfsg-1ubuntu1.2
  • Medium CVE-2022-45142 fixed in 7.7.0+dfsg-1ubuntu1.4
  • Medium CVE-2022-42898 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Medium CVE-2022-44640 fixed in 7.7.0+dfsg-1ubuntu1.3
  • Low CVE-2021-3671 fixed in 7.7.0+dfsg-1ubuntu1.1
Medium 8 known vulnerabilities in sqlite3@3.31.1-4ubuntu0.2 (yandex/clickhouse-server:21.3.2.5) Security · 8 CVEs

How to fix

Update sqlite3 from 3.31.1-4ubuntu0.2 to 3.31.1-4ubuntu0.7 or later in yandex/clickhouse-server:21.3.2.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.31.1-4ubuntu0.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-52099 fixed in 3.31.1-4ubuntu0.7
  • Medium CVE-2025-29088 fixed in 3.31.1-4ubuntu0.7
  • Medium CVE-2023-7104 fixed in 3.31.1-4ubuntu0.6
  • Medium CVE-2020-35525 fixed in 3.31.1-4ubuntu0.4
  • Medium CVE-2022-35737 fixed in 3.31.1-4ubuntu0.5
  • Medium CVE-2020-35527 fixed in 3.31.1-4ubuntu0.4
  • Medium CVE-2021-20223 fixed in 3.31.1-4ubuntu0.4
  • Low CVE-2021-36690 fixed in 3.31.1-4ubuntu0.3
Medium 7 known vulnerabilities in bcprov-jdk15on@1.64 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 7 CVEs

How to fix

Update bcprov-jdk15on from 1.64 to 1.66 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.66); 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-2020-15522 fixed in 1.66
  • 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-2023-33202 fixed in no fix yet
  • Medium CVE-2024-30171 fixed in 1.78
  • Medium CVE-2024-34447 fixed in 1.78
Medium 7 known vulnerabilities in gnutls28@3.6.13-2ubuntu1.6 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 7 CVEs

How to fix

Update gnutls28 from 3.6.13-2ubuntu1.6 to 3.6.13-2ubuntu1.12 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.6.13-2ubuntu1.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

  • Medium CVE-2024-12243 fixed in 3.6.13-2ubuntu1.12
  • Medium CVE-2024-28834 fixed in 3.6.13-2ubuntu1.11
  • Medium CVE-2023-5981 fixed in 3.6.13-2ubuntu1.9
  • Medium CVE-2023-0361 fixed in 3.6.13-2ubuntu1.8
  • Medium CVE-2022-2509 fixed in 3.6.13-2ubuntu1.7
  • Medium CVE-2024-0553 fixed in 3.6.13-2ubuntu1.10
  • Low CVE-2021-4209 fixed in 3.6.13-2ubuntu1.7
Medium 5 known vulnerabilities in guava@27.1-jre (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 5 CVEs

How to fix

Update guava from 27.1-jre to 32.0.0-android or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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 32.0.0-android); 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-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2018-10237 fixed in 24.1.1-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
Medium 5 known vulnerabilities in libssh@0.9.3-2ubuntu2.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 5 CVEs

How to fix

Update libssh from 0.9.3-2ubuntu2.2 to 0.9.3-2ubuntu2.5 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.9.3-2ubuntu2.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-2023-6004 fixed in 0.9.3-2ubuntu2.5
  • Medium CVE-2023-6918 fixed in 0.9.3-2ubuntu2.5
  • Medium CVE-2023-48795 fixed in 0.9.3-2ubuntu2.4
  • Medium CVE-2023-1667 fixed in 0.9.3-2ubuntu2.3
  • Medium CVE-2023-2283 fixed in 0.9.3-2ubuntu2.3
Medium 5 known vulnerabilities in krb5@1.21.3-5 (postgres:13) Security · 5 CVEs

How to fix

Update krb5 from 1.21.3-5 to 1.21.3-5+deb13u1 or later in postgres:13. 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.21.3-5+deb13u1); 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-40355 fixed in 1.21.3-5+deb13u1
  • Medium CVE-2026-40356 fixed in 1.21.3-5+deb13u1
  • 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
Medium 4 known vulnerabilities in bc-fips@1.0.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 4 CVEs

How to fix

Update bc-fips from 1.0.2 to 1.0.2.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.0.2.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-2020-15522 fixed in 1.0.2.1
  • Medium CVE-2024-29857 fixed in 1.0.2.5
  • Medium CVE-2022-45146 fixed in 1.0.2.4
  • Medium CVE-2025-8885 fixed in 2.1.0
Medium 4 known vulnerabilities in libxml2@2.12.7%2Bdfsg%2Breally2.9.14-2.1%2Bdeb13u1 (postgres:13) Security · 4 CVEs

How to fix

Update libxml2 from 2.12.7%2Bdfsg%2Breally2.9.14-2.1%2Bdeb13u1 to 2.12.7+dfsg+really2.9.14-2.1+deb13u2 or later in postgres:13. 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.12.7+dfsg+really2.9.14-2.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

  • Medium CVE-2025-9714 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u2
  • Medium CVE-2026-6732 fixed in no fix yet
  • Low CVE-2025-8732 fixed in no fix yet
  • Low CVE-2026-1757 fixed in no fix yet
Medium 3 known vulnerabilities in astral-tokio-tar@0.6.0 (certbot/certbot) Security · 3 CVEs

How to fix

Update astral-tokio-tar from 0.6.0 to 0.6.1 or later in certbot/certbot. 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.6.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 GHSA-fp55-jw48-c537 fixed in 0.6.1
  • Medium GHSA-3cv2-h65g-fgmm fixed in 0.6.2
  • Low GHSA-xx64-wwv2-hcqq fixed in 0.6.1
Medium 3 known vulnerabilities in log4j-core@2.17.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update log4j-core from 2.17.1 to 2.25.3 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.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-68161 fixed in 2.25.3
  • Medium CVE-2026-34477 fixed in 2.25.4
  • Medium CVE-2026-34480 fixed in 2.25.4
Medium 3 known vulnerabilities in ncurses@6.2-0ubuntu2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update ncurses from 6.2-0ubuntu2 to 6.2-0ubuntu2.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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-0ubuntu2.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-2023-29491 fixed in 6.2-0ubuntu2.1
  • Low CVE-2022-29458 fixed in 6.2-0ubuntu2.1
  • Low CVE-2021-39537 fixed in 6.2-0ubuntu2.1
Medium 3 known vulnerabilities in netty-common@4.1.66.Final (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update netty-common from 4.1.66.Final to 4.1.115.Final or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1.115.Final); 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-2024-47535 fixed in 4.1.115.Final
  • Medium CVE-2022-24823 fixed in 4.1.77.Final
  • Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 3 known vulnerabilities in perl@5.30.0-9ubuntu0.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update perl from 5.30.0-9ubuntu0.2 to 5.30.0-9ubuntu0.3 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.30.0-9ubuntu0.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-2020-16156 fixed in 5.30.0-9ubuntu0.3
  • Medium CVE-2023-47038 fixed in 5.30.0-9ubuntu0.5
  • Medium CVE-2023-31484 fixed in 5.30.0-9ubuntu0.4
Medium 3 known vulnerabilities in unzip@6.0-25ubuntu1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 3 CVEs

How to fix

Update unzip from 6.0-25ubuntu1 to 6.0-25ubuntu1.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.0-25ubuntu1.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-2022-0529 fixed in 6.0-25ubuntu1.1
  • Low CVE-2021-4217 fixed in 6.0-25ubuntu1.1
  • Low CVE-2022-0530 fixed in 6.0-25ubuntu1.1
Medium 3 known vulnerabilities in busybox@1.37.0-r18 (maxmindinc/geoipupdate) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether maxmindinc/geoipupdate 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 ncurses@6.2-0ubuntu2 (yandex/clickhouse-server:21.3.2.5) Security · 3 CVEs

How to fix

Update ncurses from 6.2-0ubuntu2 to 6.2-0ubuntu2.1 or later in yandex/clickhouse-server:21.3.2.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 6.2-0ubuntu2.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-2023-29491 fixed in 6.2-0ubuntu2.1
  • Low CVE-2022-29458 fixed in 6.2-0ubuntu2.1
  • Low CVE-2021-39537 fixed in 6.2-0ubuntu2.1
Medium 3 known vulnerabilities in perl@5.30.0-9ubuntu0.2 (yandex/clickhouse-server:21.3.2.5) Security · 3 CVEs

How to fix

Update perl from 5.30.0-9ubuntu0.2 to 5.30.0-9ubuntu0.3 or later in yandex/clickhouse-server:21.3.2.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 5.30.0-9ubuntu0.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-2020-16156 fixed in 5.30.0-9ubuntu0.3
  • Medium CVE-2023-47038 fixed in 5.30.0-9ubuntu0.5
  • Medium CVE-2023-31484 fixed in 5.30.0-9ubuntu0.4
Medium 3 known vulnerabilities in tar@1.30%2Bdfsg-7ubuntu0.20.04.1 (yandex/clickhouse-server:21.3.2.5) Security · 3 CVEs

How to fix

Update tar from 1.30%2Bdfsg-7ubuntu0.20.04.1 to 1.30+dfsg-7ubuntu0.20.04.4 or later in yandex/clickhouse-server:21.3.2.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.30+dfsg-7ubuntu0.20.04.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-2023-39804 fixed in 1.30+dfsg-7ubuntu0.20.04.4
  • Medium CVE-2022-48303 fixed in 1.30+dfsg-7ubuntu0.20.04.3
  • Low CVE-2021-20193 fixed in 1.30+dfsg-7ubuntu0.20.04.2
Medium 3 known vulnerabilities in util-linux@2.34-0.1ubuntu9.1 (yandex/clickhouse-server:21.3.2.5) Security · 3 CVEs

How to fix

Update util-linux from 2.34-0.1ubuntu9.1 to 2.34-0.1ubuntu9.5 or later in yandex/clickhouse-server:21.3.2.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 2.34-0.1ubuntu9.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-2024-28085 fixed in 2.34-0.1ubuntu9.5
  • Medium CVE-2021-3995 fixed in 2.34-0.1ubuntu9.3
  • Medium CVE-2021-3996 fixed in 2.34-0.1ubuntu9.3
Medium 2 known vulnerabilities in uv@0.11.8 (certbot/certbot) Security · 2 CVEs

How to fix

Update uv from 0.11.8 to 0.11.15 or later in certbot/certbot. 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.11.15); 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-4gg8-gxpx-9rph fixed in 0.11.15
  • Medium GHSA-4gg8-gxpx-9rph fixed in 0.11.15
Medium 2 known vulnerabilities in bcpkix-jdk15on@1.64 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update bcpkix-jdk15on from 1.64 to 1.79 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.79); 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-8916 fixed in 1.79
  • Medium CVE-2026-5588 fixed in 1.84
Medium 2 known vulnerabilities in gnupg2@2.2.19-3ubuntu2.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update gnupg2 from 2.2.19-3ubuntu2.1 to 2.2.19-3ubuntu2.4 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.2.19-3ubuntu2.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-30258 fixed in 2.2.19-3ubuntu2.4
  • Medium CVE-2022-34903 fixed in 2.2.19-3ubuntu2.2
Medium 2 known vulnerabilities in jakarta.mail@1.6.4 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update jakarta.mail from 1.6.4 to 1.6.8 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.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 CVE-2025-7962 fixed in 1.6.8
  • Medium CVE-2025-7962 fixed in 1.6.8
Medium 2 known vulnerabilities in openldap@2.4.49%2Bdfsg-2ubuntu1.8 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update openldap from 2.4.49%2Bdfsg-2ubuntu1.8 to 2.4.49+dfsg-2ubuntu1.9 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.4.49+dfsg-2ubuntu1.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

  • Medium CVE-2022-29155 fixed in 2.4.49+dfsg-2ubuntu1.9
  • Low CVE-2023-2953 fixed in 2.4.49+dfsg-2ubuntu1.10
Medium 2 known vulnerabilities in pam@1.3.1-5ubuntu4.3 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update pam from 1.3.1-5ubuntu4.3 to 1.3.1-5ubuntu4.7 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.1-5ubuntu4.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-2024-22365 fixed in 1.3.1-5ubuntu4.7
  • Low CVE-2022-28321 fixed in 1.3.1-5ubuntu4.4
Medium 2 known vulnerabilities in systemd@245.4-4ubuntu3.15 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update systemd from 245.4-4ubuntu3.15 to 245.4-4ubuntu3.20 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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 245.4-4ubuntu3.20); 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-2022-3821 fixed in 245.4-4ubuntu3.20
  • Medium CVE-2022-4415 fixed in 245.4-4ubuntu3.20
Medium 2 known vulnerabilities in tar@1.30%2Bdfsg-7ubuntu0.20.04.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update tar from 1.30%2Bdfsg-7ubuntu0.20.04.2 to 1.30+dfsg-7ubuntu0.20.04.4 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.30+dfsg-7ubuntu0.20.04.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-2023-39804 fixed in 1.30+dfsg-7ubuntu0.20.04.4
  • Medium CVE-2022-48303 fixed in 1.30+dfsg-7ubuntu0.20.04.3
Medium 2 known vulnerabilities in zlib@1%3A1.2.11.dfsg-2ubuntu1.2 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update zlib from 1%3A1.2.11.dfsg-2ubuntu1.2 to 1:1.2.11.dfsg-2ubuntu1.3 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.2.11.dfsg-2ubuntu1.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-2018-25032 fixed in 1:1.2.11.dfsg-2ubuntu1.3
  • Medium CVE-2022-37434 fixed in 1:1.2.11.dfsg-2ubuntu1.5
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (maxmindinc/geoipupdate) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in maxmindinc/geoipupdate. 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 tar@1.35%2Bdfsg-3.1 (postgres:13) Security · 2 CVEs

How to fix

No fixed version of tar is available yet. Check whether postgres:13 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

and 37 more groups with 43 findings

Low 52

Low 5 known vulnerabilities in openldap@2.6.10%2Bdfsg-1 (postgres:13) Security · 5 CVEs

How to fix

No fixed version of openldap is available yet. Check whether postgres:13 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 4 known vulnerabilities in libsepol@3.0-1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 4 CVEs

How to fix

Update libsepol from 3.0-1 to 3.0-1ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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-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

  • Low CVE-2021-36084 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36085 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36086 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36087 fixed in 3.0-1ubuntu0.1
Low 4 known vulnerabilities in libsepol@3.0-1 (yandex/clickhouse-server:21.3.2.5) Security · 4 CVEs

How to fix

Update libsepol from 3.0-1 to 3.0-1ubuntu0.1 or later in yandex/clickhouse-server:21.3.2.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.0-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

  • Low CVE-2021-36084 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36085 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36086 fixed in 3.0-1ubuntu0.1
  • Low CVE-2021-36087 fixed in 3.0-1ubuntu0.1
Low 3 known vulnerabilities in libgcrypt20@1.11.0-7 (postgres:13) Security · 3 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether postgres:13 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 CVE-2026-41989 fixed in 1.11.0-7+deb13u1
Low 3 known vulnerabilities in sqlite3@3.46.1-7 (postgres:13) Security · 3 CVEs

How to fix

No fixed version of sqlite3 is available yet. Check whether postgres:13 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 pcre2@10.34-7 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update pcre2 from 10.34-7 to 10.34-7ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.34-7ubuntu0.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

  • Low CVE-2022-1586 fixed in 10.34-7ubuntu0.1
  • Low CVE-2022-1587 fixed in 10.34-7ubuntu0.1
Low 2 known vulnerabilities in pcre3@2%3A8.39-12build1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 2 CVEs

How to fix

Update pcre3 from 2%3A8.39-12build1 to 2:8.39-12ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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:8.39-12ubuntu0.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

  • Low CVE-2020-14155 fixed in 2:8.39-12ubuntu0.1
  • Low CVE-2019-20838 fixed in 2:8.39-12ubuntu0.1
Low 2 known vulnerabilities in sys@0.32.0 (minio/minio) Security · 2 CVEs

How to fix

Update sys from 0.32.0 to 0.44.0 or later in minio/minio. 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

  • Low CVE-2026-39824 fixed in 0.44.0
  • Low CVE-2026-39824 fixed in 0.44.0
Low 2 known vulnerabilities in coreutils@9.7-3 (postgres:13) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether postgres:13 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 (postgres:13) Security · 2 CVEs

How to fix

No fixed version of util-linux is available yet. Check whether postgres:13 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 pcre2@10.34-7 (yandex/clickhouse-server:21.3.2.5) Security · 2 CVEs

How to fix

Update pcre2 from 10.34-7 to 10.34-7ubuntu0.1 or later in yandex/clickhouse-server:21.3.2.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 10.34-7ubuntu0.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

  • Low CVE-2022-1586 fixed in 10.34-7ubuntu0.1
  • Low CVE-2022-1587 fixed in 10.34-7ubuntu0.1
Low 2 known vulnerabilities in pcre3@2%3A8.39-12build1 (yandex/clickhouse-server:21.3.2.5) Security · 2 CVEs

How to fix

Update pcre3 from 2%3A8.39-12build1 to 2:8.39-12ubuntu0.1 or later in yandex/clickhouse-server:21.3.2.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 2:8.39-12ubuntu0.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

  • Low CVE-2020-14155 fixed in 2:8.39-12ubuntu0.1
  • Low CVE-2019-20838 fixed in 2:8.39-12ubuntu0.1
Low 1 known vulnerability in rand@0.9.2 (certbot/certbot) Security · 1 CVE

How to fix

Update rand from 0.9.2 to 0.9.3 or later in certbot/certbot. 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.9.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 GHSA-cq8v-f236-94qc fixed in 0.9.3
Low 1 known vulnerability in xz@5.8.2-r0 (certbot/certbot) Security · 1 CVE

How to fix

Update xz from 5.8.2-r0 to 5.8.3-r0 or later in certbot/certbot. 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.8.3-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

  • Low CVE-2026-34743 fixed in 5.8.3-r0
Low 1 known vulnerability in bash@5.0-6ubuntu1.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 1 CVE

How to fix

Update bash from 5.0-6ubuntu1.1 to 5.0-6ubuntu1.2 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.0-6ubuntu1.2); 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-2019-18276 fixed in 5.0-6ubuntu1.2
Low 1 known vulnerability in gmp@2%3A6.2.0%2Bdfsg-4 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 1 CVE

How to fix

Update gmp from 2%3A6.2.0%2Bdfsg-4 to 2:6.2.0+dfsg-4ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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.2.0+dfsg-4ubuntu0.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

  • Low CVE-2021-43618 fixed in 2:6.2.0+dfsg-4ubuntu0.1
Low 1 known vulnerability in procps@2%3A3.3.16-1ubuntu2.3 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 1 CVE

How to fix

Update procps from 2%3A3.3.16-1ubuntu2.3 to 2:3.3.16-1ubuntu2.4 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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:3.3.16-1ubuntu2.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

  • Low CVE-2023-4016 fixed in 2:3.3.16-1ubuntu2.4
Low 1 known vulnerability in shadow@1%3A4.8.1-1ubuntu5.20.04.1 (docker.elastic.co/elasticsearch/elasticsearch:7.17.2) Security · 1 CVE

How to fix

Update shadow from 1%3A4.8.1-1ubuntu5.20.04.1 to 1:4.8.1-1ubuntu5.20.04.5 or later in docker.elastic.co/elasticsearch/elasticsearch:7.17.2. 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:4.8.1-1ubuntu5.20.04.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

  • Low CVE-2023-4641 fixed in 1:4.8.1-1ubuntu5.20.04.5
Low 1 known vulnerability in sys@0.33.0 (maxmindinc/geoipupdate) Security · 1 CVE

How to fix

Update sys from 0.33.0 to 0.44.0 or later in maxmindinc/geoipupdate. 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

  • Low CVE-2026-39824 fixed in 0.44.0
Low 1 known vulnerability in sys@0.34.0 (minio/mc:latest) Security · 1 CVE

How to fix

Update sys from 0.34.0 to 0.44.0 or later in minio/mc:latest. 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

  • Low CVE-2026-39824 fixed in 0.44.0
Low 1 known vulnerability in edwards25519@1.1.0 (minio/minio) Security · 1 CVE

How to fix

Update edwards25519 from 1.1.0 to 1.1.1 or later in minio/minio. 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.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

  • Low CVE-2026-26958 fixed in 1.1.1
Low 1 known vulnerability in apt@3.0.3 (postgres:13) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether postgres:13 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 (postgres:13) Security · 1 CVE

How to fix

Update dpkg from 1.22.21 to 1.22.22 or later in postgres:13. 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 libxslt@1.1.35-1.2%2Bdeb13u2 (postgres:13) Security · 1 CVE

How to fix

No fixed version of libxslt is available yet. Check whether postgres:13 needs libxslt 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-9019 fixed in no fix yet
Low 1 known vulnerability in sed@4.9-2 (postgres:13) Security · 1 CVE

How to fix

Update sed from 4.9-2 to 4.9-2+deb13u1 or later in postgres:13. 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.9-2+deb13u1); 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-5958 fixed in 4.9-2+deb13u1
Low 1 known vulnerability in shadow@1%3A4.17.4-2 (postgres:13) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether postgres:13 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 1 known vulnerability in sys@0.1.0 (postgres:13) Security · 1 CVE

How to fix

Update sys from 0.1.0 to 0.44.0 or later in postgres:13. 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

  • Low CVE-2026-39824 fixed in 0.44.0
Low 1 known vulnerability in bash@5.0-6ubuntu1.1 (yandex/clickhouse-server:21.3.2.5) Security · 1 CVE

How to fix

Update bash from 5.0-6ubuntu1.1 to 5.0-6ubuntu1.2 or later in yandex/clickhouse-server:21.3.2.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 5.0-6ubuntu1.2); 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-2019-18276 fixed in 5.0-6ubuntu1.2
Low 1 known vulnerability in gmp@2%3A6.2.0%2Bdfsg-4 (yandex/clickhouse-server:21.3.2.5) Security · 1 CVE

How to fix

Update gmp from 2%3A6.2.0%2Bdfsg-4 to 2:6.2.0+dfsg-4ubuntu0.1 or later in yandex/clickhouse-server:21.3.2.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 2:6.2.0+dfsg-4ubuntu0.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

  • Low CVE-2021-43618 fixed in 2:6.2.0+dfsg-4ubuntu0.1
Low 1 known vulnerability in procps@2%3A3.3.16-1ubuntu2 (yandex/clickhouse-server:21.3.2.5) Security · 1 CVE

How to fix

Update procps from 2%3A3.3.16-1ubuntu2 to 2:3.3.16-1ubuntu2.4 or later in yandex/clickhouse-server:21.3.2.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 2:3.3.16-1ubuntu2.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

  • Low CVE-2023-4016 fixed in 2:3.3.16-1ubuntu2.4
Low 1 known vulnerability in shadow@1%3A4.8.1-1ubuntu5.20.04 (yandex/clickhouse-server:21.3.2.5) Security · 1 CVE

How to fix

Update shadow from 1%3A4.8.1-1ubuntu5.20.04 to 1:4.8.1-1ubuntu5.20.04.5 or later in yandex/clickhouse-server:21.3.2.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:4.8.1-1ubuntu5.20.04.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

  • Low CVE-2023-4641 fixed in 1:4.8.1-1ubuntu5.20.04.5

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 1 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.