Repository scan
OpenELIS-Global-2
DIGI-UW/OpenELIS-Global-2 · branch develop · scanned 21 Apr 2026
High 1,282
High 101 known vulnerabilities in stdlib@1.16.7 (itechuw/openelis-global-2-database:develop)
How to fix
Update stdlib from 1.16.7 to 1.19.9 or later in itechuw/openelis-global-2-database:develop. 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-2021-39293 fixed in 1.16.8
- High CVE-2021-41771 fixed in 1.16.10
- High CVE-2021-41772 fixed in 1.16.10
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-24921 fixed in 1.16.15
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-28327 fixed in 1.17.9
- 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.17.11
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30631 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30633 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- and 81 more
High 101 known vulnerabilities in stdlib@1.16.7 (postgres:14.4)
How to fix
Update stdlib from 1.16.7 to 1.19.9 or later in postgres:14.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.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-2021-39293 fixed in 1.16.8
- High CVE-2021-41771 fixed in 1.16.10
- High CVE-2021-41772 fixed in 1.16.10
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-24921 fixed in 1.16.15
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-28327 fixed in 1.17.9
- 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.17.11
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30631 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30633 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- and 81 more
High 58 known vulnerabilities in stdlib@1.19.9 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update stdlib from 1.19.9 to 1.22.7 or later in hapiproject/hapi:v6.6.0-tomcat. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-30635 fixed in 1.22.7
- High CVE-2023-39325 fixed in 1.20.10
- High CVE-2023-44487 fixed in 1.20.10
- High CVE-2023-45283 fixed in 1.20.11
- High CVE-2023-45287 fixed in 1.20.0
- High CVE-2023-45288 fixed in 1.21.9
- High CVE-2024-24784 fixed in 1.21.8
- High CVE-2024-24791 fixed in 1.21.12
- High CVE-2024-34156 fixed in 1.22.7
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2025-58187 fixed in 1.24.9
- 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
- and 38 more
High 58 known vulnerabilities in stdlib@1.19.9 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update stdlib from 1.19.9 to 1.22.7 or later in itechuw/openelis-global-2-fhir:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-30635 fixed in 1.22.7
- High CVE-2023-39325 fixed in 1.20.10
- High CVE-2023-44487 fixed in 1.20.10
- High CVE-2023-45283 fixed in 1.20.11
- High CVE-2023-45287 fixed in 1.20.0
- High CVE-2023-45288 fixed in 1.21.9
- High CVE-2024-24784 fixed in 1.21.8
- High CVE-2024-24791 fixed in 1.21.12
- High CVE-2024-34156 fixed in 1.22.7
- High CVE-2024-34158 fixed in 1.22.7
- High CVE-2025-58187 fixed in 1.24.9
- 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
- and 38 more
High 30 known vulnerabilities in openssl@1.1.1n-0%2Bdeb11u3 (itechuw/openelis-global-2-database:develop)
How to fix
Update openssl from 1.1.1n-0%2Bdeb11u3 to 1.1.1n-0+deb11u4 or later in itechuw/openelis-global-2-database:develop. 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.1n-0+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-2023-0286 fixed in 1.1.1n-0+deb11u4
- High CVE-2025-69419 fixed in 1.1.1w-0+deb11u5
- High CVE-2023-0464 fixed in 1.1.1n-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-2024-5535 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2022-4304 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2022-4450 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0215 fixed in 1.1.1n-0+deb11u4
- 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-2022-2097 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0465 fixed in 1.1.1n-0+deb11u5
- and 10 more
High 30 known vulnerabilities in openssl@1.1.1n-0%2Bdeb11u3 (postgres:14.4)
How to fix
Update openssl from 1.1.1n-0%2Bdeb11u3 to 1.1.1n-0+deb11u4 or later in postgres:14.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.1n-0+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-2023-0286 fixed in 1.1.1n-0+deb11u4
- High CVE-2025-69419 fixed in 1.1.1w-0+deb11u5
- High CVE-2023-0464 fixed in 1.1.1n-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-2024-5535 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2022-4304 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2022-4450 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0215 fixed in 1.1.1n-0+deb11u4
- 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-2022-2097 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0465 fixed in 1.1.1n-0+deb11u5
- and 10 more
High 25 known vulnerabilities in openssl@1.1.1n-0%2Bdeb11u4 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update openssl from 1.1.1n-0%2Bdeb11u4 to 1.1.1w-0+deb11u5 or later in hapiproject/hapi:v6.6.0-tomcat. 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-2023-0464 fixed in 1.1.1n-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-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-0465 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-0466 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-3446 fixed in 1.1.1v-0~deb11u1
- Medium CVE-2023-3817 fixed in 1.1.1v-0~deb11u1
- Medium CVE-2023-5678 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2026-22796 fixed in 1.1.1w-0+deb11u5
- and 5 more
High 25 known vulnerabilities in openssl@1.1.1n-0%2Bdeb11u4 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update openssl from 1.1.1n-0%2Bdeb11u4 to 1.1.1w-0+deb11u5 or later in itechuw/openelis-global-2-fhir:develop. 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-2023-0464 fixed in 1.1.1n-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-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-0465 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-0466 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-3446 fixed in 1.1.1v-0~deb11u1
- Medium CVE-2023-3817 fixed in 1.1.1v-0~deb11u1
- Medium CVE-2023-5678 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2026-22796 fixed in 1.1.1w-0+deb11u5
- and 5 more
High 23 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u2 (itechuw/openelis-global-2-database:develop)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7%2Bdeb11u2 to 2.9.10+dfsg-6.7+deb11u5 or later in itechuw/openelis-global-2-database:develop. 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.9.10+dfsg-6.7+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-2022-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
- High CVE-2022-40303 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2022-40304 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
- Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
- Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
- Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
- Medium CVE-2023-28484 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-29469 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
- Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2024-34459 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-6170 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-8732 fixed in no fix yet
- and 3 more
High 23 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u2 (postgres:14.4)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7%2Bdeb11u2 to 2.9.10+dfsg-6.7+deb11u5 or later in postgres:14.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.9.10+dfsg-6.7+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-2022-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
- High CVE-2022-40303 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2022-40304 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
- Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
- Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
- Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
- Medium CVE-2023-28484 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-29469 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
- Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2024-34459 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-6170 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-8732 fixed in no fix yet
- and 3 more
High 20 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u4 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7%2Bdeb11u4 to 2.9.10+dfsg-6.7+deb11u5 or later in hapiproject/hapi:v6.6.0-tomcat. 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.9.10+dfsg-6.7+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-2022-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
- High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
- Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
- Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
- Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
- Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
- Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2024-34459 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-12863 fixed in no fix yet
- Low CVE-2025-6170 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-8732 fixed in no fix yet
- Low CVE-2026-1757 fixed in no fix yet
- Low CVE-2025-27113 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2025-32415 fixed in 2.9.10+dfsg-6.7+deb11u7
High 20 known vulnerabilities in tomcat-catalina@9.0.75 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update tomcat-catalina from 9.0.75 to 9.0.98 or later in hapiproject/hapi:v6.6.0-tomcat. 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.0.98); 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-50379 fixed in 9.0.98
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2026-34483 fixed in 9.0.116
- High CVE-2026-34487 fixed in 9.0.117
- High CVE-2025-55752 fixed in 9.0.109
- High CVE-2025-48988 fixed in 9.0.106
- High CVE-2025-24813 fixed in 9.0.99
- High CVE-2024-52316 fixed in 9.0.96
- Medium CVE-2025-49124 fixed in 9.0.106
- Medium CVE-2023-41080 fixed in 8.5.93,
- Medium CVE-2025-49125 fixed in 9.0.106
- Medium CVE-2025-66614 fixed in 9.0.112
- Medium CVE-2025-55668 fixed in 9.0.106
- Medium CVE-2024-54677 fixed in 9.0.98
- Medium CVE-2026-25854 fixed in 9.0.116
- Low CVE-2025-46701 fixed in 9.0.105
- Low CVE-2025-55754 fixed in 9.0.109
- Low CVE-2025-61795 fixed in 9.0.110
- Low CVE-2026-24733 fixed in 9.0.112
High 20 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u4 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7%2Bdeb11u4 to 2.9.10+dfsg-6.7+deb11u5 or later in itechuw/openelis-global-2-fhir:develop. 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.9.10+dfsg-6.7+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-2022-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
- High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
- Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
- Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
- Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
- Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
- Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2024-34459 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-12863 fixed in no fix yet
- Low CVE-2025-6170 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-8732 fixed in no fix yet
- Low CVE-2026-1757 fixed in no fix yet
- Low CVE-2025-27113 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2025-32415 fixed in 2.9.10+dfsg-6.7+deb11u7
High 20 known vulnerabilities in tomcat-catalina@9.0.75 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update tomcat-catalina from 9.0.75 to 9.0.98 or later in itechuw/openelis-global-2-fhir:develop. 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.0.98); 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-50379 fixed in 9.0.98
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2026-34483 fixed in 9.0.116
- High CVE-2026-34487 fixed in 9.0.117
- High CVE-2025-55752 fixed in 9.0.109
- High CVE-2025-48988 fixed in 9.0.106
- High CVE-2025-24813 fixed in 9.0.99
- High CVE-2024-52316 fixed in 9.0.96
- Medium CVE-2025-49124 fixed in 9.0.106
- Medium CVE-2023-41080 fixed in 8.5.93,
- Medium CVE-2025-49125 fixed in 9.0.106
- Medium CVE-2025-66614 fixed in 9.0.112
- Medium CVE-2025-55668 fixed in 9.0.106
- Medium CVE-2024-54677 fixed in 9.0.98
- Medium CVE-2026-25854 fixed in 9.0.116
- Low CVE-2025-46701 fixed in 9.0.105
- Low CVE-2025-55754 fixed in 9.0.109
- Low CVE-2025-61795 fixed in 9.0.110
- Low CVE-2026-24733 fixed in 9.0.112
High 17 known vulnerabilities in aa_ER@saaho (itechuw/openelis-global-2-database:develop)
How to fix
Update aa_ER from saaho to 2.31-13+deb11u9 or later in itechuw/openelis-global-2-database:develop. 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-13+deb11u9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-2961 fixed in 2.31-13+deb11u9
- High CVE-2024-33601 fixed in 2.31-13+deb11u10
- High CVE-2024-33602 fixed in 2.31-13+deb11u10
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2021-3999 fixed in 2.31-13+deb11u4
- High CVE-2023-4911 fixed in 2.31-13+deb11u7
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2024-33599 fixed in 2.31-13+deb11u10
- Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- 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 17 known vulnerabilities in openssl@3.3.3-r0 (nginx:1.27-alpine)
How to fix
Update openssl from 3.3.3-r0 to 3.3.6-r0 or later in nginx:1.27-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.3.6-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-69419 fixed in 3.3.6-r0
- High CVE-2025-69420 fixed in 3.3.6-r0
- High CVE-2025-69421 fixed in 3.3.6-r0
- High CVE-2025-9230 fixed in 3.3.5-r0
- High CVE-2026-28388 fixed in 3.3.7-r0
- High CVE-2026-28389 fixed in 3.3.7-r0
- High CVE-2026-28390 fixed in 3.3.7-r0
- High CVE-2026-31790 fixed in 3.3.7-r0
- High CVE-2025-15467 fixed in 3.3.6-r0
- Medium CVE-2025-69418 fixed in 3.3.6-r0
- Medium CVE-2025-68160 fixed in 3.3.6-r0
- Medium CVE-2026-22796 fixed in 3.3.6-r0
- Medium CVE-2026-22795 fixed in 3.3.6-r0
- Medium CVE-2025-15468 fixed in 3.3.6-r0
- Medium CVE-2025-66199 fixed in 3.3.6-r0
- Medium CVE-2025-9232 fixed in 3.3.5-r0
- Medium CVE-2025-9231 fixed in 3.3.5-r0
High 17 known vulnerabilities in aa_ER@saaho (postgres:14.4)
How to fix
Update aa_ER from saaho to 2.31-13+deb11u9 or later in postgres:14.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-13+deb11u9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-2961 fixed in 2.31-13+deb11u9
- High CVE-2024-33601 fixed in 2.31-13+deb11u10
- High CVE-2024-33602 fixed in 2.31-13+deb11u10
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2021-3999 fixed in 2.31-13+deb11u4
- High CVE-2023-4911 fixed in 2.31-13+deb11u7
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2024-33599 fixed in 2.31-13+deb11u10
- Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- 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 16 known vulnerabilities in glibc@2.31-13%2Bdeb11u6 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update glibc from 2.31-13%2Bdeb11u6 to 2.31-13+deb11u9 or later in hapiproject/hapi:v6.6.0-tomcat. 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-13+deb11u9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-2961 fixed in 2.31-13+deb11u9
- High CVE-2024-33601 fixed in 2.31-13+deb11u10
- High CVE-2024-33602 fixed in 2.31-13+deb11u10
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2023-4911 fixed in 2.31-13+deb11u7
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2024-33599 fixed in 2.31-13+deb11u10
- Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- 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 16 known vulnerabilities in glibc@2.31-13%2Bdeb11u6 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update glibc from 2.31-13%2Bdeb11u6 to 2.31-13+deb11u9 or later in itechuw/openelis-global-2-fhir:develop. 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-13+deb11u9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-2961 fixed in 2.31-13+deb11u9
- High CVE-2024-33601 fixed in 2.31-13+deb11u10
- High CVE-2024-33602 fixed in 2.31-13+deb11u10
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2023-4911 fixed in 2.31-13+deb11u7
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2024-33599 fixed in 2.31-13+deb11u10
- Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- 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 16 known vulnerabilities in curl@8.12.1-r1 (nginx:1.27-alpine)
How to fix
Update curl from 8.12.1-r1 to 8.14.1-r0 or later in nginx:1.27-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.14.1-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-5399 fixed in 8.14.1-r0
- High CVE-2025-9086 fixed in 8.14.1-r2
- High CVE-2026-3805 fixed in no fix yet
- Medium CVE-2025-10966 fixed in no fix yet
- Medium CVE-2025-5025 fixed in 8.14.0-r0
- Medium CVE-2025-10148 fixed in 8.14.1-r2
- Medium CVE-2025-14524 fixed in no fix yet
- Medium CVE-2025-14819 fixed in no fix yet
- Medium CVE-2025-15079 fixed in no fix yet
- Medium CVE-2026-3783 fixed in no fix yet
- Medium CVE-2025-13034 fixed in no fix yet
- Medium CVE-2025-14017 fixed in no fix yet
- Medium CVE-2025-4947 fixed in 8.14.0-r0
- Medium CVE-2026-1965 fixed in no fix yet
- Medium CVE-2026-3784 fixed in no fix yet
- Low CVE-2025-15224 fixed in no fix yet
High 15 known vulnerabilities in systemd@247.3-7 (itechuw/openelis-global-2-database:develop)
How to fix
Update systemd from 247.3-7 to 247.3-7+deb11u6 or later in itechuw/openelis-global-2-database:develop. 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+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-2023-50387 fixed in 247.3-7+deb11u6
- High CVE-2023-50868 fixed in 247.3-7+deb11u6
- Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
- Medium CVE-2022-3821 fixed in 247.3-7+deb11u2
- Medium CVE-2022-4415 fixed in 247.3-7+deb11u2
- Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- 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
High 15 known vulnerabilities in systemd@247.3-7 (postgres:14.4)
How to fix
Update systemd from 247.3-7 to 247.3-7+deb11u6 or later in postgres:14.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 247.3-7+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-2023-50387 fixed in 247.3-7+deb11u6
- High CVE-2023-50868 fixed in 247.3-7+deb11u6
- Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
- Medium CVE-2022-3821 fixed in 247.3-7+deb11u2
- Medium CVE-2022-4415 fixed in 247.3-7+deb11u2
- Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- 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
High 14 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u1 (itechuw/openelis-global-2-database:develop)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u1 to 3.7.1-5+deb11u3 or later in itechuw/openelis-global-2-database:develop. 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+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-2023-0361 fixed in 3.7.1-5+deb11u3
- High CVE-2022-2509 fixed in 3.7.1-5+deb11u2
- High CVE-2024-0553 fixed in 3.7.1-5+deb11u5
- High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
- Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
- Low CVE-2011-3389 fixed in no fix yet
High 14 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u1 (postgres:14.4)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u1 to 3.7.1-5+deb11u3 or later in postgres:14.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.7.1-5+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-2023-0361 fixed in 3.7.1-5+deb11u3
- High CVE-2022-2509 fixed in 3.7.1-5+deb11u2
- High CVE-2024-0553 fixed in 3.7.1-5+deb11u5
- High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
- Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
- Low CVE-2011-3389 fixed in no fix yet
High 13 known vulnerabilities in elasticsearch@7.17.3 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update elasticsearch from 7.17.3 to 7.17.13 or later in hapiproject/hapi:v6.6.0-tomcat. 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 systemd@247.3-7%2Bdeb11u2 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update systemd from 247.3-7%2Bdeb11u2 to 247.3-7+deb11u6 or later in hapiproject/hapi:v6.6.0-tomcat. 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+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-2023-50387 fixed in 247.3-7+deb11u6
- High CVE-2023-50868 fixed in 247.3-7+deb11u6
- Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
- Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- 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
High 13 known vulnerabilities in elasticsearch@7.17.3 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update elasticsearch from 7.17.3 to 7.17.13 or later in itechuw/openelis-global-2-fhir:develop. 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 systemd@247.3-7%2Bdeb11u2 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update systemd from 247.3-7%2Bdeb11u2 to 247.3-7+deb11u6 or later in itechuw/openelis-global-2-fhir:develop. 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+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-2023-50387 fixed in 247.3-7+deb11u6
- High CVE-2023-50868 fixed in 247.3-7+deb11u6
- Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
- Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- 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
High 12 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u3 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u3 to 3.7.1-5+deb11u5 or later in hapiproject/hapi:v6.6.0-tomcat. 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+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-2024-0553 fixed in 3.7.1-5+deb11u5
- High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
- Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
- Low CVE-2011-3389 fixed in no fix yet
High 12 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u3 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u3 to 3.7.1-5+deb11u5 or later in itechuw/openelis-global-2-fhir:develop. 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+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-2024-0553 fixed in 3.7.1-5+deb11u5
- High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
- Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
- Low CVE-2011-3389 fixed in no fix yet
High 11 known vulnerabilities in netty-codec-http@4.1.42.Final (itechuw/openelis-global-2-dev:develop)
How to fix
Update netty-codec-http from 4.1.42.Final to 4.1.132.Final or later in itechuw/openelis-global-2-dev:develop. 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.132.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-33870 fixed in 4.1.132.Final
- High CVE-2019-20444 fixed in 4.1.44
- High CVE-2019-20445 fixed in 4.1.44.Final
- Medium CVE-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-43797 fixed in 4.1.71.Final
- Medium CVE-2025-67735 fixed in 4.1.129.Final
- Low CVE-2025-58056 fixed in 4.1.125.Final
High 11 known vulnerabilities in curl@8.14.1-r2 (itechuw/openelis-global-2-frontend:develop)
How to fix
No fixed version of curl is available yet. Check whether itechuw/openelis-global-2-frontend:develop needs curl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-3805 fixed in no fix yet
- Medium CVE-2025-10966 fixed in no fix yet
- Medium CVE-2025-14524 fixed in no fix yet
- Medium CVE-2025-14819 fixed in no fix yet
- Medium CVE-2025-15079 fixed in no fix yet
- Medium CVE-2026-3783 fixed in no fix yet
- Medium CVE-2025-13034 fixed in no fix yet
- Medium CVE-2025-14017 fixed in no fix yet
- Medium CVE-2026-1965 fixed in no fix yet
- Medium CVE-2026-3784 fixed in no fix yet
- Low CVE-2025-15224 fixed in no fix yet
High 11 known vulnerabilities in netty-codec-http@4.1.42.Final (itechuw/openelis-global-2:develop)
How to fix
Update netty-codec-http from 4.1.42.Final to 4.1.132.Final or later in itechuw/openelis-global-2:develop. 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.132.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-33870 fixed in 4.1.132.Final
- High CVE-2019-20444 fixed in 4.1.44
- High CVE-2019-20445 fixed in 4.1.44.Final
- Medium CVE-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-43797 fixed in 4.1.71.Final
- Medium CVE-2025-67735 fixed in 4.1.129.Final
- Low CVE-2025-58056 fixed in 4.1.125.Final
High 11 known vulnerabilities in libpng@1.6.47-r0 (nginx:1.27-alpine)
How to fix
Update libpng from 1.6.47-r0 to 1.6.53-r0 or later in nginx:1.27-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.6.53-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-64720 fixed in 1.6.53-r0
- High CVE-2025-65018 fixed in 1.6.53-r0
- High CVE-2025-66293 fixed in 1.6.53-r0
- High CVE-2026-33416 fixed in 1.6.56-r0
- High CVE-2026-33636 fixed in 1.6.56-r0
- High CVE-2026-25646 fixed in 1.6.55-r0
- Medium CVE-2026-34757 fixed in 1.6.57-r0
- Medium CVE-2025-64505 fixed in 1.6.53-r0
- Medium CVE-2025-64506 fixed in 1.6.53-r0
- Medium CVE-2026-22695 fixed in 1.6.54-r0
- Medium CVE-2026-22801 fixed in 1.6.54-r0
High 10 known vulnerabilities in runc@1.0.1 (itechuw/openelis-global-2-database:develop)
How to fix
Update runc from 1.0.1 to 1.1.5 or later in itechuw/openelis-global-2-database:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-27561 fixed in 1.1.5
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2022-29162 fixed in 1.1.2
- Medium CVE-2021-43784 fixed in 1.0.3
- Medium CVE-2023-28642 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 10 known vulnerabilities in runc@1.0.1 (postgres:14.4)
How to fix
Update runc from 1.0.1 to 1.1.5 or later in postgres:14.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.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-27561 fixed in 1.1.5
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2022-29162 fixed in 1.1.2
- Medium CVE-2021-43784 fixed in 1.0.3
- Medium CVE-2023-28642 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 9 known vulnerabilities in urllib3@1.25.8 (itechuw/certgen:main)
How to fix
Update urllib3 from 1.25.8 to 1.26.17 or later in itechuw/certgen:main. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26.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-43804 fixed in 1.26.17
- High CVE-2021-33503 fixed in 1.26.5
- High CVE-2025-66418 fixed in 2.6.0
- High CVE-2025-66471 fixed in 2.6.0
- High CVE-2026-21441 fixed in 2.6.3
- Medium CVE-2024-37891 fixed in 1.26.19
- Medium CVE-2025-50181 fixed in 2.5.0
- Medium CVE-2023-45803 fixed in 1.26.18
- Medium CVE-2020-26137 fixed in 1.25.9
High 9 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u1 (itechuw/openelis-global-2-database:develop)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u6 or later in itechuw/openelis-global-2-database:develop. 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
- High CVE-2024-37370 fixed in 1.18.3-6+deb11u5
- High CVE-2022-42898 fixed in 1.18.3-6+deb11u3
- High CVE-2024-37371 fixed in 1.18.3-6+deb11u5
- Medium CVE-2025-3576 fixed in 1.18.3-6+deb11u7
- Medium CVE-2023-36054 fixed in 1.18.3-6+deb11u4
- 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 9 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u1 (postgres:14.4)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u6 or later in postgres:14.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.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
- High CVE-2024-37370 fixed in 1.18.3-6+deb11u5
- High CVE-2022-42898 fixed in 1.18.3-6+deb11u3
- High CVE-2024-37371 fixed in 1.18.3-6+deb11u5
- Medium CVE-2025-3576 fixed in 1.18.3-6+deb11u7
- Medium CVE-2023-36054 fixed in 1.18.3-6+deb11u4
- 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 8 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u3 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u3 to 1.18.3-6+deb11u6 or later in hapiproject/hapi:v6.6.0-tomcat. 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
- High CVE-2024-37370 fixed in 1.18.3-6+deb11u5
- High CVE-2024-37371 fixed in 1.18.3-6+deb11u5
- Medium CVE-2025-3576 fixed in 1.18.3-6+deb11u7
- Medium CVE-2023-36054 fixed in 1.18.3-6+deb11u4
- 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
and 149 more groups with 396 findings
Medium 140
Medium 7 known vulnerabilities in sqlite3@3.34.1-3 (itechuw/openelis-global-2-database:develop)
How to fix
Update sqlite3 from 3.34.1-3 to 3.34.1-3+deb11u1 or later in itechuw/openelis-global-2-database:develop. 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.34.1-3+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-7104 fixed in 3.34.1-3+deb11u1
- Low CVE-2021-36690 fixed in 3.34.1-3+deb11u1
- 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
Medium 7 known vulnerabilities in sqlite3@3.34.1-3 (postgres:14.4)
How to fix
Update sqlite3 from 3.34.1-3 to 3.34.1-3+deb11u1 or later in postgres:14.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.34.1-3+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-7104 fixed in 3.34.1-3+deb11u1
- Low CVE-2021-36690 fixed in 3.34.1-3+deb11u1
- 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
Medium 4 known vulnerabilities in shadow@1%3A4.8.1-1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in hapiproject/hapi:v6.6.0-tomcat. 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 4 known vulnerabilities in requests@2.22.0 (itechuw/certgen:main)
How to fix
Update requests from 2.22.0 to 2.33.0 or later in itechuw/certgen:main. 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.33.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-25645 fixed in 2.33.0
- Medium CVE-2024-47081 fixed in 2.32.4
- Medium CVE-2024-35195 fixed in 2.32.0
- Medium CVE-2023-32681 fixed in 2.31.0
Medium 4 known vulnerabilities in shadow@1%3A4.8.1-1 (itechuw/openelis-global-2-database:develop)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in itechuw/openelis-global-2-database:develop. 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 4 known vulnerabilities in shadow@1%3A4.8.1-1 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in itechuw/openelis-global-2-fhir:develop. 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 4 known vulnerabilities in shadow@1%3A4.8.1-1 (postgres:14.4)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in postgres:14.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: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 3 known vulnerabilities in spring-context@5.3.27 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update spring-context from 5.3.27 to 6.1.14 or later in hapiproject/hapi:v6.6.0-tomcat. 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.1.14); 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-38827 fixed in 6.1.14
- Medium CVE-2024-38820 fixed in no fix yet
- Low CVE-2025-22233 fixed in no fix yet
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in hapiproject/hapi:v6.6.0-tomcat. 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.34+dfsg-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-39804 fixed in 1.34+dfsg-1+deb11u1
- Low CVE-2005-2541 fixed in no fix yet
- Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1
Medium 3 known vulnerabilities in guava@19.0 (itechuw/certgen:main)
How to fix
Update guava from 19.0 to 32.0.0-android or later in itechuw/certgen:main. 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-2018-10237 fixed in 24.1.1-android
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (itechuw/openelis-global-2-database:develop)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in itechuw/openelis-global-2-database:develop. 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.34+dfsg-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-39804 fixed in 1.34+dfsg-1+deb11u1
- Low CVE-2005-2541 fixed in no fix yet
- Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1
Medium 3 known vulnerabilities in log4j-core@2.17.1 (itechuw/openelis-global-2-dev:develop)
How to fix
Update log4j-core from 2.17.1 to 2.25.3 or later in itechuw/openelis-global-2-dev:develop. 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 spring-context@5.3.27 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update spring-context from 5.3.27 to 6.1.14 or later in itechuw/openelis-global-2-fhir:develop. 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.1.14); 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-38827 fixed in 6.1.14
- Medium CVE-2024-38820 fixed in no fix yet
- Low CVE-2025-22233 fixed in no fix yet
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in itechuw/openelis-global-2-fhir:develop. 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.34+dfsg-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-39804 fixed in 1.34+dfsg-1+deb11u1
- Low CVE-2005-2541 fixed in no fix yet
- Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1
Medium 3 known vulnerabilities in log4j-core@2.17.1 (itechuw/openelis-global-2:develop)
How to fix
Update log4j-core from 2.17.1 to 2.25.3 or later in itechuw/openelis-global-2:develop. 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 busybox@1.37.0-r12 (nginx:1.27-alpine)
How to fix
No fixed version of busybox is available yet. Check whether nginx:1.27-alpine needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2025-60876 fixed in no fix yet
- Low CVE-2024-58251 fixed in 1.37.0-r14
- Low CVE-2025-46394 fixed in 1.37.0-r14
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (postgres:14.4)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in postgres:14.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.34+dfsg-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-39804 fixed in 1.34+dfsg-1+deb11u1
- Low CVE-2005-2541 fixed in no fix yet
- Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1
Medium 2 known vulnerabilities in commons-compress@1.21 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update commons-compress from 1.21 to 1.26.0 or later in hapiproject/hapi:v6.6.0-tomcat. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26.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-2024-25710 fixed in 1.26.0
- Medium CVE-2024-26308 fixed in 1.26.0
Medium 2 known vulnerabilities in guava@31.0.1-jre (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update guava from 31.0.1-jre to 32.0.0-android or later in hapiproject/hapi:v6.6.0-tomcat. 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
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 2 known vulnerabilities in hibernate-validator@6.1.5.Final (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update hibernate-validator from 6.1.5.Final to 6.2.0.Final or later in hapiproject/hapi:v6.6.0-tomcat. 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.0.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-2023-1932 fixed in 6.2.0.Final
- Medium CVE-2025-35036 fixed in 6.2.0.CR1
Medium 2 known vulnerabilities in spring-expression@5.3.27 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update spring-expression from 5.3.27 to 6.1.14 or later in hapiproject/hapi:v6.6.0-tomcat. 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.1.14); 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-38827 fixed in 6.1.14
- Medium CVE-2024-38808 fixed in 5.3.39
Medium 2 known vulnerabilities in commons-compress@1.21 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update commons-compress from 1.21 to 1.26.0 or later in itechuw/openelis-global-2-fhir:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26.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-2024-25710 fixed in 1.26.0
- Medium CVE-2024-26308 fixed in 1.26.0
Medium 2 known vulnerabilities in guava@31.0.1-jre (itechuw/openelis-global-2-fhir:develop)
How to fix
Update guava from 31.0.1-jre to 32.0.0-android or later in itechuw/openelis-global-2-fhir:develop. 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
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 2 known vulnerabilities in hibernate-validator@6.1.5.Final (itechuw/openelis-global-2-fhir:develop)
How to fix
Update hibernate-validator from 6.1.5.Final to 6.2.0.Final or later in itechuw/openelis-global-2-fhir:develop. 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.0.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-2023-1932 fixed in 6.2.0.Final
- Medium CVE-2025-35036 fixed in 6.2.0.CR1
Medium 2 known vulnerabilities in spring-expression@5.3.27 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update spring-expression from 5.3.27 to 6.1.14 or later in itechuw/openelis-global-2-fhir:develop. 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.1.14); 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-38827 fixed in 6.1.14
- Medium CVE-2024-38808 fixed in 5.3.39
Medium 2 known vulnerabilities in libavif@1.0.4-r0 (itechuw/openelis-global-2-frontend:develop)
How to fix
No fixed version of libavif is available yet. Check whether itechuw/openelis-global-2-frontend:develop needs libavif 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-48174 fixed in no fix yet
- Medium CVE-2025-48175 fixed in no fix yet
Medium 2 known vulnerabilities in libavif@1.0.4-r0 (nginx:1.27-alpine)
How to fix
No fixed version of libavif is available yet. Check whether nginx:1.27-alpine needs libavif 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-48174 fixed in no fix yet
- Medium CVE-2025-48175 fixed in no fix yet
Medium 2 known vulnerabilities in tiff@4.7.0-r0 (nginx:1.27-alpine)
How to fix
Update tiff from 4.7.0-r0 to 4.7.1-r0 or later in nginx:1.27-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.7.1-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-2025-8961 fixed in 4.7.1-r0
- Low CVE-2025-9165 fixed in 4.7.1-r0
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (nginx:1.27-alpine)
How to fix
Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in nginx:1.27-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.3.2-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-22184 fixed in 1.3.2-r0
- Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 1 known vulnerability in busybox@1.37.0-r30 (alpine/socat)
How to fix
No fixed version of busybox is available yet. Check whether alpine/socat needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2025-60876 fixed in no fix yet
Medium 1 known vulnerability in commons-lang3@3.12.0 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update commons-lang3 from 3.12.0 to 3.18.0 or later in hapiproject/hapi:v6.6.0-tomcat. 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 1 known vulnerability in jakarta.mail@1.6.5 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update jakarta.mail from 1.6.5 to 1.6.8 or later in hapiproject/hapi:v6.6.0-tomcat. 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 1 known vulnerability in json-path@2.5.0 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update json-path from 2.5.0 to 2.9.0 or later in hapiproject/hapi:v6.6.0-tomcat. 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.9.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-2023-51074 fixed in 2.9.0
Medium 1 known vulnerability in libtasn1-6@4.16.0-2%2Bdeb11u1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update libtasn1-6 from 4.16.0-2%2Bdeb11u1 to 4.16.0-2+deb11u2 or later in hapiproject/hapi:v6.6.0-tomcat. 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 poi@4.1.2 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update poi from 4.1.2 to 5.2.1 or later in hapiproject/hapi:v6.6.0-tomcat. 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.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-2022-26336 fixed in 5.2.1
Medium 1 known vulnerability in spring-beans@5.3.27 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update spring-beans from 5.3.27 to 6.1.14 or later in hapiproject/hapi:v6.6.0-tomcat. 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.1.14); 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-38827 fixed in 6.1.14
Medium 1 known vulnerability in spring-boot-actuator@2.7.11 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update spring-boot-actuator from 2.7.11 to 2.7.18 or later in hapiproject/hapi:v6.6.0-tomcat. 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.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-2023-34055 fixed in 2.7.18
Medium 1 known vulnerability in spring-jdbc@5.3.27 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update spring-jdbc from 5.3.27 to 6.1.14 or later in hapiproject/hapi:v6.6.0-tomcat. 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.1.14); 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-38827 fixed in 6.1.14
Medium 1 known vulnerability in spring-websocket@5.3.27 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of spring-websocket is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat needs spring-websocket 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-41254 fixed in no fix yet
Medium 1 known vulnerability in tomcat-websocket@9.0.75 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update tomcat-websocket from 9.0.75 to 9.0.86 or later in hapiproject/hapi:v6.6.0-tomcat. 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.0.86); 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-23672 fixed in 9.0.86
and 41 more groups with 41 findings
Low 108
Low 9 known vulnerabilities in curl@7.74.0-1.3%2Bdeb11u16 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of curl is available yet. Check whether itechuw/openelis-global-2-fhir:develop needs curl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2021-22922 fixed in no fix yet
- Low CVE-2021-22923 fixed in no fix yet
- Low CVE-2023-28320 fixed in no fix yet
- Low CVE-2024-2379 fixed in no fix yet
- Low CVE-2025-0725 fixed in no fix yet
- Low CVE-2025-10966 fixed in no fix yet
- Low CVE-2025-14017 fixed in no fix yet
- Low CVE-2025-15079 fixed in no fix yet
- Low CVE-2025-15224 fixed in no fix yet
Low 5 known vulnerabilities in pcre3@2%3A8.39-13 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of pcre3 is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of openldap is available yet. Check whether itechuw/openelis-global-2-database:develop 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 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of pcre3 is available yet. Check whether itechuw/openelis-global-2-database:develop 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 openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of openldap is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of pcre3 is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (postgres:14.4)
How to fix
No fixed version of openldap is available yet. Check whether postgres:14.4 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 (postgres:14.4)
How to fix
No fixed version of pcre3 is available yet. Check whether postgres:14.4 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 4 known vulnerabilities in libsepol@3.1-1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in hapiproject/hapi:v6.6.0-tomcat. 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 libsepol@3.1-1 (itechuw/openelis-global-2-database:develop)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in itechuw/openelis-global-2-database:develop. 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 libsepol@3.1-1 (itechuw/openelis-global-2-fhir:develop)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in itechuw/openelis-global-2-fhir:develop. 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 libsepol@3.1-1 (postgres:14.4)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in postgres:14.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.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 3 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of util-linux is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Low 3 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u1 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of util-linux is available yet. Check whether itechuw/openelis-global-2-database:develop 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 CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Low 3 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u1 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of util-linux is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Low 3 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u1 (postgres:14.4)
How to fix
No fixed version of util-linux is available yet. Check whether postgres:14.4 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 CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Low 2 known vulnerabilities in coreutils@8.32-4%2Bb1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of coreutils is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 coreutils@8.32-4%2Bb1 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of coreutils is available yet. Check whether itechuw/openelis-global-2-database:develop 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 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether itechuw/openelis-global-2-database:develop 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 coreutils@8.32-4%2Bb1 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of coreutils is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 coreutils@8.32-4%2Bb1 (postgres:14.4)
How to fix
No fixed version of coreutils is available yet. Check whether postgres:14.4 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 (postgres:14.4)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether postgres:14.4 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 1 known vulnerability in apt@2.2.4 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of apt is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of gcc-10 is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat 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 pcre2@10.36-2%2Bdeb11u1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of pcre2 is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat needs pcre2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2022-41409 fixed in no fix yet
Low 1 known vulnerability in sed@4.7-1 (hapiproject/hapi:v6.6.0-tomcat)
How to fix
No fixed version of sed is available yet. Check whether hapiproject/hapi:v6.6.0-tomcat needs sed at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2026-5958 fixed in no fix yet
Low 1 known vulnerability in apt@2.2.4 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of apt is available yet. Check whether itechuw/openelis-global-2-database:develop 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 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of gcc-10 is available yet. Check whether itechuw/openelis-global-2-database:develop 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 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of gcc-9 is available yet. Check whether itechuw/openelis-global-2-database:develop 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 sed@4.7-1 (itechuw/openelis-global-2-database:develop)
How to fix
No fixed version of sed is available yet. Check whether itechuw/openelis-global-2-database:develop needs sed at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2026-5958 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (itechuw/openelis-global-2-dev:develop)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether itechuw/openelis-global-2-dev:develop needs libgcrypt20 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2024-2236 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (itechuw/openelis-global-2-dev:develop)
How to fix
No fixed version of shadow is available yet. Check whether itechuw/openelis-global-2-dev:develop needs shadow at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2024-56433 fixed in no fix yet
Low 1 known vulnerability in apt@2.2.4 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of apt is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of gcc-10 is available yet. Check whether itechuw/openelis-global-2-fhir:develop 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 pcre2@10.36-2%2Bdeb11u1 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of pcre2 is available yet. Check whether itechuw/openelis-global-2-fhir:develop needs pcre2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2022-41409 fixed in no fix yet
Low 1 known vulnerability in sed@4.7-1 (itechuw/openelis-global-2-fhir:develop)
How to fix
No fixed version of sed is available yet. Check whether itechuw/openelis-global-2-fhir:develop needs sed at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2026-5958 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (itechuw/openelis-global-2:develop)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether itechuw/openelis-global-2:develop needs libgcrypt20 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2024-2236 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (itechuw/openelis-global-2:develop)
How to fix
No fixed version of shadow is available yet. Check whether itechuw/openelis-global-2:develop needs shadow at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2024-56433 fixed in no fix yet
and 4 more groups with 4 findings
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 21 Apr 2026; it may have changed since.
Scan your own repository
InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.