Repository scan
bahmni-docker
Bahmni/bahmni-docker · branch master · scanned 23 Apr 2026
High 554
High 101 known vulnerabilities in stdlib@1.16.7 (postgres:9.6)
How to fix
Update stdlib from 1.16.7 to 1.19.9 or later in postgres:9.6. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.19.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2021-39293 fixed in 1.16.8
- High CVE-2021-41771 fixed in 1.16.10
- High CVE-2021-41772 fixed in 1.16.10
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-24921 fixed in 1.16.15
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-28327 fixed in 1.17.9
- High CVE-2022-2879 fixed in 1.18.7
- High CVE-2022-2880 fixed in 1.18.7
- High CVE-2022-29804 fixed in 1.17.11
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30631 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30633 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- and 81 more
High 90 known vulnerabilities in stdlib@1.18.2 (mysql:5.7)
How to fix
Update stdlib from 1.18.2 to 1.19.9 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.19.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.18.4
- High CVE-2022-2879 fixed in 1.18.7
- High CVE-2022-2880 fixed in 1.18.7
- High CVE-2022-29804 fixed in 1.18.3
- High CVE-2022-30630 fixed in 1.18.4
- High CVE-2022-30631 fixed in 1.18.4
- High CVE-2022-30632 fixed in 1.18.4
- High CVE-2022-30633 fixed in 1.18.4
- High CVE-2022-30634 fixed in 1.18.3
- High CVE-2022-30635 fixed in 1.18.4
- High CVE-2022-32189 fixed in 1.18.5
- High CVE-2022-41715 fixed in 1.18.7
- High CVE-2022-41716 fixed in 1.18.8
- High CVE-2022-41720 fixed in 1.18.9
- High CVE-2022-41722 fixed in 1.19.6
- High CVE-2022-41723 fixed in 1.19.6
- High CVE-2022-41724 fixed in 1.19.6
- and 70 more
High 55 known vulnerabilities in jackson-databind@2.6.5 (bahmni/atomfeed-console:latest)
How to fix
Update jackson-databind from 2.6.5 to 2.7.9.4 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.9.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2018-12022 fixed in 2.7.9.4
- High CVE-2019-12086 fixed in 2.6.7.3
- High CVE-2019-14439 fixed in 2.6.7.3
- High CVE-2019-14892 fixed in 2.6.7.3
- High CVE-2020-25649 fixed in 2.6.7.4
- High CVE-2020-36518 fixed in 2.12.6.1
- High CVE-2022-42003 fixed in 2.12.7.1
- High CVE-2018-5968 fixed in 2.7.9.5
- High CVE-2020-10650 fixed in 2.9.10.4
- High CVE-2020-24616 fixed in 2.9.10.6
- High CVE-2020-24750 fixed in 2.6.7.5
- 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.6.7.5
- High CVE-2020-36180 fixed in 2.6.7.5
- High CVE-2020-36181 fixed in 2.6.7.5
- High CVE-2020-36182 fixed in 2.6.7.5
- High CVE-2020-36183 fixed in 2.6.7.5
- High CVE-2020-36184 fixed in 2.9.10.8
- and 35 more
High 37 known vulnerabilities in tomcat-embed-core@8.0.30 (bahmni/atomfeed-console:latest)
How to fix
Update tomcat-embed-core from 8.0.30 to 8.5.49 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.5.49); if 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 8.5.49
- High CVE-2021-25329 fixed in 8.5.61
- High CVE-2022-23181 fixed in 8.5.75
- High CVE-2016-6816 fixed in 8.5.8,
- High CVE-2016-6796 fixed in 8.0.37
- High CVE-2016-6797 fixed in 8.0.37
- High CVE-2016-8745 fixed in 7.0.75,
- High CVE-2017-5647 fixed in 8.0.43
- High CVE-2017-5664 fixed in 8.0.44
- High CVE-2018-1336 fixed in 8.0.51
- High CVE-2018-8034 fixed in 8.0.53
- High CVE-2019-0199 fixed in 8.5.38
- High CVE-2019-17563 fixed in 8.5.50
- High CVE-2021-30639 fixed in 8.5.65
- High CVE-2026-24880 fixed in 9.0.116
- High CVE-2020-8022 fixed in 8.0.53,
- High CVE-2015-5346 fixed in 8.0.31
- High CVE-2017-12617 fixed in 8.0.47
- High CVE-2019-0232 fixed in 8.5.40
- High CVE-2015-5351 fixed in 8.0.31
- and 17 more
High 22 known vulnerabilities in python@2.7.18-1.amzn2.0.8 (bahmni/atomfeed-console:latest)
How to fix
Update python from 2.7.18-1.amzn2.0.8 to 2.7.18-1.amzn2.0.18 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.18-1.amzn2.0.18); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-13462 fixed in 2.7.18-1.amzn2.0.18
- High CVE-2025-8194 fixed in 2.7.18-1.amzn2.0.14
- High CVE-2026-3479 fixed in 2.7.18-1.amzn2.0.18
- High CVE-2026-4519 fixed in 2.7.18-1.amzn2.0.18
- Medium CVE-2007-4559 fixed in 2.7.18-1.amzn2.0.12
- Medium CVE-2023-27043 fixed in 2.7.18-1.amzn2.0.9
- Medium CVE-2023-40217 fixed in 2.7.18-1.amzn2.0.12
- Medium CVE-2024-0450 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-11168 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-5642 fixed in 2.7.18-1.amzn2.0.10
- Medium CVE-2024-6923 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-7592 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2025-0938 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2025-11468 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2025-12084 fixed in 2.7.18-1.amzn2.0.15
- Medium CVE-2025-15282 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2025-6069 fixed in 2.7.18-1.amzn2.0.13
- Medium CVE-2025-6075 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2026-0672 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2026-0865 fixed in 2.7.18-1.amzn2.0.16
- and 2 more
High 22 known vulnerabilities in python-libs@2.7.18-1.amzn2.0.8 (bahmni/atomfeed-console:latest)
How to fix
Update python-libs from 2.7.18-1.amzn2.0.8 to 2.7.18-1.amzn2.0.18 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.18-1.amzn2.0.18); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-13462 fixed in 2.7.18-1.amzn2.0.18
- High CVE-2025-8194 fixed in 2.7.18-1.amzn2.0.14
- High CVE-2026-3479 fixed in 2.7.18-1.amzn2.0.18
- High CVE-2026-4519 fixed in 2.7.18-1.amzn2.0.18
- Medium CVE-2007-4559 fixed in 2.7.18-1.amzn2.0.12
- Medium CVE-2023-27043 fixed in 2.7.18-1.amzn2.0.9
- Medium CVE-2023-40217 fixed in 2.7.18-1.amzn2.0.12
- Medium CVE-2024-0450 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-11168 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-5642 fixed in 2.7.18-1.amzn2.0.10
- Medium CVE-2024-6923 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2024-7592 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2025-0938 fixed in 2.7.18-1.amzn2.0.11
- Medium CVE-2025-11468 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2025-12084 fixed in 2.7.18-1.amzn2.0.15
- Medium CVE-2025-15282 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2025-6069 fixed in 2.7.18-1.amzn2.0.13
- Medium CVE-2025-6075 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2026-0672 fixed in 2.7.18-1.amzn2.0.16
- Medium CVE-2026-0865 fixed in 2.7.18-1.amzn2.0.16
- and 2 more
High 18 known vulnerabilities in spring-core@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-core from 4.2.4.RELEASE to 4.3.0.RELEASE or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.3.0.RELEASE); if 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-11272 fixed in 4.3.0.RELEASE
- High CVE-2016-5007 fixed in 4.3.1
- High CVE-2016-9878 fixed in 3.2.18,
- High CVE-2018-1272 fixed in 4.3.15
- High CVE-2018-15756 fixed in 4.3.20.RELEASE
- High CVE-2020-5421 fixed in 4.3.29.RELEASE,
- High CVE-2018-1270 fixed in 4.3.16
- High CVE-2018-1275 fixed in 4.3.16,
- High CVE-2022-22965 fixed in 5.2.20,
- Medium CVE-2024-38827 fixed in 6.1.14
- Medium CVE-2019-3795 fixed in 4.3.0.RELEASE,
- Medium CVE-2022-22968 fixed in 5.2.21,
- Medium CVE-2022-22970 fixed in 5.2.22.RELEASE,
- Medium CVE-2018-1271 fixed in 4.3.15
- Medium CVE-2018-1257 fixed in 4.3.17
- Medium CVE-2022-22971 fixed in 5.2.22.RELEASE,
- Medium CVE-2023-20861 fixed in 5.3.26,
- Medium CVE-2023-20863 fixed in 5.3.27,
High 16 known vulnerabilities in libxml2@2.9.1-6.amzn2.5.13 (bahmni/atomfeed-console:latest)
How to fix
Update libxml2 from 2.9.1-6.amzn2.5.13 to 2.9.1-6.amzn2.5.15 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.9.1-6.amzn2.5.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
- High CVE-2022-49043 fixed in 2.9.1-6.amzn2.5.15
- High CVE-2024-56171 fixed in 2.9.1-6.amzn2.5.16
- High CVE-2025-24928 fixed in 2.9.1-6.amzn2.5.16
- High CVE-2025-27113 fixed in 2.9.1-6.amzn2.5.16
- High CVE-2025-49794 fixed in 2.9.1-6.amzn2.5.19
- High CVE-2025-49796 fixed in 2.9.1-6.amzn2.5.19
- High CVE-2025-6021 fixed in 2.9.1-6.amzn2.5.18
- High CVE-2025-7425 fixed in 2.9.1-6.amzn2.5.20
- Medium CVE-2024-34459 fixed in 2.9.1-6.amzn2.5.14
- Medium CVE-2025-32414 fixed in 2.9.1-6.amzn2.5.17
- Medium CVE-2025-32415 fixed in 2.9.1-6.amzn2.5.17
- Medium CVE-2026-0990 fixed in 2.9.1-6.amzn2.5.22
- Medium CVE-2026-0992 fixed in 2.9.1-6.amzn2.5.22
- Low CVE-2025-8732 fixed in 2.9.1-6.amzn2.5.21
- Low CVE-2026-0989 fixed in 2.9.1-6.amzn2.5.23
- Low CVE-2026-1757 fixed in 2.9.1-6.amzn2.5.24
High 12 known vulnerabilities in mysql-connector-java@5.1.8 (bahmni/atomfeed-console:latest)
How to fix
Update mysql-connector-java from 5.1.8 to 8.2.0 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.2.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-22102 fixed in 8.2.0
- High CVE-2017-3523 fixed in 5.1.41
- High CVE-2018-3258 fixed in 8.0.13
- High CVE-2023-22102 fixed in no fix yet
- Medium CVE-2015-2575 fixed in 5.1.35
- Medium CVE-2020-2875 fixed in 5.1.49,
- Medium CVE-2020-2934 fixed in 5.1.49,
- Medium CVE-2019-2692 fixed in 8.0.16
- Medium CVE-2017-3586 fixed in 5.1.42
- Medium CVE-2022-21363 fixed in 8.0.28
- Low CVE-2020-2933 fixed in 5.1.49
- Low CVE-2017-3589 fixed in 5.1.42
High 12 known vulnerabilities in openssl@3.1.3-r0 (bash:5.2.15)
How to fix
Update openssl from 3.1.3-r0 to 3.1.4-r0 or later in bash:5.2.15. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.4-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-5363 fixed in 3.1.4-r0
- High CVE-2024-4741 fixed in 3.1.6-r0
- High CVE-2024-6119 fixed in 3.1.7-r0
- High CVE-2024-5535 fixed in 3.1.6-r0
- Medium CVE-2024-13176 fixed in 3.1.8-r0
- Medium CVE-2024-9143 fixed in 3.1.7-r1
- Medium CVE-2023-5678 fixed in 3.1.4-r1
- Medium CVE-2024-4603 fixed in 3.1.5-r0
- Medium CVE-2024-0727 fixed in 3.1.4-r5
- Medium CVE-2023-6237 fixed in 3.1.4-r4
- Medium CVE-2024-2511 fixed in 3.1.4-r6
- Medium CVE-2023-6129 fixed in 3.1.4-r3
High 11 known vulnerabilities in cryptography@3.2.1 (mysql:5.7)
How to fix
Update cryptography from 3.2.1 to 39.0.1 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 39.0.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-0286 fixed in 39.0.1
- High CVE-2026-26007 fixed in 46.0.5
- High CVE-2023-50782 fixed in 42.0.0
- High CVE-2020-36242 fixed in 3.3.2
- Medium CVE-2024-0727 fixed in 42.0.2
- Medium CVE-2023-49083 fixed in 41.0.6
- Medium CVE-2023-23931 fixed in 39.0.1
- Low GHSA-5cpq-8wj7-hf2v fixed in 41.0.0
- Low GHSA-jm77-qphf-c4w8 fixed in 41.0.3
- Low GHSA-v8gr-m533-ghj9 fixed in 41.0.4
- Low CVE-2026-34073 fixed in 46.0.6
High 10 known vulnerabilities in runc@1.0.1 (postgres:9.6)
How to fix
Update runc from 1.0.1 to 1.1.5 or later in postgres:9.6. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-27561 fixed in 1.1.5
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2022-29162 fixed in 1.1.2
- Medium CVE-2021-43784 fixed in 1.0.3
- Medium CVE-2023-28642 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 9 known vulnerabilities in runc@1.1.0 (mysql:5.7)
How to fix
Update runc from 1.1.0 to 1.1.5 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-27561 fixed in 1.1.5
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2022-29162 fixed in 1.1.2
- Medium CVE-2023-28642 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 8 known vulnerabilities in snakeyaml@1.16 (bahmni/atomfeed-console:latest)
How to fix
Update snakeyaml from 1.16 to 1.26 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26); if 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-2017-18640 fixed in 1.26
- High CVE-2022-25857 fixed in 1.31
- High CVE-2022-1471 fixed in 2.0
- Medium CVE-2022-38750 fixed in 1.31
- Medium CVE-2022-38749 fixed in 1.31
- Medium CVE-2022-38751 fixed in 1.31
- Medium CVE-2022-38752 fixed in 1.32
- Medium CVE-2022-41854 fixed in 1.32
High 8 known vulnerabilities in spring-web@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-web from 4.2.4.RELEASE to 4.3.20.RELEASE, or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.3.20.RELEASE,); if 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-2018-15756 fixed in 4.3.20.RELEASE,
- High CVE-2024-22243 fixed in no fix yet
- High CVE-2024-22259 fixed in 5.3.33
- High CVE-2024-22262 fixed in 5.3.34
- High CVE-2020-5421 fixed in 4.3.29.RELEASE,
- High CVE-2016-1000027 fixed in 6.0.0
- Medium CVE-2024-38809 fixed in 5.3.38
- Medium CVE-2024-38820 fixed in no fix yet
High 7 known vulnerabilities in glib2@2.56.1-9.amzn2.0.8 (bahmni/atomfeed-console:latest)
How to fix
Update glib2 from 2.56.1-9.amzn2.0.8 to 2.56.1-9.amzn2.0.9 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.56.1-9.amzn2.0.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-29499 fixed in 2.56.1-9.amzn2.0.9
- High CVE-2023-32611 fixed in 2.56.1-9.amzn2.0.9
- High CVE-2023-32636 fixed in 2.56.1-9.amzn2.0.9
- High CVE-2023-32643 fixed in 2.56.1-9.amzn2.0.9
- High CVE-2023-32665 fixed in 2.56.1-9.amzn2.0.9
- High CVE-2025-13601 fixed in 2.56.1-9.amzn2.0.12
- High CVE-2025-14087 fixed in 2.56.1-9.amzn2.0.13
High 7 known vulnerabilities in log4j@1.2.17 (bahmni/atomfeed-console:latest)
How to fix
No fixed version of log4j is available yet. Check whether bahmni/atomfeed-console:latest needs log4j at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2021-4104 fixed in no fix yet
- High CVE-2023-26464 fixed in 2.0
- High CVE-2022-23302 fixed in no fix yet
- High CVE-2019-17571 fixed in no fix yet
- High CVE-2022-23305 fixed in no fix yet
- High CVE-2022-23307 fixed in no fix yet
- Low CVE-2020-9488 fixed in 2.12.3,
High 7 known vulnerabilities in logback-core@1.1.3 (bahmni/atomfeed-console:latest)
How to fix
Update logback-core from 1.1.3 to 1.2.13 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.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-6378 fixed in 1.2.13
- High CVE-2017-5929 fixed in 1.2.0
- Medium CVE-2024-12798 fixed in 1.3.15
- Medium CVE-2025-11226 fixed in 1.5.19
- Medium CVE-2021-42550 fixed in 1.2.9
- Low CVE-2026-1225 fixed in 1.5.25
- Low CVE-2024-12801 fixed in 1.3.15
High 7 known vulnerabilities in spring-webmvc@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-webmvc from 4.2.4.RELEASE to 4.2.9 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.2.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2016-9878 fixed in 4.2.9
- High CVE-2018-1272 fixed in 5.0.5.RELEASE
- High CVE-2018-15756 fixed in 4.3.20.RELEASE,
- High CVE-2024-38819 fixed in no fix yet
- High CVE-2020-5421 fixed in 4.3.29.RELEASE,
- High CVE-2022-22965 fixed in 5.2.20.RELEASE
- Medium CVE-2018-1271 fixed in 4.3.15.RELEASE,
High 7 known vulnerabilities in libxml2@2.9.1-6.0.3.el7_9.6 (mysql:5.7)
How to fix
Update libxml2 from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.5.el7_9.6 or later in mysql:5.7. If the 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:2.9.1-6.0.5.el7_9.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
- High CVE-2024-56171 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-24928 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
- Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 7 known vulnerabilities in libxml2-python@2.9.1-6.0.3.el7_9.6 (mysql:5.7)
How to fix
Update libxml2-python from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.5.el7_9.6 or later in mysql:5.7. If the 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:2.9.1-6.0.5.el7_9.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
- High CVE-2024-56171 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-24928 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
- Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 6 known vulnerabilities in openssl@1%3A1.0.2k-24.amzn2.0.13 (bahmni/atomfeed-console:latest)
How to fix
Update openssl from 1%3A1.0.2k-24.amzn2.0.13 to 1.0.2k-24.amzn2.0.17 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.0.2k-24.amzn2.0.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-2025-68160 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2025-69420 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2025-69421 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2026-22796 fixed in 1.0.2k-24.amzn2.0.17
- Medium CVE-2024-13176 fixed in 1.0.2k-24.amzn2.0.15
- Medium CVE-2025-9230 fixed in 1.0.2k-24.amzn2.0.16
High 6 known vulnerabilities in openssl-libs@1%3A1.0.2k-24.amzn2.0.13 (bahmni/atomfeed-console:latest)
How to fix
Update openssl-libs from 1%3A1.0.2k-24.amzn2.0.13 to 1.0.2k-24.amzn2.0.17 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.0.2k-24.amzn2.0.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-2025-68160 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2025-69420 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2025-69421 fixed in 1.0.2k-24.amzn2.0.17
- High CVE-2026-22796 fixed in 1.0.2k-24.amzn2.0.17
- Medium CVE-2024-13176 fixed in 1.0.2k-24.amzn2.0.15
- Medium CVE-2025-9230 fixed in 1.0.2k-24.amzn2.0.16
High 5 known vulnerabilities in postgresql@9.4.1211.jre7 (bahmni/atomfeed-console:latest)
How to fix
Update postgresql from 9.4.1211.jre7 to 42.2.25 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 42.2.25); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-21724 fixed in 42.2.25
- High CVE-2022-31197 fixed in 42.2.26
- High CVE-2020-25694 fixed in 13.1
- High CVE-2020-25695 fixed in 13.1
- High CVE-2024-1597 fixed in 42.2.28
High 5 known vulnerabilities in spring-boot@1.3.2.RELEASE (bahmni/atomfeed-console:latest)
How to fix
No fixed version of spring-boot is available yet. Check whether bahmni/atomfeed-console:latest needs spring-boot at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2025-22235 fixed in no fix yet
- High CVE-2022-27772 fixed in 2.2.11.RELEASE
- High CVE-2017-8046 fixed in 1.5.9.RELEASE
- Medium CVE-2023-34055 fixed in 2.7.18,
- Medium CVE-2018-1196 fixed in 1.5.10.RELEASE
High 5 known vulnerabilities in spring-expression@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-expression from 4.2.4.RELEASE to 5.2.24.RELEASE or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.24.RELEASE); if 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-20863 fixed in 5.2.24.RELEASE
- Medium CVE-2024-38827 fixed in 6.1.14
- Medium CVE-2024-38808 fixed in 5.3.39
- Medium CVE-2022-22950 fixed in 5.2.20.RELEASE
- Medium CVE-2023-20861 fixed in 5.2.23.RELEASE
High 4 known vulnerabilities in hibernate-validator@5.2.2.Final (bahmni/atomfeed-console:latest)
How to fix
Update hibernate-validator from 5.2.2.Final to 5.2.5.Final or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.5.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-2017-7536 fixed in 5.2.5.Final
- Medium CVE-2020-10693 fixed in 6.0.20.Final
- Medium CVE-2023-1932 fixed in 6.2.0.Final
- Medium CVE-2025-35036 fixed in 6.2.0.CR1
High 4 known vulnerabilities in libpng@2%3A1.5.13-8.amzn2.0.5 (bahmni/atomfeed-console:latest)
How to fix
Update libpng from 2%3A1.5.13-8.amzn2.0.5 to 1.5.13-8.amzn2.0.8 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.5.13-8.amzn2.0.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-33416 fixed in 1.5.13-8.amzn2.0.8
- Medium CVE-2025-64505 fixed in 1.5.13-8.amzn2.0.6
- Medium CVE-2025-64720 fixed in 1.5.13-8.amzn2.0.6
- Medium CVE-2026-25646 fixed in 1.5.13-8.amzn2.0.7
High 4 known vulnerabilities in spring-context@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-context from 4.2.4.RELEASE to 5.2.21.RELEASE or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.21.RELEASE); if 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-22968 fixed in 5.2.21.RELEASE
- Medium CVE-2024-38827 fixed in 6.1.14
- Medium CVE-2024-38820 fixed in no fix yet
- Low CVE-2025-22233 fixed in no fix yet
High 4 known vulnerabilities in krb5-libs@1.15.1-55.0.1.el7_9 (mysql:5.7)
How to fix
Update krb5-libs from 1.15.1-55.0.1.el7_9 to 0:1.15.1-55.0.7.el7_9 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:1.15.1-55.0.7.el7_9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-3596 fixed in 0:1.15.1-55.0.7.el7_9
- Medium CVE-2024-37370 fixed in 0:1.15.1-55.0.3.el7_9
- Medium CVE-2024-37371 fixed in 0:1.15.1-55.0.3.el7_9
- Medium CVE-2025-24528 fixed in 0:1.15.1-55.0.9.el7_9
High 3 known vulnerabilities in c3p0@0.9.1.2 (bahmni/atomfeed-console:latest)
How to fix
Update c3p0 from 0.9.1.2 to 0.9.5.4 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.9.5.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2019-5427 fixed in 0.9.5.4
- High CVE-2026-27830 fixed in 0.12.0
- High CVE-2018-20433 fixed in 0.9.5.3
High 3 known vulnerabilities in expat@2.1.0-15.amzn2.0.3 (bahmni/atomfeed-console:latest)
How to fix
Update expat from 2.1.0-15.amzn2.0.3 to 2.1.0-15.amzn2.0.4 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.1.0-15.amzn2.0.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-45490 fixed in 2.1.0-15.amzn2.0.4
- Medium CVE-2024-50602 fixed in 2.1.0-15.amzn2.0.5
- Medium CVE-2026-25210 fixed in 2.1.0-15.amzn2.0.6
High 3 known vulnerabilities in jackson-core@2.6.5 (bahmni/atomfeed-console:latest)
How to fix
Update jackson-core from 2.6.5 to 2.15.0 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.15.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-52999 fixed in 2.15.0
- Medium CVE-2025-49128 fixed in 2.13.0
- Medium GHSA-72hv-8253-57qq fixed in 2.18.6
High 3 known vulnerabilities in plexus-utils@3.0.22 (bahmni/atomfeed-console:latest)
How to fix
Update plexus-utils from 3.0.22 to 4.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.0.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-67030 fixed in 4.0.3
- High CVE-2022-4244 fixed in 3.0.24
- Medium CVE-2022-4245 fixed in 3.0.24
High 3 known vulnerabilities in spring-beans@4.2.4.RELEASE (bahmni/atomfeed-console:latest)
How to fix
Update spring-beans from 4.2.4.RELEASE to 5.2.22.RELEASE or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.22.RELEASE); if 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-22970 fixed in 5.2.22.RELEASE
- High CVE-2022-22965 fixed in 5.2.20.RELEASE
- Medium CVE-2024-38827 fixed in 6.1.14
High 3 known vulnerabilities in setuptools@58.1.0 (mysql:5.7)
How to fix
Update setuptools from 58.1.0 to 70.0.0 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 70.0.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-2024-6345 fixed in 70.0.0
- High CVE-2025-47273 fixed in 78.1.1
- High CVE-2022-40897 fixed in 65.5.1
High 2 known vulnerabilities in commons-io@2.4 (bahmni/atomfeed-console:latest)
How to fix
Update commons-io from 2.4 to 2.14.0 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.14.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-2024-47554 fixed in 2.14.0
- Medium CVE-2021-29425 fixed in 2.7
High 2 known vulnerabilities in freetype@2.8-14.amzn2.1.2 (bahmni/atomfeed-console:latest)
How to fix
Update freetype from 2.8-14.amzn2.1.2 to 2.8-14.amzn2.1.4 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.8-14.amzn2.1.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-23022 fixed in 2.8-14.amzn2.1.4
- High CVE-2025-27363 fixed in 2.8-14.amzn2.1.4
High 2 known vulnerabilities in libtasn1@4.10-1.amzn2.0.6 (bahmni/atomfeed-console:latest)
How to fix
Update libtasn1 from 4.10-1.amzn2.0.6 to 4.10-1.amzn2.0.8 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.10-1.amzn2.0.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-13151 fixed in 4.10-1.amzn2.0.8
- Medium CVE-2024-12133 fixed in 4.10-1.amzn2.0.7
High 2 known vulnerabilities in logback-classic@1.1.3 (bahmni/atomfeed-console:latest)
How to fix
Update logback-classic from 1.1.3 to 1.2.13 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.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-6378 fixed in 1.2.13
- High CVE-2017-5929 fixed in 1.2.0
and 11 more groups with 12 findings
Medium 76
Medium 9 known vulnerabilities in curl@8.3.0-1.amzn2.0.7 (bahmni/atomfeed-console:latest)
How to fix
Update curl from 8.3.0-1.amzn2.0.7 to 8.3.0-1.amzn2.0.8 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.3.0-1.amzn2.0.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-9681 fixed in 8.3.0-1.amzn2.0.8
- Medium CVE-2025-10966 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-11563 fixed in 8.3.0-1.amzn2.0.11
- Medium CVE-2025-14017 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-14524 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-14819 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-15079 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-15224 fixed in 8.3.0-1.amzn2.0.12
- Low CVE-2025-9086 fixed in 8.3.0-1.amzn2.0.10
Medium 9 known vulnerabilities in libcurl@8.3.0-1.amzn2.0.7 (bahmni/atomfeed-console:latest)
How to fix
Update libcurl from 8.3.0-1.amzn2.0.7 to 8.3.0-1.amzn2.0.8 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.3.0-1.amzn2.0.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-9681 fixed in 8.3.0-1.amzn2.0.8
- Medium CVE-2025-10966 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-11563 fixed in 8.3.0-1.amzn2.0.11
- Medium CVE-2025-14017 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-14524 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-14819 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-15079 fixed in 8.3.0-1.amzn2.0.12
- Medium CVE-2025-15224 fixed in 8.3.0-1.amzn2.0.12
- Low CVE-2025-9086 fixed in 8.3.0-1.amzn2.0.10
Medium 5 known vulnerabilities in vim-data@2%3A9.0.2153-1.amzn2.0.1 (bahmni/atomfeed-console:latest)
How to fix
Update vim-data from 2%3A9.0.2153-1.amzn2.0.1 to 9.0.2153-1.amzn2.0.2 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.2153-1.amzn2.0.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-43802 fixed in 9.0.2153-1.amzn2.0.2
- Medium CVE-2025-1215 fixed in 9.0.2153-1.amzn2.0.4
- Medium CVE-2025-24014 fixed in 9.0.2153-1.amzn2.0.3
- Medium CVE-2025-26603 fixed in 9.0.2153-1.amzn2.0.4
- Medium CVE-2025-29768 fixed in 9.0.2153-1.amzn2.0.4
Medium 5 known vulnerabilities in vim-minimal@2%3A9.0.2153-1.amzn2.0.1 (bahmni/atomfeed-console:latest)
How to fix
Update vim-minimal from 2%3A9.0.2153-1.amzn2.0.1 to 9.0.2153-1.amzn2.0.2 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.2153-1.amzn2.0.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-43802 fixed in 9.0.2153-1.amzn2.0.2
- Medium CVE-2025-1215 fixed in 9.0.2153-1.amzn2.0.4
- Medium CVE-2025-24014 fixed in 9.0.2153-1.amzn2.0.3
- Medium CVE-2025-26603 fixed in 9.0.2153-1.amzn2.0.4
- Medium CVE-2025-29768 fixed in 9.0.2153-1.amzn2.0.4
Medium 4 known vulnerabilities in busybox@1.36.1-r2 (bash:5.2.15)
How to fix
Update busybox from 1.36.1-r2 to 1.36.1-r7 or later in bash:5.2.15. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.36.1-r7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-42363 fixed in 1.36.1-r7
- Medium CVE-2023-42364 fixed in 1.36.1-r7
- Medium CVE-2023-42365 fixed in 1.36.1-r7
- Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium 3 known vulnerabilities in glibc@2.26-64.amzn2.0.2 (bahmni/atomfeed-console:latest)
How to fix
Update glibc from 2.26-64.amzn2.0.2 to 2.26-64.amzn2.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.26-64.amzn2.0.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-2024-33600 fixed in 2.26-64.amzn2.0.3
- Medium CVE-2025-0395 fixed in 2.26-64.amzn2.0.4
- Medium CVE-2025-8058 fixed in 2.26-64.amzn2.0.5
Medium 3 known vulnerabilities in glibc-common@2.26-64.amzn2.0.2 (bahmni/atomfeed-console:latest)
How to fix
Update glibc-common from 2.26-64.amzn2.0.2 to 2.26-64.amzn2.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.26-64.amzn2.0.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-2024-33600 fixed in 2.26-64.amzn2.0.3
- Medium CVE-2025-0395 fixed in 2.26-64.amzn2.0.4
- Medium CVE-2025-8058 fixed in 2.26-64.amzn2.0.5
Medium 3 known vulnerabilities in glibc-langpack-en@2.26-64.amzn2.0.2 (bahmni/atomfeed-console:latest)
How to fix
Update glibc-langpack-en from 2.26-64.amzn2.0.2 to 2.26-64.amzn2.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.26-64.amzn2.0.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-2024-33600 fixed in 2.26-64.amzn2.0.3
- Medium CVE-2025-0395 fixed in 2.26-64.amzn2.0.4
- Medium CVE-2025-8058 fixed in 2.26-64.amzn2.0.5
Medium 3 known vulnerabilities in glibc-minimal-langpack@2.26-64.amzn2.0.2 (bahmni/atomfeed-console:latest)
How to fix
Update glibc-minimal-langpack from 2.26-64.amzn2.0.2 to 2.26-64.amzn2.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.26-64.amzn2.0.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-2024-33600 fixed in 2.26-64.amzn2.0.3
- Medium CVE-2025-0395 fixed in 2.26-64.amzn2.0.4
- Medium CVE-2025-8058 fixed in 2.26-64.amzn2.0.5
Medium 3 known vulnerabilities in guava@18.0 (bahmni/atomfeed-console:latest)
How to fix
Update guava from 18.0 to 32.0.0-android or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 32.0.0-android); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-2976 fixed in 32.0.0-android
- Medium CVE-2018-10237 fixed in 24.1.1-android
- Low CVE-2020-8908 fixed in 32.0.0-android
Medium 3 known vulnerabilities in libcrypt@2.26-64.amzn2.0.2 (bahmni/atomfeed-console:latest)
How to fix
Update libcrypt from 2.26-64.amzn2.0.2 to 2.26-64.amzn2.0.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.26-64.amzn2.0.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-2024-33600 fixed in 2.26-64.amzn2.0.3
- Medium CVE-2025-0395 fixed in 2.26-64.amzn2.0.4
- Medium CVE-2025-8058 fixed in 2.26-64.amzn2.0.5
Medium 3 known vulnerabilities in pip@23.0.1 (mysql:5.7)
How to fix
Update pip from 23.0.1 to 25.3 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 25.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-8869 fixed in 25.3
- Medium CVE-2023-5752 fixed in 23.3
- Low CVE-2026-1703 fixed in 26.0
Medium 3 known vulnerabilities in python@2.7.5-94.0.1.el7_9 (mysql:5.7)
How to fix
Update python from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.3.el7_9 or later in mysql:5.7. If the 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:2.7.5-94.0.3.el7_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-12084 fixed in 0:2.7.5-94.0.3.el7_9
- Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
- Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
Medium 3 known vulnerabilities in python-libs@2.7.5-94.0.1.el7_9 (mysql:5.7)
How to fix
Update python-libs from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.3.el7_9 or later in mysql:5.7. If the 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:2.7.5-94.0.3.el7_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-12084 fixed in 0:2.7.5-94.0.3.el7_9
- Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
- Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
Medium 2 known vulnerabilities in krb5-libs@1.15.1-55.amzn2.2.8 (bahmni/atomfeed-console:latest)
How to fix
Update krb5-libs from 1.15.1-55.amzn2.2.8 to 1.15.1-55.amzn2.2.9 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.15.1-55.amzn2.2.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.15.1-55.amzn2.2.9
- Medium CVE-2025-3576 fixed in 1.15.1-55.amzn2.2.9
Medium 1 known vulnerability in busybox@1.37.0-r30 (alpine)
How to fix
No fixed version of busybox is available yet. Check whether alpine needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2025-60876 fixed in no fix yet
Medium 1 known vulnerability in commons-lang3@3.4 (bahmni/atomfeed-console:latest)
How to fix
Update commons-lang3 from 3.4 to 3.18.0 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-48924 fixed in 3.18.0
Medium 1 known vulnerability in sqlite@3.7.17-8.amzn2.1.2 (bahmni/atomfeed-console:latest)
How to fix
Update sqlite from 3.7.17-8.amzn2.1.2 to 3.7.17-8.amzn2.1.3 or later in bahmni/atomfeed-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.7.17-8.amzn2.1.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-6965 fixed in 3.7.17-8.amzn2.1.3
Medium 1 known vulnerability in zlib@1.2.13-r1 (bash:5.2.15)
How to fix
No fixed version of zlib is available yet. Check whether bash:5.2.15 needs zlib 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-6992 fixed in no fix yet
Medium 1 known vulnerability in e2fsprogs@1.42.9-19.0.1.el7 (mysql:5.7)
How to fix
Update e2fsprogs from 1.42.9-19.0.1.el7 to 0:1.45.4-3.0.7.el7 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:1.45.4-3.0.7.el7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-1304 fixed in 0:1.45.4-3.0.7.el7
Medium 1 known vulnerability in gcc@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update gcc from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. If the 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:4.8.5-45.0.1.el7_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-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in glib2@2.56.1-9.el7_9 (mysql:5.7)
How to fix
Update glib2 from 2.56.1-9.el7_9 to 0:2.56.1-9.0.3.el7_9 or later in mysql:5.7. If the 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:2.56.1-9.0.3.el7_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-13601 fixed in 0:2.56.1-9.0.3.el7_9
Medium 1 known vulnerability in libcom_err@1.42.9-19.0.1.el7 (mysql:5.7)
How to fix
Update libcom_err from 1.42.9-19.0.1.el7 to 0:1.45.4-3.0.7.el7 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:1.45.4-3.0.7.el7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-1304 fixed in 0:1.45.4-3.0.7.el7
Medium 1 known vulnerability in libgcc@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update libgcc from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. If the 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:4.8.5-45.0.1.el7_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-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in libstdc%2B%2B@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update libstdc%2B%2B from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. If the 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:4.8.5-45.0.1.el7_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-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in openssl@1%3A1.0.2k-26.el7_9 (mysql:5.7)
How to fix
Update openssl from 1%3A1.0.2k-26.el7_9 to 1:1.0.2k-26.0.1.el7_9 or later in mysql:5.7. If the 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.0.2k-26.0.1.el7_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-9230 fixed in 1:1.0.2k-26.0.1.el7_9
Medium 1 known vulnerability in openssl-libs@1%3A1.0.2k-26.el7_9 (mysql:5.7)
How to fix
Update openssl-libs from 1%3A1.0.2k-26.el7_9 to 1:1.0.2k-26.0.1.el7_9 or later in mysql:5.7. If the 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.0.2k-26.0.1.el7_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-9230 fixed in 1:1.0.2k-26.0.1.el7_9
Medium 1 known vulnerability in paramiko@2.11.0 (mysql:5.7)
How to fix
Update paramiko from 2.11.0 to 3.4.0 or later in mysql:5.7. If the 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.4.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-48795 fixed in 3.4.0
Medium 1 known vulnerability in pynacl@1.4.0 (mysql:5.7)
How to fix
Update pynacl from 1.4.0 to 1.6.2 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.6.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-69277 fixed in 1.6.2
Medium 1 known vulnerability in sys@0.0.0-20210817142637-7d9622a276b7 (postgres:9.6)
How to fix
Update sys from 0.0.0-20210817142637-7d9622a276b7 to 0.0.0-20220412211240-33da011f77ad or later in postgres:9.6. If the 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.0.0-20220412211240-33da011f77ad); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-29526 fixed in 0.0.0-20220412211240-33da011f77ad
Low 2
Low 1 known vulnerability in certifi@2023.7.22 (mysql:5.7)
How to fix
Update certifi from 2023.7.22 to 2024.7.4 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2024.7.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-2024-39689 fixed in 2024.7.4
Low 1 known vulnerability in pyopenssl@20.0.1 (mysql:5.7)
How to fix
Update pyopenssl from 20.0.1 to 26.0.0 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 26.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-27448 fixed in 26.0.0
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 23 Apr 2026; it may have changed since.
Scan your own repository
InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.