Repository scan
hub-foss
everwell/hub-foss · branch master · scanned 20 Apr 2026
High 3,305
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/episode-service:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/episode-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie. If the 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.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 58 known vulnerabilities in openjdk8@8.212.04-r0 (registry.gitlab.com/everwell/hub-foss/user-service:latest-master)
How to fix
Update openjdk8 from 8.212.04-r0 to 8.272.10-r0 or later in registry.gitlab.com/everwell/hub-foss/user-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.272.10-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-2020-14593 fixed in 8.272.10-r0
- High CVE-2020-2604 fixed in 8.242.08-r0
- High CVE-2020-14583 fixed in 8.272.10-r0
- High CVE-2020-2803 fixed in 8.252.09-r0
- High CVE-2020-2805 fixed in 8.252.09-r0
- Medium CVE-2020-14792 fixed in 8.272.10-r0
- Medium CVE-2019-2999 fixed in 8.232.09-r0
- Medium CVE-2019-2816 fixed in 8.222.10-r0
- Medium CVE-2019-2975 fixed in 8.232.09-r0
- Medium CVE-2020-14556 fixed in 8.272.10-r0
- Medium CVE-2020-2593 fixed in 8.242.08-r0
- Medium CVE-2020-2800 fixed in 8.252.09-r0
- Medium CVE-2019-2745 fixed in 8.222.10-r0
- Medium CVE-2019-2762 fixed in 8.222.10-r0
- Medium CVE-2019-2769 fixed in 8.222.10-r0
- Medium CVE-2019-7317 fixed in 8.222.10-r0
- Medium CVE-2020-14621 fixed in 8.272.10-r0
- Medium CVE-2020-14803 fixed in 8.272.10-r0
- Medium CVE-2020-2781 fixed in 8.252.09-r0
- Medium CVE-2020-2830 fixed in 8.252.09-r0
- and 38 more
High 55 known vulnerabilities in tomcat-embed-core@9.0.16 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master)
How to fix
Update tomcat-embed-core from 9.0.16 to 9.0.29 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.29); if 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-2019-12418 fixed in 9.0.29
- High CVE-2020-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2019-10072 fixed in 9.0.20
- High CVE-2019-17563 fixed in 9.0.30
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- and 35 more
High 55 known vulnerabilities in tomcat-embed-core@9.0.16 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie)
How to fix
Update tomcat-embed-core from 9.0.16 to 9.0.29 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie. If the 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.29); if 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-2019-12418 fixed in 9.0.29
- High CVE-2020-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2019-10072 fixed in 9.0.20
- High CVE-2019-17563 fixed in 9.0.30
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- and 35 more
High 53 known vulnerabilities in jackson-databind@2.9.8 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master)
How to fix
Update jackson-databind from 2.9.8 to 2.9.10 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.9.10); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2019-14893 fixed in 2.9.10
- High CVE-2019-12086 fixed in 2.9.9
- High CVE-2019-14439 fixed in 2.9.9.2
- High CVE-2019-14892 fixed in 2.9.10
- High CVE-2020-25649 fixed in 2.9.10.7
- High CVE-2020-36518 fixed in 2.12.6.1
- High CVE-2022-42003 fixed in 2.12.7.1
- High CVE-2020-10650 fixed in 2.9.10.4
- High CVE-2020-11619 fixed in 2.9.10.4
- High CVE-2020-11620 fixed in 2.9.10.4
- High CVE-2020-14060 fixed in 2.9.10.5
- High CVE-2020-14061 fixed in 2.9.10.5
- High CVE-2020-14062 fixed in 2.9.10.5
- High CVE-2020-14195 fixed in 2.9.10.5
- High CVE-2020-24616 fixed in 2.9.10.6
- High CVE-2020-24750 fixed in 2.9.10.6
- High CVE-2020-35490 fixed in 2.9.10.8
- High CVE-2020-35491 fixed in 2.9.10.8
- High CVE-2020-35728 fixed in 2.9.10.8
- High CVE-2020-36179 fixed in 2.9.10.8
- and 33 more
High 53 known vulnerabilities in jackson-databind@2.9.8 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie)
How to fix
Update jackson-databind from 2.9.8 to 2.9.10 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie. If the 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); if 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-2019-14893 fixed in 2.9.10
- High CVE-2019-12086 fixed in 2.9.9
- High CVE-2019-14439 fixed in 2.9.9.2
- High CVE-2019-14892 fixed in 2.9.10
- High CVE-2020-25649 fixed in 2.9.10.7
- High CVE-2020-36518 fixed in 2.12.6.1
- High CVE-2022-42003 fixed in 2.12.7.1
- High CVE-2020-10650 fixed in 2.9.10.4
- High CVE-2020-11619 fixed in 2.9.10.4
- High CVE-2020-11620 fixed in 2.9.10.4
- High CVE-2020-14060 fixed in 2.9.10.5
- High CVE-2020-14061 fixed in 2.9.10.5
- High CVE-2020-14062 fixed in 2.9.10.5
- High CVE-2020-14195 fixed in 2.9.10.5
- High CVE-2020-24616 fixed in 2.9.10.6
- High CVE-2020-24750 fixed in 2.9.10.6
- High CVE-2020-35490 fixed in 2.9.10.8
- High CVE-2020-35491 fixed in 2.9.10.8
- High CVE-2020-35728 fixed in 2.9.10.8
- High CVE-2020-36179 fixed in 2.9.10.8
- and 33 more
High 48 known vulnerabilities in tomcat-embed-core@9.0.31 (registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master)
How to fix
Update tomcat-embed-core from 9.0.31 to 7.0.104, or later in registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.104,); if 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-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- and 28 more
High 48 known vulnerabilities in tomcat-embed-core@9.0.31 (registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master)
How to fix
Update tomcat-embed-core from 9.0.31 to 7.0.104, or later in registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.104,); if 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-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- and 28 more
High 48 known vulnerabilities in tomcat-embed-core@9.0.34 (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update tomcat-embed-core from 9.0.34 to 7.0.104, or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.104,); if 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-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- and 28 more
High 48 known vulnerabilities in tomcat-embed-core@9.0.34 (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update tomcat-embed-core from 9.0.34 to 7.0.104, or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.104,); if 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-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- and 28 more
High 48 known vulnerabilities in tomcat-embed-core@9.0.34 (registry.gitlab.com/everwell/hub-foss/user-service:latest-master)
How to fix
Update tomcat-embed-core from 9.0.34 to 7.0.104, or later in registry.gitlab.com/everwell/hub-foss/user-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.104,); if 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-9484 fixed in 7.0.104,
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-11996 fixed in 9.0.35
- High CVE-2020-13934 fixed in 9.0.36
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- and 28 more
High 45 known vulnerabilities in tomcat-embed-core@9.0.36 (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update tomcat-embed-core from 9.0.36 to 9.0.41 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.41); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2021-25329 fixed in 9.0.41
- High CVE-2022-23181 fixed in 9.0.58
- High CVE-2024-50379 fixed in 9.0.98
- High CVE-2024-56337 fixed in 9.0.98
- High CVE-2020-13934 fixed in 8.5.57,
- High CVE-2020-13935 fixed in 9.0.37
- High CVE-2020-17527 fixed in 8.5.60,
- High CVE-2021-25122 fixed in 9.0.43
- High CVE-2021-30639 fixed in 9.0.45
- High CVE-2021-41079 fixed in 9.0.44
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- High CVE-2026-34487 fixed in 9.0.117
- High CVE-2025-55752 fixed in 9.0.109
- and 25 more
High 35 known vulnerabilities in tomcat-embed-core@9.0.60 (registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master)
How to fix
Update tomcat-embed-core from 9.0.60 to 9.0.98 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2024-56337 fixed in 9.0.98
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2022-45143 fixed in 9.0.69
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- 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-2024-34750 fixed in 9.0.90
- High CVE-2025-48988 fixed in 9.0.106
- High CVE-2026-29146 fixed in 9.0.116
- High CVE-2025-24813 fixed in 9.0.99
- Medium CVE-2023-28708 fixed in 10.1.6,
- Medium CVE-2025-49124 fixed in 9.0.106
- and 15 more
High 35 known vulnerabilities in tomcat-embed-core@9.0.60 (registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master)
How to fix
Update tomcat-embed-core from 9.0.60 to 9.0.98 or later in registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2024-56337 fixed in 9.0.98
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2022-45143 fixed in 9.0.69
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- 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-2024-34750 fixed in 9.0.90
- High CVE-2025-48988 fixed in 9.0.106
- High CVE-2026-29146 fixed in 9.0.116
- High CVE-2025-24813 fixed in 9.0.99
- Medium CVE-2023-28708 fixed in 10.1.6,
- Medium CVE-2025-49124 fixed in 9.0.106
- and 15 more
High 35 known vulnerabilities in tomcat-embed-core@9.0.60 (registry.gitlab.com/everwell/hub-foss/episode-service:latest-master)
How to fix
Update tomcat-embed-core from 9.0.60 to 9.0.98 or later in registry.gitlab.com/everwell/hub-foss/episode-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2024-56337 fixed in 9.0.98
- High CVE-2022-29885 fixed in 9.0.63
- High CVE-2022-42252 fixed in 9.0.68
- High CVE-2022-45143 fixed in 9.0.69
- High CVE-2023-24998 fixed in 9.0.71
- High CVE-2023-46589 fixed in 9.0.83
- High CVE-2025-48989 fixed in 9.0.108
- High CVE-2025-52520 fixed in 9.0.107
- High CVE-2025-53506 fixed in 9.0.107
- High CVE-2026-24880 fixed in 9.0.116
- 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-2024-34750 fixed in 9.0.90
- High CVE-2025-48988 fixed in 9.0.106
- High CVE-2026-29146 fixed in 9.0.116
- High CVE-2025-24813 fixed in 9.0.99
- Medium CVE-2023-28708 fixed in 10.1.6,
- Medium CVE-2025-49124 fixed in 9.0.106
- and 15 more
High 30 known vulnerabilities in netty-codec-http@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update netty-codec-http from 4.1.25.Final to 4.1.42.Final or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.42.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-2019-16869 fixed in 4.1.42.Final
- High CVE-2026-33870 fixed in 4.1.132.Final
- High CVE-2026-33870 fixed in 4.1.132.Final
- 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-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 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-21290 fixed in 4.1.59.Final
- and 10 more
High 30 known vulnerabilities in netty-codec-http@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update netty-codec-http from 4.1.25.Final to 4.1.42.Final or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.42.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-2019-16869 fixed in 4.1.42.Final
- High CVE-2026-33870 fixed in 4.1.132.Final
- High CVE-2026-33870 fixed in 4.1.132.Final
- 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-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2024-29025 fixed in 4.1.108.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 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-21290 fixed in 4.1.59.Final
- and 10 more
High 22 known vulnerabilities in curl@7.79.1-r0 (alpine/curl:3.14)
How to fix
Update curl from 7.79.1-r0 to 7.79.1-r1 or later in alpine/curl:3.14. If the 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.79.1-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-27775 fixed in 7.79.1-r1
- High CVE-2022-27781 fixed in 7.79.1-r2
- High CVE-2022-27782 fixed in 7.79.1-r2
- High CVE-2022-43551 fixed in 7.79.1-r4
- High CVE-2022-22576 fixed in 7.79.1-r1
- High CVE-2023-27533 fixed in 8.0.1-r0
- High CVE-2023-27534 fixed in 8.0.1-r0
- High CVE-2022-32207 fixed in 7.79.1-r2
- Medium CVE-2023-23916 fixed in 7.79.1-r5
- Medium CVE-2022-32205 fixed in 7.79.1-r2
- Medium CVE-2023-27538 fixed in 8.0.1-r0
- Medium CVE-2022-27774 fixed in 7.79.1-r1
- Medium CVE-2022-32208 fixed in 7.79.1-r2
- Medium CVE-2022-43552 fixed in 7.79.1-r4
- Medium CVE-2023-27535 fixed in 8.0.1-r0
- Medium CVE-2023-27536 fixed in 8.0.1-r0
- Medium CVE-2023-27537 fixed in 8.0.1-r0
- Medium CVE-2022-27776 fixed in 7.79.1-r1
- Medium CVE-2022-32206 fixed in 7.79.1-r2
- Low CVE-2023-23914 fixed in 7.79.1-r5
- and 2 more
High 17 known vulnerabilities in openssl@1.1.1f-1ubuntu2.16 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update openssl from 1.1.1f-1ubuntu2.16 to 1.1.1f-1ubuntu2.17 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.1f-1ubuntu2.17); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-0286 fixed in 1.1.1f-1ubuntu2.17
- Medium CVE-2022-4304 fixed in 1.1.1f-1ubuntu2.17
- Medium CVE-2023-2650 fixed in 1.1.1f-1ubuntu2.19
- Medium CVE-2022-4450 fixed in 1.1.1f-1ubuntu2.17
- Medium CVE-2023-0215 fixed in 1.1.1f-1ubuntu2.17
- Low CVE-2024-13176 fixed in 1.1.1f-1ubuntu2.24
- Low CVE-2024-2511 fixed in 1.1.1f-1ubuntu2.23
- Low CVE-2024-4741 fixed in 1.1.1f-1ubuntu2.23
- Low CVE-2024-5535 fixed in 1.1.1f-1ubuntu2.23
- Low CVE-2024-9143 fixed in 1.1.1f-1ubuntu2.24
- Low CVE-2023-0465 fixed in 1.1.1f-1ubuntu2.18
- Low CVE-2023-0466 fixed in 1.1.1f-1ubuntu2.18
- Low CVE-2023-3446 fixed in 1.1.1f-1ubuntu2.20
- Low CVE-2023-3817 fixed in 1.1.1f-1ubuntu2.20
- Low CVE-2023-5678 fixed in 1.1.1f-1ubuntu2.21
- Low CVE-2024-0727 fixed in 1.1.1f-1ubuntu2.21
- Low CVE-2023-0464 fixed in 1.1.1f-1ubuntu2.18
High 16 known vulnerabilities in elasticsearch@7.6.2 (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update elasticsearch from 7.6.2 to 7.17.13 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2021-22134 fixed in 7.11.0
- Medium CVE-2024-23450 fixed in 7.17.19
- Medium CVE-2021-22135 fixed in 7.11.2
- Medium CVE-2021-22144 fixed in 7.13.3
- Medium CVE-2025-37727 fixed in 8.18.8
- Medium CVE-2020-7019 fixed in 7.9.0
- 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-2025-37731 fixed in 8.19.8
- Medium CVE-2024-23444 fixed in 7.17.23
- Low CVE-2020-7020 fixed in 7.9.2
High 16 known vulnerabilities in netty-codec@4.1.49.Final (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update netty-codec from 4.1.49.Final to 4.1.68.Final or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.68.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2020-11612 fixed in 4.1.46.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
High 16 known vulnerabilities in netty-codec@4.1.49.Final (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update netty-codec from 4.1.49.Final to 4.1.68.Final or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.68.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37136 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2021-37137 fixed in 4.1.68.Final
- High CVE-2020-11612 fixed in 4.1.46.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
- Medium CVE-2025-58057 fixed in 4.1.125.Final
High 15 known vulnerabilities in netty-handler@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update netty-handler from 4.1.25.Final to 4.1.46 or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.46); if 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-11612 fixed in 4.1.46
- High CVE-2019-20444 fixed in 4.1.44
- Medium CVE-2019-20445 fixed in 4.1.45
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
High 15 known vulnerabilities in netty-handler@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update netty-handler from 4.1.25.Final to 4.1.46 or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.46); if 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-11612 fixed in 4.1.46
- High CVE-2019-20444 fixed in 4.1.44
- Medium CVE-2019-20445 fixed in 4.1.45
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
High 14 known vulnerabilities in elasticsearch@8.6.1 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update elasticsearch from 8.6.1 to 8.9.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.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
- High CVE-2023-31418 fixed in 8.9.0
- Medium CVE-2023-31417 fixed in 8.9.2
- Medium CVE-2023-49921 fixed in 8.11.2
- Medium CVE-2024-23449 fixed in 8.11.1
- Medium CVE-2024-23450 fixed in 8.13.0
- Medium CVE-2024-52981 fixed in 8.15.1
- Medium CVE-2025-37727 fixed in 8.18.8
- Medium CVE-2023-31419 fixed in 8.9.1
- Medium CVE-2023-46673 fixed in 8.10.3
- Medium CVE-2024-43709 fixed in 8.13.3
- Medium CVE-2024-52979 fixed in 8.16.0
- Medium CVE-2024-52980 fixed in 8.15.1
- Medium CVE-2025-37731 fixed in 8.19.8
- Medium CVE-2024-23444 fixed in 8.13.0
High 14 known vulnerabilities in netty-codec-http@4.1.50.Final (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update netty-codec-http from 4.1.50.Final to 4.1.132.Final or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.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-2026-33870 fixed in 4.1.132.Final
- Medium CVE-2024-29025 fixed in 4.1.108.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-2022-41915 fixed in 4.1.86.Final
- Medium CVE-2025-67735 fixed in 4.1.129.Final
- Medium CVE-2025-67735 fixed in 4.1.129.Final
- Low CVE-2025-58056 fixed in 4.1.125.Final
- Low CVE-2025-58056 fixed in 4.1.125.Final
High 13 known vulnerabilities in elasticsearch@7.12.1 (registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master)
How to fix
Update elasticsearch from 7.12.1 to 7.17.13 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2021-22144 fixed in 7.13.3
- Medium CVE-2025-37727 fixed in 8.18.8
- Medium CVE-2021-22147 fixed in 7.14.0
- 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-2025-37731 fixed in 8.19.8
- Medium CVE-2024-23444 fixed in 7.17.23
High 13 known vulnerabilities in elasticsearch@7.12.1 (registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master)
How to fix
Update elasticsearch from 7.12.1 to 7.17.13 or later in registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2021-22144 fixed in 7.13.3
- Medium CVE-2025-37727 fixed in 8.18.8
- Medium CVE-2021-22147 fixed in 7.14.0
- 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-2025-37731 fixed in 8.19.8
- Medium CVE-2024-23444 fixed in 7.17.23
High 13 known vulnerabilities in elasticsearch@7.12.1 (registry.gitlab.com/everwell/hub-foss/episode-service:latest-master)
How to fix
Update elasticsearch from 7.12.1 to 7.17.13 or later in registry.gitlab.com/everwell/hub-foss/episode-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-2021-22144 fixed in 7.13.3
- Medium CVE-2025-37727 fixed in 8.18.8
- Medium CVE-2021-22147 fixed in 7.14.0
- 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-2025-37731 fixed in 8.19.8
- Medium CVE-2024-23444 fixed in 7.17.23
High 13 known vulnerabilities in netty-codec-http2@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update netty-codec-http2 from 4.1.25.Final to 4.1.100.Final or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.100.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-2023-44487 fixed in 4.1.100.Final
- High CVE-2023-44487 fixed in 4.1.100.Final
- High GHSA-xpw8-rcwv-8f8p fixed in 4.1.100.Final
- High GHSA-xpw8-rcwv-8f8p fixed in 4.1.100.Final
- High CVE-2025-55163 fixed in 4.1.124.Final
- High CVE-2025-55163 fixed in 4.1.124.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
- High CVE-2020-11612 fixed in 4.1.46.Final
- Medium CVE-2021-21295 fixed in 4.1.60.Final
- Medium CVE-2021-21295 fixed in 4.1.60.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
High 13 known vulnerabilities in netty-codec-http2@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update netty-codec-http2 from 4.1.25.Final to 4.1.100.Final or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.100.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-2023-44487 fixed in 4.1.100.Final
- High CVE-2023-44487 fixed in 4.1.100.Final
- High GHSA-xpw8-rcwv-8f8p fixed in 4.1.100.Final
- High GHSA-xpw8-rcwv-8f8p fixed in 4.1.100.Final
- High CVE-2025-55163 fixed in 4.1.124.Final
- High CVE-2025-55163 fixed in 4.1.124.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
- High CVE-2020-11612 fixed in 4.1.46.Final
- Medium CVE-2021-21295 fixed in 4.1.60.Final
- Medium CVE-2021-21295 fixed in 4.1.60.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
and 523 more groups with 1,791 findings
Medium 547
Medium 23 known vulnerabilities in openssl@3.0.2-0ubuntu1.14 (rabbitmq:3.9)
How to fix
Update openssl from 3.0.2-0ubuntu1.14 to 3.0.2-0ubuntu1.21 or later in rabbitmq:3.9. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.2-0ubuntu1.21); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-15467 fixed in 3.0.2-0ubuntu1.21
- Medium CVE-2025-9230 fixed in 3.0.2-0ubuntu1.20
- Medium CVE-2026-31790 fixed in 3.0.2-0ubuntu1.23
- Medium CVE-2022-40735 fixed in 3.0.2-0ubuntu1.16
- Medium CVE-2024-6119 fixed in 3.0.2-0ubuntu1.18
- Low CVE-2024-13176 fixed in 3.0.2-0ubuntu1.19
- Low CVE-2024-2511 fixed in 3.0.2-0ubuntu1.17
- Low CVE-2024-4603 fixed in 3.0.2-0ubuntu1.17
- Low CVE-2024-4741 fixed in 3.0.2-0ubuntu1.17
- Low CVE-2024-5535 fixed in 3.0.2-0ubuntu1.17
- Low CVE-2024-9143 fixed in 3.0.2-0ubuntu1.19
- Low CVE-2025-68160 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2025-69418 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2025-69419 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2025-69420 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2026-22795 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2026-22796 fixed in 3.0.2-0ubuntu1.21
- Low CVE-2026-28387 fixed in 3.0.2-0ubuntu1.23
- Low CVE-2026-28388 fixed in 3.0.2-0ubuntu1.23
- Low CVE-2026-28389 fixed in 3.0.2-0ubuntu1.23
- and 3 more
Medium 14 known vulnerabilities in curl@7.68.0-1ubuntu2.15 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update curl from 7.68.0-1ubuntu2.15 to 7.68.0-1ubuntu2.22 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.68.0-1ubuntu2.22); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-2398 fixed in 7.68.0-1ubuntu2.22
- Medium CVE-2024-8096 fixed in 7.68.0-1ubuntu2.24
- Medium CVE-2023-27535 fixed in 7.68.0-1ubuntu2.18
- Medium CVE-2023-23916 fixed in 7.68.0-1ubuntu2.16
- Medium CVE-2023-46218 fixed in 7.68.0-1ubuntu2.21
- Medium CVE-2024-7264 fixed in 7.68.0-1ubuntu2.23
- Low CVE-2024-11053 fixed in 7.68.0-1ubuntu2.25
- Low CVE-2023-28322 fixed in 7.68.0-1ubuntu2.19
- Low CVE-2023-38546 fixed in 7.68.0-1ubuntu2.20
- Low CVE-2023-27538 fixed in 7.68.0-1ubuntu2.18
- Low CVE-2023-27536 fixed in 7.68.0-1ubuntu2.18
- Low CVE-2023-28321 fixed in 7.68.0-1ubuntu2.19
- Low CVE-2023-27533 fixed in 7.68.0-1ubuntu2.18
- Low CVE-2023-27534 fixed in 7.68.0-1ubuntu2.18
Medium 12 known vulnerabilities in netty-common@4.1.25.Final (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update netty-common from 4.1.25.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 12 known vulnerabilities in netty-common@4.1.49.Final (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update netty-common from 4.1.49.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 11 known vulnerabilities in krb5@1.17-6ubuntu4.1 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update krb5 from 1.17-6ubuntu4.1 to 1.17-6ubuntu4.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.17-6ubuntu4.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-24528 fixed in 1.17-6ubuntu4.9
- Medium CVE-2025-3576 fixed in 1.17-6ubuntu4.11
- Medium CVE-2021-37750 fixed in 1.17-6ubuntu4.3
- Medium CVE-2023-36054 fixed in 1.17-6ubuntu4.4
- Medium CVE-2021-36222 fixed in 1.17-6ubuntu4.3
- Medium CVE-2024-37370 fixed in 1.17-6ubuntu4.6
- Medium CVE-2022-42898 fixed in 1.17-6ubuntu4.2
- Medium CVE-2024-3596 fixed in 1.17-6ubuntu4.8
- Medium CVE-2024-37371 fixed in 1.17-6ubuntu4.6
- Low CVE-2024-26458 fixed in 1.17-6ubuntu4.9
- Low CVE-2024-26461 fixed in 1.17-6ubuntu4.9
Medium 11 known vulnerabilities in glibc@2.35-0ubuntu3.6 (rabbitmq:3.9)
How to fix
Update glibc from 2.35-0ubuntu3.6 to 2.35-0ubuntu3.7 or later in rabbitmq:3.9. If the 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.35-0ubuntu3.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-2961 fixed in 2.35-0ubuntu3.7
- Medium CVE-2024-33599 fixed in 2.35-0ubuntu3.8
- Medium CVE-2024-33600 fixed in 2.35-0ubuntu3.8
- Medium CVE-2024-33601 fixed in 2.35-0ubuntu3.8
- Medium CVE-2024-33602 fixed in 2.35-0ubuntu3.8
- Medium CVE-2025-0395 fixed in 2.35-0ubuntu3.9
- Medium CVE-2025-15281 fixed in 2.35-0ubuntu3.13
- Medium CVE-2025-4802 fixed in 2.35-0ubuntu3.10
- Medium CVE-2025-8058 fixed in 2.35-0ubuntu3.11
- Medium CVE-2026-0861 fixed in 2.35-0ubuntu3.13
- Medium CVE-2026-0915 fixed in 2.35-0ubuntu3.13
Medium 9 known vulnerabilities in glibc@2.31-0ubuntu9.9 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update glibc from 2.31-0ubuntu9.9 to 2.31-0ubuntu9.15 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.31-0ubuntu9.15); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-2961 fixed in 2.31-0ubuntu9.15
- Medium CVE-2024-33599 fixed in 2.31-0ubuntu9.16
- Medium CVE-2024-33600 fixed in 2.31-0ubuntu9.16
- Medium CVE-2024-33601 fixed in 2.31-0ubuntu9.16
- Medium CVE-2024-33602 fixed in 2.31-0ubuntu9.16
- Medium CVE-2025-0395 fixed in 2.31-0ubuntu9.17
- Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
- Low CVE-2023-4806 fixed in 2.31-0ubuntu9.14
- Low CVE-2023-4813 fixed in 2.31-0ubuntu9.14
Medium 9 known vulnerabilities in gnutls28@3.7.3-4ubuntu1.4 (rabbitmq:3.9)
How to fix
Update gnutls28 from 3.7.3-4ubuntu1.4 to 3.7.3-4ubuntu1.6 or later in rabbitmq:3.9. If the 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.3-4ubuntu1.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 CVE-2024-12243 fixed in 3.7.3-4ubuntu1.6
- Medium CVE-2024-28834 fixed in 3.7.3-4ubuntu1.5
- Medium CVE-2024-28835 fixed in 3.7.3-4ubuntu1.5
- Medium CVE-2025-14831 fixed in 3.7.3-4ubuntu1.8
- Medium CVE-2025-32989 fixed in 3.7.3-4ubuntu1.7
- Medium CVE-2025-6395 fixed in 3.7.3-4ubuntu1.7
- Medium CVE-2025-32988 fixed in 3.7.3-4ubuntu1.7
- Medium CVE-2025-32990 fixed in 3.7.3-4ubuntu1.7
- Low CVE-2025-9820 fixed in 3.7.3-4ubuntu1.8
Medium 7 known vulnerabilities in bcprov-jdk15on@1.64 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update bcprov-jdk15on from 1.64 to 1.66 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.66
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 7 known vulnerabilities in krb5@1.19.2-2ubuntu0.3 (rabbitmq:3.9)
How to fix
Update krb5 from 1.19.2-2ubuntu0.3 to 1.19.2-2ubuntu0.6 or later in rabbitmq:3.9. If the 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.2-2ubuntu0.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 CVE-2025-24528 fixed in 1.19.2-2ubuntu0.6
- Medium CVE-2025-3576 fixed in 1.19.2-2ubuntu0.7
- Medium CVE-2024-37370 fixed in 1.19.2-2ubuntu0.4
- Medium CVE-2024-3596 fixed in 1.19.2-2ubuntu0.5
- Medium CVE-2024-37371 fixed in 1.19.2-2ubuntu0.4
- Low CVE-2024-26458 fixed in 1.19.2-2ubuntu0.6
- Low CVE-2024-26461 fixed in 1.19.2-2ubuntu0.6
Medium 7 known vulnerabilities in bcprov-jdk15on@1.64 (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update bcprov-jdk15on from 1.64 to 1.66 or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.66
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 7 known vulnerabilities in bcprov-jdk15on@1.60 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master)
How to fix
Update bcprov-jdk15on from 1.60 to 1.66 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.66
- Medium CVE-2020-26939 fixed in 1.61
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
Medium 7 known vulnerabilities in bcprov-jdk15on@1.60 (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie)
How to fix
Update bcprov-jdk15on from 1.60 to 1.66 or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.66
- Medium CVE-2020-26939 fixed in 1.61
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
Medium 7 known vulnerabilities in bcprov-jdk15on@1.64 (registry.gitlab.com/everwell/hub-foss/user-service:latest-master)
How to fix
Update bcprov-jdk15on from 1.64 to 1.66 or later in registry.gitlab.com/everwell/hub-foss/user-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.66
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in guava@27.1-jre (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update guava from 27.1-jre to 32.0.0-android or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 32.0.0-android); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Low CVE-2020-8908 fixed in 32.0.0-android
- Low CVE-2020-8908 fixed in 32.0.0-android
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 6 known vulnerabilities in log4j-core@2.12.4 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update log4j-core from 2.12.4 to 2.25.3 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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 6 known vulnerabilities in bcprov-jdk15on@1.67 (registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in bcprov-jdk15on@1.67 (registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in netty-common@4.1.84.Final (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update netty-common from 4.1.84.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 6 known vulnerabilities in bcprov-jdk15on@1.68 (registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in bcprov-jdk15on@1.68 (registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in bcprov-jdk15on@1.68 (registry.gitlab.com/everwell/hub-foss/episode-service:latest-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/episode-service:latest-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in bcprov-jdk15on@1.69 (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 6 known vulnerabilities in bcprov-jdk15on@1.69 (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
No fixed version of bcprov-jdk15on is available yet. Check whether registry.gitlab.com/everwell/hub-foss/ins:latest-master needs bcprov-jdk15on at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-33201 fixed in no fix yet
- Medium CVE-2024-29857 fixed in 1.78
- Medium CVE-2024-30172 fixed in 1.78
- Medium CVE-2023-33202 fixed in no fix yet
- Medium CVE-2024-30171 fixed in 1.78
- Medium CVE-2024-34447 fixed in 1.78
Medium 5 known vulnerabilities in gnutls28@3.6.13-2ubuntu1.7 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update gnutls28 from 3.6.13-2ubuntu1.7 to 3.6.13-2ubuntu1.12 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.6.13-2ubuntu1.12); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-12243 fixed in 3.6.13-2ubuntu1.12
- Medium CVE-2024-28834 fixed in 3.6.13-2ubuntu1.11
- Medium CVE-2023-5981 fixed in 3.6.13-2ubuntu1.9
- Medium CVE-2023-0361 fixed in 3.6.13-2ubuntu1.8
- Medium CVE-2024-0553 fixed in 3.6.13-2ubuntu1.10
Medium 5 known vulnerabilities in libssh@0.9.3-2ubuntu2.2 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update libssh from 0.9.3-2ubuntu2.2 to 0.9.3-2ubuntu2.5 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.9.3-2ubuntu2.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-6004 fixed in 0.9.3-2ubuntu2.5
- Medium CVE-2023-6918 fixed in 0.9.3-2ubuntu2.5
- Medium CVE-2023-48795 fixed in 0.9.3-2ubuntu2.4
- Medium CVE-2023-1667 fixed in 0.9.3-2ubuntu2.3
- Medium CVE-2023-2283 fixed in 0.9.3-2ubuntu2.3
Medium 5 known vulnerabilities in netty-handler@4.1.50.Final (registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master)
How to fix
Update netty-handler from 4.1.50.Final to 4.1.59.Final or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.59.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-2021-21290 fixed in 4.1.59.Final
- Medium CVE-2021-21295 fixed in 4.1.61.Final
- Medium CVE-2021-21409 fixed in 4.1.61.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
- Medium CVE-2023-34462 fixed in 4.1.94.Final
Medium 5 known vulnerabilities in netty-common@4.1.84.Final (registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master)
How to fix
Update netty-common from 4.1.84.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/dispensation-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 5 known vulnerabilities in netty-common@4.1.75.Final (registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master)
How to fix
Update netty-common from 4.1.75.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/episode-service:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 5 known vulnerabilities in netty-common@4.1.84.Final (registry.gitlab.com/everwell/hub-foss/episode-service:latest-master)
How to fix
Update netty-common from 4.1.84.Final to 4.1.115.Final or later in registry.gitlab.com/everwell/hub-foss/episode-service:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2024-47535 fixed in 4.1.115.Final
- Medium CVE-2022-24823 fixed in 4.1.77.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
- Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 5 known vulnerabilities in guava@20.0 (registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master)
How to fix
Update guava from 20.0 to 32.0.0-android or later in registry.gitlab.com/everwell/hub-foss/ins:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 32.0.0-android); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2018-10237 fixed in 24.1.1-android
- Low CVE-2020-8908 fixed in 32.0.0-android
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 5 known vulnerabilities in guava@29.0-jre (registry.gitlab.com/everwell/hub-foss/ins:latest-master)
How to fix
Update guava from 29.0-jre to 32.0.0-android or later in registry.gitlab.com/everwell/hub-foss/ins:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 32.0.0-android); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2018-10237 fixed in 24.1.1-android
- Low CVE-2020-8908 fixed in 32.0.0-android
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 4 known vulnerabilities in bc-fips@1.0.2 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update bc-fips from 1.0.2 to 1.0.2.1 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.0.2.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-15522 fixed in 1.0.2.1
- Medium CVE-2024-29857 fixed in 1.0.2.5
- Medium CVE-2022-45146 fixed in 1.0.2.4
- Medium CVE-2025-8885 fixed in 2.1.0
Medium 4 known vulnerabilities in hibernate-validator@6.0.14.Final (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master)
How to fix
Update hibernate-validator from 6.0.14.Final to 6.0.20.Final or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.0.20.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-2020-10693 fixed in 6.0.20.Final
- Medium CVE-2023-1932 fixed in 6.2.0.Final
- Medium CVE-2019-10219 fixed in 6.0.18.Final
- Medium CVE-2025-35036 fixed in 6.2.0.CR1
Medium 4 known vulnerabilities in hibernate-validator@6.0.14.Final (registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie)
How to fix
Update hibernate-validator from 6.0.14.Final to 6.0.20.Final or later in registry.gitlab.com/everwell/hub-foss/iam-backend:latest-openhie. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.0.20.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-2020-10693 fixed in 6.0.20.Final
- Medium CVE-2023-1932 fixed in 6.2.0.Final
- Medium CVE-2019-10219 fixed in 6.0.18.Final
- Medium CVE-2025-35036 fixed in 6.2.0.CR1
Medium 3 known vulnerabilities in ncurses@6.2-0ubuntu2 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update ncurses from 6.2-0ubuntu2 to 6.2-0ubuntu2.1 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.2-0ubuntu2.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-29491 fixed in 6.2-0ubuntu2.1
- Low CVE-2022-29458 fixed in 6.2-0ubuntu2.1
- Low CVE-2021-39537 fixed in 6.2-0ubuntu2.1
Medium 3 known vulnerabilities in sqlite3@3.31.1-4ubuntu0.5 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update sqlite3 from 3.31.1-4ubuntu0.5 to 3.31.1-4ubuntu0.7 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.31.1-4ubuntu0.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-52099 fixed in 3.31.1-4ubuntu0.7
- Medium CVE-2025-29088 fixed in 3.31.1-4ubuntu0.7
- Medium CVE-2023-7104 fixed in 3.31.1-4ubuntu0.6
Medium 3 known vulnerabilities in libtasn1-6@4.18.0-4build1 (rabbitmq:3.9)
How to fix
Update libtasn1-6 from 4.18.0-4build1 to 4.18.0-4ubuntu0.1 or later in rabbitmq:3.9. If the 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.18.0-4ubuntu0.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-12133 fixed in 4.18.0-4ubuntu0.1
- Medium CVE-2025-13151 fixed in 4.18.0-4ubuntu0.2
- Low CVE-2021-46848 fixed in 4.18.0-4ubuntu0.2
Medium 3 known vulnerabilities in systemd@249.11-0ubuntu3.12 (rabbitmq:3.9)
How to fix
Update systemd from 249.11-0ubuntu3.12 to 249.11-0ubuntu3.16 or later in rabbitmq:3.9. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 249.11-0ubuntu3.16); if 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 249.11-0ubuntu3.16
- Medium CVE-2026-29111 fixed in 249.11-0ubuntu3.19
- Low CVE-2023-7008 fixed in no fix yet
Medium 3 known vulnerabilities in guava@20.0 (registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master)
How to fix
Update guava from 20.0 to 32.0.0-android or later in registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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
and 197 more groups with 277 findings
Low 16
Low 3 known vulnerabilities in shadow@1%3A4.8.1-2ubuntu2.1 (rabbitmq:3.9)
How to fix
No fixed version of shadow is available yet. Check whether rabbitmq:3.9 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 CVE-2023-29383 fixed in no fix yet
- Low CVE-2023-4641 fixed in 1:4.8.1-2ubuntu2.2
Low 2 known vulnerabilities in gcc-12@12.3.0-1ubuntu1~22.04 (rabbitmq:3.9)
How to fix
Update gcc-12 from 12.3.0-1ubuntu1~22.04 to 12.3.0-1ubuntu1~22.04.2 or later in rabbitmq:3.9. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 12.3.0-1ubuntu1~22.04.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-2023-4039 fixed in 12.3.0-1ubuntu1~22.04.2
- Low CVE-2022-27943 fixed in no fix yet
Low 1 known vulnerability in openldap@2.4.49%2Bdfsg-2ubuntu1.9 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update openldap from 2.4.49%2Bdfsg-2ubuntu1.9 to 2.4.49+dfsg-2ubuntu1.10 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.4.49+dfsg-2ubuntu1.10); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2023-2953 fixed in 2.4.49+dfsg-2ubuntu1.10
Low 1 known vulnerability in procps@2%3A3.3.16-1ubuntu2.3 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update procps from 2%3A3.3.16-1ubuntu2.3 to 2:3.3.16-1ubuntu2.4 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2:3.3.16-1ubuntu2.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2023-4016 fixed in 2:3.3.16-1ubuntu2.4
Low 1 known vulnerability in shadow@1%3A4.8.1-1ubuntu5.20.04.4 (docker.elastic.co/elasticsearch/elasticsearch:8.6.1)
How to fix
Update shadow from 1%3A4.8.1-1ubuntu5.20.04.4 to 1:4.8.1-1ubuntu5.20.04.5 or later in docker.elastic.co/elasticsearch/elasticsearch:8.6.1. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1:4.8.1-1ubuntu5.20.04.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2023-4641 fixed in 1:4.8.1-1ubuntu5.20.04.5
Low 1 known vulnerability in dpkg@1.21.1ubuntu2.2 (rabbitmq:3.9)
How to fix
Update dpkg from 1.21.1ubuntu2.2 to 1.21.1ubuntu2.6 or later in rabbitmq:3.9. If the 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.1ubuntu2.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
- Low CVE-2025-6297 fixed in 1.21.1ubuntu2.6
Low 1 known vulnerability in libgcrypt20@1.9.4-3ubuntu3 (rabbitmq:3.9)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether rabbitmq:3.9 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 libzstd@1.4.8%2Bdfsg-3build1 (rabbitmq:3.9)
How to fix
No fixed version of libzstd is available yet. Check whether rabbitmq:3.9 needs libzstd 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-4899 fixed in no fix yet
Low 1 known vulnerability in ncurses@6.3-2ubuntu0.1 (rabbitmq:3.9)
How to fix
No fixed version of ncurses is available yet. Check whether rabbitmq:3.9 needs ncurses 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-50495 fixed in no fix yet
Low 1 known vulnerability in pcre2@10.39-3ubuntu0.1 (rabbitmq:3.9)
How to fix
No fixed version of pcre2 is available yet. Check whether rabbitmq:3.9 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 pcre3@2%3A8.39-13ubuntu0.22.04.1 (rabbitmq:3.9)
How to fix
No fixed version of pcre3 is available yet. Check whether rabbitmq:3.9 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 1 known vulnerability in commons-configuration@1.8 (registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master)
How to fix
No fixed version of commons-configuration is available yet. Check whether registry.gitlab.com/everwell/hub-foss/data-gateway:2023-03-09T1307110530-master needs commons-configuration at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2025-46392 fixed in no fix yet
Low 1 known vulnerability in commons-configuration@1.8 (registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master)
How to fix
No fixed version of commons-configuration is available yet. Check whether registry.gitlab.com/everwell/hub-foss/data-gateway:latest-master needs commons-configuration at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2025-46392 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 20 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.