Repository scan
opencrvs-core
opencrvs/opencrvs-core · branch develop · scanned 27 May 2026
High 484
High 98 known vulnerabilities in stdlib@1.18.2 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update stdlib from 1.18.2 to 1.19.9 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 78 more
High 79 known vulnerabilities in stdlib@1.21.12 (mongo:4.4)
How to fix
Update stdlib from 1.21.12 to 1.22.7 or later in mongo:4.4. 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-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-58187 fixed in 1.24.9
- High CVE-2025-58188 fixed in 1.24.8
- High CVE-2025-58188 fixed in 1.24.8
- High CVE-2025-61723 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-61725 fixed in 1.24.8
- High CVE-2025-61726 fixed in 1.24.12
- High CVE-2025-61726 fixed in 1.24.12
- High CVE-2025-61729 fixed in 1.24.11
- High CVE-2025-61729 fixed in 1.24.11
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-32280 fixed in 1.25.9
- High CVE-2026-32280 fixed in 1.25.9
- High CVE-2026-32281 fixed in 1.25.9
- and 59 more
High 71 known vulnerabilities in stdlib@1.24.3 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update stdlib from 1.24.3 to 1.24.4 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.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-2025-22874 fixed in 1.24.4
- High CVE-2025-58187 fixed in 1.24.9
- High CVE-2025-58187 fixed in 1.24.9
- High CVE-2025-58188 fixed in 1.24.8
- High CVE-2025-58188 fixed in 1.24.8
- High CVE-2025-61723 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-61725 fixed in 1.24.8
- High CVE-2025-61726 fixed in 1.24.12
- High CVE-2025-61726 fixed in 1.24.12
- High CVE-2025-61729 fixed in 1.24.11
- High CVE-2025-61729 fixed in 1.24.11
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-25679 fixed in 1.25.8
- High CVE-2026-32280 fixed in 1.25.9
- High CVE-2026-32280 fixed in 1.25.9
- High CVE-2026-32281 fixed in 1.25.9
- High CVE-2026-32281 fixed in 1.25.9
- High CVE-2026-32283 fixed in 1.25.9
- and 51 more
High 23 known vulnerabilities in openssl@3.5.1-1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update openssl from 3.5.1-1 to 3.5.4-1~deb13u2 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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
- 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-2025-9231 fixed in 3.5.1-1+deb13u1
- Low CVE-2025-9232 fixed in 3.5.1-1+deb13u1
- and 3 more
High 21 known vulnerabilities in openssl@1.1.1w-0%2Bdeb11u1 (influxdb:1.8.10)
How to fix
Update openssl from 1.1.1w-0%2Bdeb11u1 to 1.1.1w-0+deb11u5 or later in influxdb:1.8.10. 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-2024-4741 fixed in 1.1.1w-0+deb11u2
- 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-28389 fixed in no fix yet
- High CVE-2026-28390 fixed in no fix yet
- High CVE-2026-28387 fixed in no fix yet
- High CVE-2024-5535 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2025-69418 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2024-13176 fixed in 1.1.1w-0+deb11u3
- Medium CVE-2024-9143 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2025-68160 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2023-5678 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2026-22796 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2024-0727 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2026-22795 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2024-2511 fixed in 1.1.1w-0+deb11u2
- Low CVE-2010-0928 fixed in no fix yet
- and 1 more
High 18 known vulnerabilities in crypto@0.25.0 (mongo:4.4)
How to fix
Update crypto from 0.25.0 to 0.35.0 or later in mongo:4.4. 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-2026-39829 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2024-45337 fixed in 0.31.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 17 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u6 (influxdb:1.8.10)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u6 to 3.7.1-5+deb11u10 or later in influxdb:1.8.10. 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+deb11u10); 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.7.1-5+deb11u10
- High CVE-2026-42012 fixed in 3.7.1-5+deb11u10
- High CVE-2026-42011 fixed in 3.7.1-5+deb11u10
- High CVE-2026-33845 fixed in 3.7.1-5+deb11u10
- High CVE-2026-33846 fixed in 3.7.1-5+deb11u10
- High CVE-2026-42009 fixed in 3.7.1-5+deb11u10
- High CVE-2026-42013 fixed in 3.7.1-5+deb11u10
- High CVE-2026-5260 fixed in 3.7.1-5+deb11u10
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2026-42015 fixed in 3.7.1-5+deb11u10
- 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
- Medium CVE-2026-3833 fixed in 3.7.1-5+deb11u10
- Low CVE-2011-3389 fixed in no fix yet
High 16 known vulnerabilities in postgresql-17@17.6-1.pgdg13%2B1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update postgresql-17 from 17.6-1.pgdg13%2B1 to 17.10-0+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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 17.10-0+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
- High CVE-2026-6476 fixed in 17.10-0+deb13u1
- High CVE-2026-6479 fixed in 17.10-0+deb13u1
- High CVE-2026-2004 fixed in 17.8-0+deb13u1
- High CVE-2026-2005 fixed in 17.8-0+deb13u1
- High CVE-2026-2006 fixed in 17.8-0+deb13u1
- High CVE-2026-6473 fixed in 17.10-0+deb13u1
- High CVE-2026-6475 fixed in 17.10-0+deb13u1
- High CVE-2026-6477 fixed in 17.10-0+deb13u1
- High CVE-2026-6637 fixed in 17.10-0+deb13u1
- Medium CVE-2026-2003 fixed in 17.8-0+deb13u1
- Medium CVE-2026-6474 fixed in 17.10-0+deb13u1
- Medium CVE-2026-6472 fixed in 17.10-0+deb13u1
- Medium CVE-2025-12818 fixed in 17.7-0+deb13u1
- Medium CVE-2026-6478 fixed in 17.10-0+deb13u1
- Low CVE-2025-12817 fixed in 17.7-0+deb13u1
- Low CVE-2026-6638 fixed in 17.10-0+deb13u1
High 16 known vulnerabilities in crypto@0.37.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update crypto from 0.37.0 to 0.43.0 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update gnutls28 from 3.8.9-3 to 3.8.9-3+deb13u4 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 14 known vulnerabilities in glibc@2.31-13%2Bdeb11u11 (influxdb:1.8.10)
How to fix
No fixed version of glibc is available yet. Check whether influxdb:1.8.10 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-5435 fixed in no fix yet
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2026-5928 fixed in no fix yet
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2026-5450 fixed in no fix yet
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- Medium CVE-2026-6238 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 13 known vulnerabilities in be_BY@latin (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update be_BY from latin to 2.41-12+deb13u2 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 9 known vulnerabilities in netty-codec-http@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-codec-http from 4.1.115.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-2026-41417 fixed in 4.1.133.Final
- Medium CVE-2026-42581 fixed in 4.1.133.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 9 known vulnerabilities in minio@0.0.0-20250613113347-a6c538c5a113%2Bdirty (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
No fixed version of minio is available yet. Check whether quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z 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 9 known vulnerabilities in net@0.39.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update net from 0.39.0 to 0.53.0 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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 7 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u5 (influxdb:1.8.10)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u5 to 1.18.3-6+deb11u6 or later in influxdb:1.8.10. 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.18.3-6+deb11u6); 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-24528 fixed in 1.18.3-6+deb11u6
- Medium CVE-2025-3576 fixed in 1.18.3-6+deb11u7
- Medium CVE-2026-40355 fixed in no fix yet
- Medium CVE-2026-40356 fixed in no fix yet
- 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
High 6 known vulnerabilities in glibc@2.34-168.el9_6.19 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
No fixed version of glibc is available yet. Check whether quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z 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-2025-8058 fixed in 2.34-168.el9_6.23
- Medium CVE-2026-0915 fixed in no fix yet
- Medium CVE-2025-5702 fixed in 2.34-168.el9_6.20
- Low CVE-2025-15281 fixed in no fix yet
High 5 known vulnerabilities in perl@5.32.1-4%2Bdeb11u3 (influxdb:1.8.10)
How to fix
Update perl from 5.32.1-4%2Bdeb11u3 to 5.32.1-4+deb11u4 or later in influxdb:1.8.10. 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+deb11u4); 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-16156 fixed in 5.32.1-4+deb11u4
- High CVE-2023-31484 fixed in 5.32.1-4+deb11u4
- 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
High 4 known vulnerabilities in prometheus@0.303.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update prometheus from 0.303.0 to 0.311.3 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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 netty-codec-http2@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-codec-http2 from 4.1.115.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-42587 fixed in 4.1.133.Final
- High CVE-2025-55163 fixed in 4.1.124.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
High 3 known vulnerabilities in libxslt@1.1.35-1.2 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update libxslt from 1.1.35-1.2 to 1.1.35-1.2+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.35-1.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
- High CVE-2025-7424 fixed in 1.1.35-1.2+deb13u1
- Low CVE-2015-9019 fixed in no fix yet
- Low CVE-2023-40403 fixed in 1.1.35-1.2+deb13u1
High 2 known vulnerabilities in bcprov-jdk18on@1.78.1 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update bcprov-jdk18on from 1.78.1 to 1.84 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.84); 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-5598 fixed in 1.84
- Medium CVE-2026-0636 fixed in 1.84
High 2 known vulnerabilities in json-smart@2.5.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update json-smart from 2.5.0 to 2.5.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.5.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-2024-57699 fixed in 2.5.2
- High CVE-2024-57699 fixed in 2.5.2
High 2 known vulnerabilities in lz4-java@1.8.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
No fixed version of lz4-java is available yet. Check whether docker.elastic.co/elasticsearch/elasticsearch:8.16.4 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 netty-codec@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-codec from 4.1.115.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-42583 fixed in 4.1.133.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
High 2 known vulnerabilities in tika-parser-pdf-module@2.9.2 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update tika-parser-pdf-module from 2.9.2 to 3.2.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.2.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-2025-54988 fixed in 3.2.2
- High CVE-2025-66516 fixed in 3.2.2
High 2 known vulnerabilities in gnupg2@2.4.7-21 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update gnupg2 from 2.4.7-21 to 2.4.7-21+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.7-21+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
- High CVE-2025-68973 fixed in 2.4.7-21+deb13u1
- Low CVE-2022-3219 fixed in no fix yet
High 2 known vulnerabilities in gnupg2@2.2.27-2%2Bdeb11u2 (influxdb:1.8.10)
How to fix
Update gnupg2 from 2.2.27-2%2Bdeb11u2 to 2.2.27-2+deb11u3 or later in influxdb:1.8.10. 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.27-2+deb11u3); 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-68973 fixed in 2.2.27-2+deb11u3
- Low CVE-2022-3219 fixed in no fix yet
High 2 known vulnerabilities in pam@1.4.0-9%2Bdeb11u1 (influxdb:1.8.10)
How to fix
Update pam from 1.4.0-9%2Bdeb11u1 to 1.4.0-9+deb11u2 or later in influxdb:1.8.10. 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.0-9+deb11u2); 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-6020 fixed in 1.4.0-9+deb11u2
- Medium CVE-2024-22365 fixed in 1.4.0-9+deb11u2
High 2 known vulnerabilities in grpc@1.72.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update grpc from 1.72.0 to 1.79.3 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update sdk from 1.35.0 to 1.40.0 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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
High 1 known vulnerability in netty-codec-dns@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-codec-dns from 4.1.115.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-42579 fixed in 4.1.133.Final
High 1 known vulnerability in netty-handler@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-handler from 4.1.115.Final to 4.1.118.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.118.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-2025-24970 fixed in 4.1.118.Final
High 1 known vulnerability in tika-core@2.9.2 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update tika-core from 2.9.2 to 3.2.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.2.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-2025-66516 fixed in 3.2.2
High 1 known vulnerability in nghttp2@1.43.0-1%2Bdeb11u2 (influxdb:1.8.10)
How to fix
Update nghttp2 from 1.43.0-1%2Bdeb11u2 to 1.43.0-1+deb11u3 or later in influxdb:1.8.10. 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-1+deb11u3); 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-27135 fixed in 1.43.0-1+deb11u3
High 1 known vulnerability in wget@1.21-1%2Bdeb11u1 (influxdb:1.8.10)
How to fix
Update wget from 1.21-1%2Bdeb11u1 to 1.21-1+deb11u2 or later in influxdb:1.8.10. 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-1+deb11u2); 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-38428 fixed in 1.21-1+deb11u2
High 1 known vulnerability in jsonparser@1.1.1 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update jsonparser from 1.1.1 to 1.1.2 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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); 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-32285 fixed in 1.1.2
High 1 known vulnerability in thrift@0.21.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update thrift from 0.21.0 to 0.23.0 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.23.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-41602 fixed in 0.23.0
High 1 known vulnerability in v4@4.1.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update v4 from 4.1.0 to 4.1.4 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.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-2026-34986 fixed in 4.1.4
Medium 86
Medium 10 known vulnerabilities in curl@7.74.0-1.3%2Bdeb11u13 (influxdb:1.8.10)
How to fix
Update curl from 7.74.0-1.3%2Bdeb11u13 to 7.74.0-1.3+deb11u14 or later in influxdb:1.8.10. 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.74.0-1.3+deb11u14); 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-8096 fixed in 7.74.0-1.3+deb11u14
- 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
Medium 10 known vulnerabilities in systemd@247.3-7%2Bdeb11u6 (influxdb:1.8.10)
How to fix
Update systemd from 247.3-7%2Bdeb11u6 to 247.3-7+deb11u7 or later in influxdb:1.8.10. 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 8 known vulnerabilities in systemd@257.7-1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update systemd from 257.7-1 to 257.13-1~deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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 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 6 known vulnerabilities in log4j-core@2.12.4 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update log4j-core from 2.12.4 to 2.25.3 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-2025-68161 fixed in 2.25.3
- Medium CVE-2026-34477 fixed in 2.25.4
- Medium CVE-2026-34477 fixed in 2.25.4
- Medium CVE-2026-34480 fixed in 2.25.4
- Medium CVE-2026-34480 fixed in 2.25.4
Medium 5 known vulnerabilities in krb5@1.21.3-5 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update krb5 from 1.21.3-5 to 1.21.3-5+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 krb5@1.17-6ubuntu4.8 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update krb5 from 1.17-6ubuntu4.8 to 1.17-6ubuntu4.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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
- Low CVE-2024-26458 fixed in 1.17-6ubuntu4.9
- Low CVE-2024-26461 fixed in 1.17-6ubuntu4.9
Medium 4 known vulnerabilities in libxml2@2.12.7%2Bdfsg%2Breally2.9.14-2.1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update libxml2 from 2.12.7%2Bdfsg%2Breally2.9.14-2.1 to 2.12.7+dfsg+really2.9.14-2.1+deb13u2 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 4 known vulnerabilities in shadow@1%3A4.8.1-1 (influxdb:1.8.10)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in influxdb:1.8.10. 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-1+deb11u1); 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-4641 fixed in 1:4.8.1-1+deb11u1
- Low CVE-2007-5686 fixed in no fix yet
- Low CVE-2013-4235 fixed in no fix yet
- Low CVE-2023-29383 fixed in 1:4.8.1-1+deb11u1
Medium 2 known vulnerabilities in bcpkix-jdk18on@1.78.1 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update bcpkix-jdk18on from 1.78.1 to 1.79 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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 commons-lang3@3.14.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update commons-lang3 from 3.14.0 to 3.18.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.18.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-48924 fixed in 3.18.0
- Medium CVE-2025-48924 fixed in 3.18.0
Medium 2 known vulnerabilities in elasticsearch@8.16.4 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update elasticsearch from 8.16.4 to 8.18.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.18.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-37727 fixed in 8.18.8
- Medium CVE-2025-37731 fixed in 8.19.8
Medium 2 known vulnerabilities in jackson-core@2.15.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update jackson-core from 2.15.0 to 2.18.6 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.18.6); 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-72hv-8253-57qq fixed in 2.18.6
- Medium GHSA-72hv-8253-57qq fixed in 2.18.6
Medium 2 known vulnerabilities in jakarta.mail@1.6.3 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update jakarta.mail from 1.6.3 to 1.6.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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 sqlite3@3.31.1-4ubuntu0.6 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update sqlite3 from 3.31.1-4ubuntu0.6 to 3.31.1-4ubuntu0.7 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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 2 known vulnerabilities in tar@1.35%2Bdfsg-3.1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of tar is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 tar@1.35%2Bdfsg-3.1 (redis:8)
How to fix
No fixed version of tar is available yet. Check whether redis:8 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 1 known vulnerability in bc-fips@1.0.2.5 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update bc-fips from 1.0.2.5 to 2.1.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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-8885 fixed in 2.1.0
Medium 1 known vulnerability in glibc@2.31-0ubuntu9.17 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update glibc from 2.31-0ubuntu9.17 to 2.31-0ubuntu9.18 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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
- Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
Medium 1 known vulnerability in gnupg2@2.2.19-3ubuntu2.2 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update gnupg2 from 2.2.19-3ubuntu2.2 to 2.2.19-3ubuntu2.4 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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 1 known vulnerability in gnutls28@3.6.13-2ubuntu1.11 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update gnutls28 from 3.6.13-2ubuntu1.11 to 3.6.13-2ubuntu1.12 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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 1 known vulnerability in libtasn1-6@4.16.0-2 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update libtasn1-6 from 4.16.0-2 to 4.16.0-2ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.16.0-2ubuntu0.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-2024-12133 fixed in 4.16.0-2ubuntu0.1
Medium 1 known vulnerability in log4j-1.2-api@2.19.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update log4j-1.2-api from 2.19.0 to 2.25.4 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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-34479 fixed in 2.25.4
Medium 1 known vulnerability in netty-common@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-common from 4.1.115.Final to 4.1.118.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.118.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-2025-25193 fixed in 4.1.118.Final
Medium 1 known vulnerability in nimbus-jose-jwt@9.37.3 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update nimbus-jose-jwt from 9.37.3 to 10.0.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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
- Medium CVE-2025-53864 fixed in 10.0.2
Medium 1 known vulnerability in opentelemetry-api@1.31.0 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update opentelemetry-api from 1.31.0 to 1.62.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.62.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-45292 fixed in 1.62.0
Medium 1 known vulnerability in poi-ooxml@5.2.5 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update poi-ooxml from 5.2.5 to 5.4.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.4.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-31672 fixed in 5.4.0
Medium 1 known vulnerability in reactor-netty-http@1.0.45 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update reactor-netty-http from 1.0.45 to 1.2.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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-22227 fixed in 1.2.8
Medium 1 known vulnerability in x-pack-core@8.16.4 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update x-pack-core from 8.16.4 to 8.19.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.19.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-68390 fixed in 8.19.8
Medium 1 known vulnerability in x-pack-security@8.16.4 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update x-pack-security from 8.16.4 to 8.19.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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
- Medium CVE-2025-68384 fixed in 8.19.9
Medium 1 known vulnerability in libcap2@1%3A2.75-10%2Bb1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update libcap2 from 1%3A2.75-10%2Bb1 to 1:2.75-10+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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:2.75-10+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-4878 fixed in 1:2.75-10+deb13u1
Medium 1 known vulnerability in libtasn1-6@4.16.0-2%2Bdeb11u1 (influxdb:1.8.10)
How to fix
Update libtasn1-6 from 4.16.0-2%2Bdeb11u1 to 4.16.0-2+deb11u2 or later in influxdb:1.8.10. 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.16.0-2+deb11u2); 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-12133 fixed in 4.16.0-2+deb11u2
Medium 1 known vulnerability in glibc@2.31-0ubuntu9.17 (mongo:4.4)
How to fix
Update glibc from 2.31-0ubuntu9.17 to 2.31-0ubuntu9.18 or later in mongo:4.4. 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.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
- Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
Medium 1 known vulnerability in js-yaml@3.13.1 (mongo:4.4)
How to fix
Update js-yaml from 3.13.1 to 4.1.1 or later in mongo:4.4. 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.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-2025-64718 fixed in 4.1.1
Medium 1 known vulnerability in go-ntlmssp@0.0.0-20221128193559-754e69321358 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update go-ntlmssp from 0.0.0-20221128193559-754e69321358 to 0.1.1 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.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
- Medium CVE-2026-32952 fixed in 0.1.1
Medium 1 known vulnerability in paho.mqtt.golang@1.5.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update paho.mqtt.golang from 1.5.0 to 1.5.1 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.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
- Medium CVE-2025-10543 fixed in 1.5.1
Low 78
Low 7 known vulnerabilities in glibc@2.41-12%2Bdeb13u3 (redis:8)
How to fix
No fixed version of glibc is available yet. Check whether redis:8 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
- 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 5 known vulnerabilities in openldap@2.6.10%2Bdfsg-1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of openldap is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (influxdb:1.8.10)
How to fix
No fixed version of openldap is available yet. Check whether influxdb:1.8.10 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 (influxdb:1.8.10)
How to fix
No fixed version of pcre3 is available yet. Check whether influxdb:1.8.10 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 (influxdb:1.8.10)
How to fix
No fixed version of sqlite3 is available yet. Check whether influxdb:1.8.10 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 libsepol@3.1-1 (influxdb:1.8.10)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in influxdb:1.8.10. 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-1+deb11u1); 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.1-1+deb11u1
- Low CVE-2021-36085 fixed in 3.1-1+deb11u1
- Low CVE-2021-36086 fixed in 3.1-1+deb11u1
- Low CVE-2021-36087 fixed in 3.1-1+deb11u1
Low 4 known vulnerabilities in systemd@257.13-1~deb13u1 (redis:8)
How to fix
No fixed version of systemd is available yet. Check whether redis:8 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 libgcrypt20@1.11.0-7 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of sqlite3 is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 openssl@1.1.1f-1ubuntu2.23 (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update openssl from 1.1.1f-1ubuntu2.23 to 1.1.1f-1ubuntu2.24 or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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.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
- Low CVE-2024-13176 fixed in 1.1.1f-1ubuntu2.24
- Low CVE-2024-9143 fixed in 1.1.1f-1ubuntu2.24
Low 2 known vulnerabilities in coreutils@9.7-3 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of coreutils is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of util-linux is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 coreutils@8.32-4%2Bb1 (influxdb:1.8.10)
How to fix
No fixed version of coreutils is available yet. Check whether influxdb:1.8.10 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 (influxdb:1.8.10)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether influxdb:1.8.10 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 util-linux@2.36.1-8%2Bdeb11u2 (influxdb:1.8.10)
How to fix
No fixed version of util-linux is available yet. Check whether influxdb:1.8.10 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 coreutils@9.7-3 (redis:8)
How to fix
No fixed version of coreutils is available yet. Check whether redis:8 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 sqlite3@3.46.1-7%2Bdeb13u1 (redis:8)
How to fix
No fixed version of sqlite3 is available yet. Check whether redis:8 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 2 known vulnerabilities in util-linux@2.41-5 (redis:8)
How to fix
No fixed version of util-linux is available yet. Check whether redis:8 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 netty-handler-proxy@4.1.115.Final (docker.elastic.co/elasticsearch/elasticsearch:8.16.4)
How to fix
Update netty-handler-proxy from 4.1.115.Final to 4.1.133.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.16.4. 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
- Low CVE-2026-42578 fixed in 4.1.133.Final
Low 1 known vulnerability in apt@3.0.3 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of apt is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update dpkg from 1.22.21 to 1.22.22 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 pcre2@10.45-1 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update pcre2 from 10.45-1 to 10.46-1~deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.46-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
- Low CVE-2025-58050 fixed in 10.46-1~deb13u1
Low 1 known vulnerability in perl@5.40.1-6 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of perl is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 sed@4.9-2 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
Update sed from 4.9-2 to 4.9-2+deb13u1 or later in docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.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.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 (docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2)
How to fix
No fixed version of shadow is available yet. Check whether docker.io/chumaky/postgres_mongo_fdw:17.6_fdw5.5.2 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 apt@2.2.4 (influxdb:1.8.10)
How to fix
No fixed version of apt is available yet. Check whether influxdb:1.8.10 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 (influxdb:1.8.10)
How to fix
No fixed version of gcc-10 is available yet. Check whether influxdb:1.8.10 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 (influxdb:1.8.10)
How to fix
No fixed version of gcc-9 is available yet. Check whether influxdb:1.8.10 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 influxdb@1.8.10-1 (influxdb:1.8.10)
How to fix
No fixed version of influxdb is available yet. Check whether influxdb:1.8.10 needs influxdb 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-36640 fixed in no fix yet
Low 1 known vulnerability in pcre2@10.36-2%2Bdeb11u1 (influxdb:1.8.10)
How to fix
No fixed version of pcre2 is available yet. Check whether influxdb:1.8.10 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 tar@1.34%2Bdfsg-1%2Bdeb11u1 (influxdb:1.8.10)
How to fix
No fixed version of tar is available yet. Check whether influxdb:1.8.10 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 edwards25519@1.1.0 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update edwards25519 from 1.1.0 to 1.1.1 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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 ncurses@6.2-10.20210508.el9 (quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z)
How to fix
Update ncurses from 6.2-10.20210508.el9 to 6.2-10.20210508.el9_6.2 or later in quay.io/minio/minio:RELEASE.2025-06-13T11-33-47Z. 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.20210508.el9_6.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-2022-29458 fixed in 6.2-10.20210508.el9_6.2
Low 1 known vulnerability in apt@3.0.3 (redis:8)
How to fix
No fixed version of apt is available yet. Check whether redis:8 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 openssl@3.5.6-1~deb13u1 (redis:8)
How to fix
No fixed version of openssl is available yet. Check whether redis:8 needs openssl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2010-0928 fixed in no fix yet
Low 1 known vulnerability in perl@5.40.1-6 (redis:8)
How to fix
No fixed version of perl is available yet. Check whether redis:8 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 (redis:8)
How to fix
No fixed version of shadow is available yet. Check whether redis:8 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 27 May 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.