InfraScan Cloud

Repository scan

openlmis-ref-distro

OpenLMIS/openlmis-ref-distro · branch master · scanned 21 May 2026

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

High 1,730

High 109 known vulnerabilities in stdlib@1.16.7 (openlmis/postgres:12-debezium) Security · 109 CVEs

How to fix

Update stdlib from 1.16.7 to 1.19.9 or later in openlmis/postgres:12-debezium. If the 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 89 more
High 77 known vulnerabilities in tiff@4.2.0-1 (openlmis/postgres:12-debezium) Security · 77 CVEs

How to fix

Update tiff from 4.2.0-1 to 4.2.0-1+deb11u6 or later in openlmis/postgres:12-debezium. If the 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.0-1+deb11u6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-52356 fixed in 4.2.0-1+deb11u6
  • High CVE-2024-7006 fixed in 4.2.0-1+deb11u6
  • High CVE-2022-0908 fixed in 4.2.0-1+deb11u1
  • High CVE-2022-3570 fixed in 4.2.0-1+deb11u3
  • High CVE-2026-4775 fixed in 4.2.0-1+deb11u8
  • High CVE-2023-25434 fixed in 4.2.0-1+deb11u4
  • High CVE-2025-9900 fixed in 4.2.0-1+deb11u7
  • Medium CVE-2022-0561 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-0562 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-0865 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-0907 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-0909 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-0924 fixed in 4.2.0-1+deb11u1
  • Medium CVE-2022-1354 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-1622 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-1623 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-2056 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-2057 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-2058 fixed in 4.2.0-1+deb11u3
  • Medium CVE-2022-22844 fixed in 4.2.0-1+deb11u1
  • and 57 more
High 61 known vulnerabilities in jackson-databind@2.9.6 (openlmis/dev:5.1) Security · 61 CVEs

How to fix

Update jackson-databind from 2.9.6 to 2.9.10 or later in openlmis/dev:5.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.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 41 more
High 60 known vulnerabilities in mariadb-10.5@1%3A10.5.12-0%2Bdeb11u1 (openlmis/postgres:12-debezium) Security · 60 CVEs

How to fix

Update mariadb-10.5 from 1%3A10.5.12-0%2Bdeb11u1 to 1:10.5.18-0+deb11u1 or later in openlmis/postgres:12-debezium. If the 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:10.5.18-0+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-46669 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27376 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27377 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27378 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27379 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27380 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27381 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27382 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27383 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27384 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27385 fixed in 1:10.5.13-0+deb11u1
  • High CVE-2022-27386 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27387 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27444 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27445 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27446 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27447 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27448 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27449 fixed in 1:10.5.18-0+deb11u1
  • High CVE-2022-27451 fixed in 1:10.5.18-0+deb11u1
  • and 40 more
High 58 known vulnerabilities in jackson-databind@2.8.5 (openlmis/bmp) Security · 58 CVEs

How to fix

Update jackson-databind from 2.8.5 to 2.8.11.2 or later in openlmis/bmp. If the 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.11.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2018-12022 fixed in 2.8.11.2
  • High CVE-2018-12023 fixed in 2.8.11.2
  • High CVE-2019-12086 fixed in 2.8.11.4
  • High CVE-2019-14439 fixed in 2.8.11.4
  • High CVE-2019-14892 fixed in 2.8.11.5
  • 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-2018-5968 fixed in 2.8.11.1
  • 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.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
  • High CVE-2020-36180 fixed in 2.9.10.8
  • High CVE-2020-36181 fixed in 2.9.10.8
  • High CVE-2020-36182 fixed in 2.9.10.8
  • High CVE-2020-36183 fixed in 2.9.10.8
  • and 38 more
High 57 known vulnerabilities in libde265@1.0.8-1 (openlmis/postgres:12-debezium) Security · 57 CVEs

How to fix

Update libde265 from 1.0.8-1 to 1.0.11-0+deb11u1 or later in openlmis/postgres:12-debezium. If the 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.11-0+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-36409 fixed in 1.0.11-0+deb11u1
  • High CVE-2022-47655 fixed in 1.0.11-0+deb11u1
  • High CVE-2022-47664 fixed in 1.0.11-0+deb11u1
  • High CVE-2022-47665 fixed in 1.0.11-0+deb11u1
  • High CVE-2023-25221 fixed in 1.0.11-0+deb11u1
  • High CVE-2023-43887 fixed in 1.0.11-0+deb11u2
  • High CVE-2026-33164 fixed in 1.0.11-0+deb11u4
  • High CVE-2020-21598 fixed in 1.0.11-0+deb11u1
  • High CVE-2023-27103 fixed in 1.0.11-0+deb11u2
  • High CVE-2023-49465 fixed in 1.0.11-0+deb11u3
  • High CVE-2023-49467 fixed in 1.0.11-0+deb11u3
  • High CVE-2023-49468 fixed in 1.0.11-0+deb11u3
  • High CVE-2022-1253 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2021-36408 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2021-36410 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2021-36411 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2023-24752 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2023-24754 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2023-24755 fixed in 1.0.11-0+deb11u1
  • Medium CVE-2023-24756 fixed in 1.0.11-0+deb11u1
  • and 37 more
High 47 known vulnerabilities in python3.9@3.9.2-1 (openlmis/postgres:12-debezium) Security · 47 CVEs

How to fix

Update python3.9 from 3.9.2-1 to 3.9.2-1+deb11u7 or later in openlmis/postgres:12-debezium. If the 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.9.2-1+deb11u7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-4519 fixed in 3.9.2-1+deb11u7
  • High CVE-2020-10735 fixed in 3.9.2-1+deb11u2
  • High CVE-2021-3737 fixed in 3.9.2-1+deb11u2
  • High CVE-2022-0391 fixed in 3.9.2-1+deb11u3
  • High CVE-2022-45061 fixed in 3.9.2-1+deb11u2
  • High CVE-2023-24329 fixed in 3.9.2-1+deb11u2
  • High CVE-2024-6232 fixed in 3.9.2-1+deb11u2
  • High CVE-2024-7592 fixed in 3.9.2-1+deb11u2
  • High CVE-2025-8194 fixed in 3.9.2-1+deb11u4
  • High CVE-2015-20107 fixed in 3.9.2-1+deb11u2
  • Medium CVE-2025-6069 fixed in 3.9.2-1+deb11u4
  • Medium CVE-2025-8291 fixed in 3.9.2-1+deb11u4
  • Medium CVE-2021-4189 fixed in 3.9.2-1+deb11u2
  • Medium CVE-2023-27043 fixed in 3.9.2-1+deb11u2
  • Medium CVE-2023-40217 fixed in 3.9.2-1+deb11u2
  • Medium CVE-2024-6923 fixed in 3.9.2-1+deb11u2
  • Medium CVE-2026-0865 fixed in 3.9.2-1+deb11u5
  • Medium CVE-2026-0672 fixed in 3.9.2-1+deb11u7
  • Medium CVE-2026-1299 fixed in 3.9.2-1+deb11u5
  • Medium CVE-2026-3644 fixed in 3.9.2-1+deb11u7
  • and 27 more
High 41 known vulnerabilities in curl@7.74.0-1.3 (openlmis/postgres:12-debezium) Security · 41 CVEs

How to fix

Update curl from 7.74.0-1.3 to 7.74.0-1.3+deb11u2 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.74.0-1.3+deb11u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-22946 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-27775 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-27781 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-27782 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-22576 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2024-2398 fixed in 7.74.0-1.3+deb11u12
  • High CVE-2023-27533 fixed in 7.74.0-1.3+deb11u8
  • High CVE-2023-27534 fixed in 7.74.0-1.3+deb11u8
  • High CVE-2021-22945 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-32207 fixed in 7.74.0-1.3+deb11u2
  • High CVE-2022-32221 fixed in 7.74.0-1.3+deb11u5
  • High CVE-2023-38545 fixed in 7.74.0-1.3+deb11u10
  • Medium CVE-2023-23916 fixed in 7.74.0-1.3+deb11u7
  • Medium CVE-2022-32205 fixed in 7.74.0-1.3+deb11u2
  • Medium CVE-2023-27538 fixed in 7.74.0-1.3+deb11u8
  • Medium CVE-2022-27774 fixed in 7.74.0-1.3+deb11u2
  • Medium CVE-2021-22947 fixed in 7.74.0-1.3+deb11u2
  • Medium CVE-2022-32208 fixed in 7.74.0-1.3+deb11u2
  • Medium CVE-2022-43552 fixed in 7.74.0-1.3+deb11u5
  • Medium CVE-2023-27535 fixed in 7.74.0-1.3+deb11u8
  • and 21 more
High 38 known vulnerabilities in xstream@1.3.1 (openlmis/bmp) Security · 38 CVEs

How to fix

Update xstream from 1.3.1 to 1.4.9 or later in openlmis/bmp. If the 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.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-3674 fixed in 1.4.9
  • High CVE-2017-7957 fixed in 1.4.10
  • High CVE-2021-21341 fixed in 1.4.16
  • High CVE-2021-29505 fixed in 1.4.17
  • High CVE-2021-43859 fixed in 1.4.19
  • High CVE-2022-40151 fixed in 1.4.20
  • High CVE-2024-47072 fixed in 1.4.21
  • High CVE-2020-26217 fixed in 1.4.14-jdk7
  • High CVE-2022-41966 fixed in 1.4.20
  • High CVE-2021-39139 fixed in 1.4.18
  • High CVE-2021-39141 fixed in 1.4.18
  • High CVE-2021-39144 fixed in 1.4.18
  • High CVE-2021-39145 fixed in 1.4.18
  • High CVE-2021-39146 fixed in 1.4.18
  • High CVE-2021-39147 fixed in 1.4.18
  • High CVE-2021-39148 fixed in 1.4.18
  • High CVE-2021-39149 fixed in 1.4.18
  • High CVE-2021-39150 fixed in 1.4.18
  • High CVE-2021-39151 fixed in 1.4.18
  • High CVE-2021-39152 fixed in 1.4.18
  • and 18 more
High 35 known vulnerabilities in openssl@1.1.1k-1%2Bdeb11u1 (openlmis/postgres:12-debezium) Security · 35 CVEs

How to fix

Update openssl from 1.1.1k-1%2Bdeb11u1 to 1.1.1n-0+deb11u4 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.1n-0+deb11u4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-0286 fixed in 1.1.1n-0+deb11u4
  • High CVE-2022-1292 fixed in 1.1.1n-0+deb11u2
  • High CVE-2022-2068 fixed in 1.1.1n-0+deb11u3
  • High CVE-2025-69419 fixed in 1.1.1w-0+deb11u5
  • High CVE-2022-0778 fixed in 1.1.1k-1+deb11u2
  • High CVE-2023-0464 fixed in 1.1.1n-0+deb11u5
  • High CVE-2024-4741 fixed in 1.1.1w-0+deb11u2
  • High CVE-2025-69420 fixed in 1.1.1w-0+deb11u5
  • High CVE-2025-69421 fixed in 1.1.1w-0+deb11u5
  • High CVE-2025-9230 fixed in 1.1.1w-0+deb11u4
  • High CVE-2026-28388 fixed in no fix yet
  • High CVE-2026-28389 fixed in no fix yet
  • High CVE-2026-28390 fixed in no fix yet
  • High CVE-2026-28387 fixed in no fix yet
  • High CVE-2024-5535 fixed in 1.1.1w-0+deb11u2
  • Medium CVE-2022-4304 fixed in 1.1.1n-0+deb11u4
  • Medium CVE-2022-4450 fixed in 1.1.1n-0+deb11u4
  • Medium CVE-2023-0215 fixed in 1.1.1n-0+deb11u4
  • Medium CVE-2025-69418 fixed in 1.1.1w-0+deb11u5
  • Medium CVE-2024-13176 fixed in 1.1.1w-0+deb11u3
  • and 15 more
High 32 known vulnerabilities in openssl@3.0.9-1 (driesva/proftpd) Security · 32 CVEs

How to fix

Update openssl from 3.0.9-1 to 3.0.18-1~deb12u2 or later in driesva/proftpd. If the 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.18-1~deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-69419 fixed in 3.0.18-1~deb12u2
  • High CVE-2024-4741 fixed in 3.0.14-1~deb12u1
  • High CVE-2025-69420 fixed in 3.0.18-1~deb12u2
  • High CVE-2025-69421 fixed in 3.0.18-1~deb12u2
  • High CVE-2025-9230 fixed in 3.0.17-1~deb12u3
  • High CVE-2026-28388 fixed in 3.0.19-1~deb12u2
  • High CVE-2026-28389 fixed in 3.0.19-1~deb12u2
  • High CVE-2026-28390 fixed in 3.0.19-1~deb12u2
  • High CVE-2026-28387 fixed in 3.0.19-1~deb12u2
  • High CVE-2024-5535 fixed in 3.0.15-1~deb12u1
  • Medium CVE-2025-69418 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2024-13176 fixed in 3.0.16-1~deb12u1
  • Medium CVE-2024-9143 fixed in 3.0.15-1~deb12u1
  • Medium CVE-2025-68160 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2023-3446 fixed in 3.0.10-1~deb12u1
  • Medium CVE-2023-3817 fixed in 3.0.10-1~deb12u1
  • Medium CVE-2023-5678 fixed in 3.0.13-1~deb12u1
  • Medium CVE-2026-22796 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2024-0727 fixed in 3.0.13-1~deb12u1
  • Medium CVE-2026-22795 fixed in 3.0.18-1~deb12u2
  • and 12 more
High 27 known vulnerabilities in glibc@2.36-9%2Bdeb12u1 (driesva/proftpd) Security · 27 CVEs

How to fix

Update glibc from 2.36-9%2Bdeb12u1 to 2.36-9+deb12u6 or later in driesva/proftpd. If the 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.36-9+deb12u6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-2961 fixed in 2.36-9+deb12u6
  • High CVE-2024-33601 fixed in 2.36-9+deb12u7
  • High CVE-2024-33602 fixed in 2.36-9+deb12u7
  • High CVE-2025-15281 fixed in 2.36-9+deb12u14
  • High CVE-2026-0915 fixed in 2.36-9+deb12u14
  • High CVE-2026-4046 fixed in 2.36-9+deb12u14
  • High CVE-2026-4437 fixed in 2.36-9+deb12u14
  • High CVE-2023-4911 fixed in 2.36-9+deb12u3
  • High CVE-2025-4802 fixed in 2.36-9+deb12u11
  • High CVE-2024-33599 fixed in 2.36-9+deb12u7
  • High CVE-2026-0861 fixed in 2.36-9+deb12u14
  • Medium CVE-2026-4438 fixed in 2.36-9+deb12u14
  • Medium CVE-2023-4806 fixed in 2.36-9+deb12u3
  • Medium CVE-2024-33600 fixed in 2.36-9+deb12u7
  • Medium CVE-2025-8058 fixed in 2.36-9+deb12u13
  • Medium CVE-2025-0395 fixed in 2.36-9+deb12u10
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • and 7 more
High 26 known vulnerabilities in tar@2.2.1 (openlmis/dev:5.1) Security · 26 CVEs

How to fix

Update tar from 2.2.1 to 7.5.8 or later in openlmis/dev:5.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.5.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-26960 fixed in 7.5.8
  • High CVE-2026-26960 fixed in 7.5.8
  • High CVE-2018-20834 fixed in 2.2.2
  • High CVE-2018-20834 fixed in 4.4.2
  • High CVE-2021-32803 fixed in 3.2.3,
  • High CVE-2021-32803 fixed in 4.4.15
  • High CVE-2021-32804 fixed in 3.2.2
  • High CVE-2021-32804 fixed in 4.4.14
  • High CVE-2021-37701 fixed in 4.4.16
  • High CVE-2021-37712 fixed in 4.4.18
  • High CVE-2021-37713 fixed in 4.4.18
  • High CVE-2021-37713 fixed in 4.4.18
  • High CVE-2026-23745 fixed in 7.5.3
  • High CVE-2026-23745 fixed in 7.5.3
  • High CVE-2026-24842 fixed in 7.5.7
  • High CVE-2026-24842 fixed in 7.5.7
  • High CVE-2026-29786 fixed in 7.5.10
  • High CVE-2026-29786 fixed in 7.5.10
  • High CVE-2026-31802 fixed in 7.5.11
  • High CVE-2026-31802 fixed in 7.5.11
  • and 6 more
High 26 known vulnerabilities in expat@2.2.10-2 (openlmis/postgres:12-debezium) Security · 26 CVEs

How to fix

Update expat from 2.2.10-2 to 2.2.10-2+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.2.10-2+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-23990 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-25314 fixed in 2.2.10-2+deb11u2
  • High CVE-2022-43680 fixed in 2.2.10-2+deb11u5
  • High CVE-2023-52425 fixed in 2.2.10-2+deb11u6
  • High CVE-2024-45490 fixed in 2.2.10-2+deb11u6
  • High CVE-2021-46143 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-40674 fixed in 2.2.10-2+deb11u4
  • High CVE-2021-45960 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22825 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22826 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22827 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22822 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22823 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-22824 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-23852 fixed in 2.2.10-2+deb11u1
  • High CVE-2022-25235 fixed in 2.2.10-2+deb11u2
  • High CVE-2022-25236 fixed in 2.2.10-2+deb11u2
  • High CVE-2022-25315 fixed in 2.2.10-2+deb11u2
  • High CVE-2024-45491 fixed in 2.2.10-2+deb11u6
  • High CVE-2024-45492 fixed in 2.2.10-2+deb11u6
  • and 6 more
High 26 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7 (openlmis/postgres:12-debezium) Security · 26 CVEs

How to fix

Update libxml2 from 2.9.10%2Bdfsg-6.7 to 2.9.10+dfsg-6.7+deb11u5 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.9.10+dfsg-6.7+deb11u5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
  • High CVE-2022-23308 fixed in 2.9.10+dfsg-6.7+deb11u1
  • High CVE-2022-40303 fixed in 2.9.10+dfsg-6.7+deb11u3
  • High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
  • High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
  • High CVE-2022-40304 fixed in 2.9.10+dfsg-6.7+deb11u3
  • High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
  • High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
  • High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
  • High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
  • High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
  • Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
  • Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
  • Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
  • Medium CVE-2022-29824 fixed in 2.9.10+dfsg-6.7+deb11u2
  • Medium CVE-2023-28484 fixed in 2.9.10+dfsg-6.7+deb11u4
  • Medium CVE-2023-29469 fixed in 2.9.10+dfsg-6.7+deb11u4
  • Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
  • Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
  • Medium CVE-2026-6732 fixed in no fix yet
  • and 6 more
High 25 known vulnerabilities in aa_ER@saaho (openlmis/postgres:12-debezium) Security · 25 CVEs

How to fix

Update aa_ER from saaho to 2.31-13+deb11u9 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.31-13+deb11u9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-2961 fixed in 2.31-13+deb11u9
  • High CVE-2024-33601 fixed in 2.31-13+deb11u10
  • High CVE-2026-5435 fixed in no fix yet
  • High CVE-2024-33602 fixed in 2.31-13+deb11u10
  • High CVE-2026-4046 fixed in no fix yet
  • High CVE-2026-5928 fixed in no fix yet
  • High CVE-2021-3999 fixed in 2.31-13+deb11u4
  • High CVE-2023-4911 fixed in 2.31-13+deb11u7
  • High CVE-2025-4802 fixed in 2.31-13+deb11u13
  • High CVE-2024-33599 fixed in 2.31-13+deb11u10
  • High CVE-2021-33574 fixed in 2.31-13+deb11u3
  • High CVE-2022-23218 fixed in 2.31-13+deb11u3
  • High CVE-2022-23219 fixed in 2.31-13+deb11u3
  • High CVE-2026-5450 fixed in no fix yet
  • Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
  • Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
  • Medium CVE-2026-6238 fixed in no fix yet
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • and 5 more
High 24 known vulnerabilities in aa_ER@saaho (openlmis/bmp) Security · 24 CVEs

How to fix

Update aa_ER from saaho to 2.23-0ubuntu10 or later in openlmis/bmp. If the 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.23-0ubuntu10); if 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-1000001 fixed in 2.23-0ubuntu10
  • Medium CVE-2020-1751 fixed in 2.23-0ubuntu11.2
  • Medium CVE-2017-1000366 fixed in 2.23-0ubuntu9
  • Medium CVE-2018-11237 fixed in 2.23-0ubuntu11.2
  • Medium CVE-2017-18269 fixed in 2.23-0ubuntu11.2
  • Medium CVE-2018-11236 fixed in 2.23-0ubuntu11.2
  • Medium CVE-2018-6485 fixed in 2.23-0ubuntu11.2
  • Low CVE-2019-19126 fixed in 2.23-0ubuntu11.2
  • Low CVE-2020-10029 fixed in 2.23-0ubuntu11.2
  • Low CVE-2016-4429 fixed in 2.23-0ubuntu6
  • Low CVE-2017-12133 fixed in 2.23-0ubuntu11.2
  • Low CVE-2017-1000409 fixed in 2.23-0ubuntu10
  • Low CVE-2020-1752 fixed in 2.23-0ubuntu11.2
  • Low CVE-2009-5155 fixed in 2.23-0ubuntu11.3
  • Low CVE-2016-1234 fixed in 2.23-0ubuntu6
  • Low CVE-2016-3706 fixed in 2.23-0ubuntu6
  • Low CVE-2016-5417 fixed in 2.23-0ubuntu6
  • Low CVE-2016-6323 fixed in 2.23-0ubuntu6
  • Low CVE-2017-1000408 fixed in 2.23-0ubuntu10
  • Low CVE-2017-16997 fixed in 2.23-0ubuntu10
  • and 4 more
High 22 known vulnerabilities in openssl@1.0.2g-1ubuntu4.5 (openlmis/bmp) Security · 22 CVEs

How to fix

Update openssl from 1.0.2g-1ubuntu4.5 to 1.0.2g-1ubuntu4.18 or later in openlmis/bmp. If the 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.2g-1ubuntu4.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-2020-1971 fixed in 1.0.2g-1ubuntu4.18
  • Medium CVE-2017-3732 fixed in 1.0.2g-1ubuntu4.6
  • Medium CVE-2017-3737 fixed in 1.0.2g-1ubuntu4.10
  • Medium CVE-2019-1559 fixed in 1.0.2g-1ubuntu4.15
  • Medium CVE-2021-23841 fixed in 1.0.2g-1ubuntu4.19
  • Medium CVE-2017-3736 fixed in 1.0.2g-1ubuntu4.9
  • Medium CVE-2018-0739 fixed in 1.0.2g-1ubuntu4.11
  • Medium CVE-2017-3731 fixed in 1.0.2g-1ubuntu4.6
  • Low CVE-2019-1563 fixed in 1.0.2g-1ubuntu4.16
  • Low CVE-2020-1968 fixed in 1.0.2g-1ubuntu4.17
  • Low CVE-2018-0495 fixed in 1.0.2g-1ubuntu4.13
  • Low CVE-2018-5407 fixed in 1.0.2g-1ubuntu4.14
  • Low CVE-2019-1547 fixed in 1.0.2g-1ubuntu4.16
  • Low CVE-2017-3735 fixed in 1.0.2g-1ubuntu4.9
  • Low CVE-2019-1551 fixed in 1.0.2g-1ubuntu4.16
  • Low CVE-2016-7055 fixed in 1.0.2g-1ubuntu4.6
  • Low CVE-2017-3738 fixed in 1.0.2g-1ubuntu4.10
  • Low CVE-2018-0734 fixed in 1.0.2g-1ubuntu4.14
  • Low CVE-2018-0737 fixed in 1.0.2g-1ubuntu4.13
  • Low CVE-2016-8610 fixed in 1.0.2g-1ubuntu4.6
  • and 2 more
High 21 known vulnerabilities in gnutls28@3.7.1-5 (openlmis/postgres:12-debezium) Security · 21 CVEs

How to fix

No fixed version of gnutls28 is available yet. Check whether openlmis/postgres:12-debezium needs gnutls28 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-42010 fixed in no fix yet
  • High CVE-2023-0361 fixed in 3.7.1-5+deb11u3
  • High CVE-2026-42011 fixed in no fix yet
  • High CVE-2022-2509 fixed in 3.7.1-5+deb11u2
  • High CVE-2024-0553 fixed in 3.7.1-5+deb11u5
  • High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
  • High CVE-2026-33845 fixed in no fix yet
  • High CVE-2026-33846 fixed in no fix yet
  • High CVE-2026-42009 fixed in no fix yet
  • Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
  • Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
  • Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
  • Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
  • Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
  • Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
  • Medium CVE-2021-4209 fixed in 3.7.1-5+deb11u1
  • Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
  • Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
  • Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
  • Medium CVE-2026-3833 fixed in no fix yet
  • and 1 more
High 19 known vulnerabilities in gnutls28@3.7.9-2 (driesva/proftpd) Security · 19 CVEs

How to fix

Update gnutls28 from 3.7.9-2 to 3.7.9-2+deb12u7 or later in driesva/proftpd. If the 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.9-2+deb12u7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-42010 fixed in 3.7.9-2+deb12u7
  • High CVE-2026-42011 fixed in 3.7.9-2+deb12u7
  • High CVE-2024-0553 fixed in 3.7.9-2+deb12u2
  • High CVE-2024-0567 fixed in 3.7.9-2+deb12u2
  • High CVE-2026-33845 fixed in 3.7.9-2+deb12u7
  • High CVE-2026-33846 fixed in 3.7.9-2+deb12u7
  • High CVE-2026-42009 fixed in 3.7.9-2+deb12u7
  • Medium CVE-2025-9820 fixed in 3.7.9-2+deb12u6
  • Medium CVE-2024-28835 fixed in 3.7.9-2+deb12u3
  • Medium CVE-2024-12243 fixed in 3.7.9-2+deb12u4
  • Medium CVE-2024-28834 fixed in 3.7.9-2+deb12u3
  • Medium CVE-2025-14831 fixed in 3.7.9-2+deb12u6
  • Medium CVE-2023-5981 fixed in 3.7.9-2+deb12u1
  • Medium CVE-2025-32988 fixed in 3.7.9-2+deb12u5
  • Medium CVE-2025-32990 fixed in 3.7.9-2+deb12u5
  • Medium CVE-2025-6395 fixed in 3.7.9-2+deb12u5
  • Medium CVE-2026-3833 fixed in 3.7.9-2+deb12u7
  • Low CVE-2011-3389 fixed in no fix yet
  • Low CVE-2025-32989 fixed in 3.7.9-2+deb12u5
High 18 known vulnerabilities in bind@32%3A9.11.4-16.P2.el7 (openlmis/debezium-connect) Security · 18 CVEs

How to fix

Update bind from 32%3A9.11.4-16.P2.el7 to 32:9.11.4-16.P2.el7_8.6 or later in openlmis/debezium-connect. If the 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:9.11.4-16.P2.el7_8.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-2020-8617 fixed in 32:9.11.4-16.P2.el7_8.6
  • High CVE-2021-25215 fixed in 32:9.11.4-26.P2.el7_9.5
  • High CVE-2022-38177 fixed in 32:9.11.4-26.P2.el7_9.10
  • High CVE-2022-38178 fixed in 32:9.11.4-26.P2.el7_9.10
  • High CVE-2023-2828 fixed in 32:9.11.4-26.P2.el7_9.14
  • High CVE-2023-3341 fixed in 32:9.11.4-26.P2.el7_9.15
  • High CVE-2023-4408 fixed in 32:9.11.4-26.P2.el7_9.16
  • High CVE-2023-50387 fixed in 32:9.11.4-26.P2.el7_9.16
  • High CVE-2023-50868 fixed in 32:9.11.4-26.P2.el7_9.16
  • High CVE-2026-1519 fixed in no fix yet
  • High CVE-2020-8625 fixed in 32:9.11.4-26.P2.el7_9.4
  • High CVE-2020-8616 fixed in 32:9.11.4-16.P2.el7_8.6
  • Medium CVE-2020-8624 fixed in 32:9.11.4-26.P2.el7_9.2
  • Medium CVE-2022-2795 fixed in 32:9.11.4-26.P2.el7_9.13
  • Medium CVE-2020-8622 fixed in 32:9.11.4-26.P2.el7_9.2
  • Medium CVE-2021-25214 fixed in 32:9.11.4-26.P2.el7_9.7
  • Medium CVE-2021-25220 fixed in 32:9.11.4-26.P2.el7_9.13
  • Medium CVE-2020-8623 fixed in 32:9.11.4-26.P2.el7_9.2
High 18 known vulnerabilities in poppler@20.09.0-3.1 (openlmis/postgres:12-debezium) Security · 18 CVEs

How to fix

Update poppler from 20.09.0-3.1 to 20.09.0-3.1+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 20.09.0-3.1+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-38784 fixed in 20.09.0-3.1+deb11u1
  • Medium CVE-2025-32364 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2025-32365 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2024-56378 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2020-36024 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2020-36023 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2022-27337 fixed in 20.09.0-3.1+deb11u1
  • Medium CVE-2022-37050 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2022-37051 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2022-37052 fixed in 20.09.0-3.1+deb11u2
  • Medium CVE-2022-38349 fixed in 20.09.0-3.1+deb11u2
  • Low CVE-2013-4472 fixed in no fix yet
  • Low CVE-2017-2814 fixed in no fix yet
  • Low CVE-2017-2818 fixed in no fix yet
  • Low CVE-2017-2820 fixed in no fix yet
  • Low CVE-2017-9083 fixed in no fix yet
  • Low CVE-2022-24106 fixed in no fix yet
  • Low CVE-2024-6239 fixed in no fix yet
High 17 known vulnerabilities in curl@7.52.1-r0 (gliderlabs/consul-server) Security · 17 CVEs

How to fix

Update curl from 7.52.1-r0 to 7.55.0-r1 or later in gliderlabs/consul-server. If the 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.55.0-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-2017-1000254 fixed in 7.55.0-r1
  • High CVE-2018-1000121 fixed in 7.59.0-r0
  • High CVE-2017-1000257 fixed in 7.55.0-r2
  • High CVE-2018-1000005 fixed in 7.58.0-r0
  • High CVE-2018-1000122 fixed in 7.59.0-r0
  • High CVE-2018-1000301 fixed in 7.60.0-r0
  • High CVE-2017-8816 fixed in 7.57.0-r0
  • High CVE-2017-8817 fixed in 7.57.0-r0
  • High CVE-2017-8818 fixed in 7.57.0-r0
  • High CVE-2018-1000120 fixed in 7.59.0-r0
  • High CVE-2018-1000300 fixed in 7.60.0-r0
  • Medium CVE-2017-2629 fixed in 7.52.1-r2
  • Medium CVE-2017-7468 fixed in 7.52.1-r2
  • Medium CVE-2017-1000099 fixed in 7.55.0-r0
  • Medium CVE-2017-1000100 fixed in 7.55.0-r0
  • Medium CVE-2017-1000101 fixed in 7.55.0-r0
  • Low CVE-2017-7407 fixed in 7.52.1-r2
High 16 known vulnerabilities in container-getty@.service (openlmis/bmp) Security · 16 CVEs

How to fix

Update container-getty from .service to 229-4ubuntu19 or later in openlmis/bmp. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 229-4ubuntu19); if 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-9445 fixed in 229-4ubuntu19
  • High CVE-2018-16864 fixed in 229-4ubuntu21.15
  • High CVE-2018-16865 fixed in 229-4ubuntu21.15
  • Medium CVE-2018-16866 fixed in 229-4ubuntu21.15
  • Medium CVE-2019-6454 fixed in 229-4ubuntu21.16
  • Medium CVE-2018-1049 fixed in 229-4ubuntu21.1
  • Medium CVE-2018-15687 fixed in 229-4ubuntu21.8
  • Medium CVE-2019-3842 fixed in 229-4ubuntu21.21
  • Medium CVE-2017-15908 fixed in 229-4ubuntu21.1
  • Medium CVE-2018-15686 fixed in 229-4ubuntu21.8
  • Medium CVE-2018-6954 fixed in 229-4ubuntu21.15
  • Medium CVE-2020-1712 fixed in 229-4ubuntu21.27
  • Medium CVE-2018-15688 fixed in 229-4ubuntu21.6
  • Low CVE-2019-20386 fixed in 229-4ubuntu21.27
  • Low CVE-2018-16888 fixed in 229-4ubuntu21.27
  • Low CVE-2017-9217 fixed in 229-4ubuntu19
High 16 known vulnerabilities in glib2.0@2.66.8-1 (openlmis/postgres:12-debezium) Security · 16 CVEs

How to fix

Update glib2.0 from 2.66.8-1 to 2.66.8-1+deb11u7 or later in openlmis/postgres:12-debezium. If the 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.66.8-1+deb11u7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-13601 fixed in 2.66.8-1+deb11u7
  • High CVE-2024-52533 fixed in 2.66.8-1+deb11u5
  • Medium CVE-2026-1484 fixed in 2.66.8-1+deb11u8
  • Medium CVE-2025-4373 fixed in 2.66.8-1+deb11u7
  • Medium CVE-2024-34397 fixed in 2.66.8-1+deb11u2
  • Medium CVE-2026-1489 fixed in 2.66.8-1+deb11u8
  • Medium CVE-2023-29499 fixed in 2.66.8-1+deb11u1
  • Medium CVE-2023-32611 fixed in 2.66.8-1+deb11u1
  • Medium CVE-2023-32665 fixed in 2.66.8-1+deb11u1
  • Medium CVE-2025-14087 fixed in 2.66.8-1+deb11u7
  • Medium CVE-2025-14512 fixed in 2.66.8-1+deb11u7
  • Low CVE-2012-0039 fixed in no fix yet
  • Low CVE-2026-1485 fixed in 2.66.8-1+deb11u8
  • Low CVE-2025-3360 fixed in 2.66.8-1+deb11u6
  • Low CVE-2025-7039 fixed in 2.66.8-1+deb11u7
  • Low CVE-2026-0988 fixed in 2.66.8-1+deb11u8
High 16 known vulnerabilities in openjpeg2@2.4.0-3 (openlmis/postgres:12-debezium) Security · 16 CVEs

How to fix

Update openjpeg2 from 2.4.0-3 to 2.4.0-3+deb11u1 or later in openlmis/postgres:12-debezium. If the 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.0-3+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-3575 fixed in 2.4.0-3+deb11u1
  • Medium CVE-2021-29338 fixed in 2.4.0-3+deb11u1
  • Medium CVE-2022-1122 fixed in 2.4.0-3+deb11u1
  • Medium CVE-2024-56826 fixed in 2.4.0-3+deb11u1
  • Medium CVE-2024-56827 fixed in 2.4.0-3+deb11u1
  • Medium CVE-2025-50952 fixed in 2.4.0-3+deb11u2
  • Low CVE-2016-10505 fixed in no fix yet
  • Low CVE-2016-9113 fixed in no fix yet
  • Low CVE-2016-9114 fixed in no fix yet
  • Low CVE-2016-9115 fixed in no fix yet
  • Low CVE-2016-9116 fixed in no fix yet
  • Low CVE-2016-9117 fixed in no fix yet
  • Low CVE-2016-9580 fixed in no fix yet
  • Low CVE-2016-9581 fixed in no fix yet
  • Low CVE-2018-16376 fixed in no fix yet
  • Low CVE-2026-6192 fixed in no fix yet
High 16 known vulnerabilities in systemd@247.3-6 (openlmis/postgres:12-debezium) Security · 16 CVEs

How to fix

Update systemd from 247.3-6 to 247.3-7+deb11u6 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 247.3-7+deb11u6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-50387 fixed in 247.3-7+deb11u6
  • High CVE-2023-50868 fixed in 247.3-7+deb11u6
  • Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
  • Medium CVE-2021-3997 fixed in 247.3-7
  • Medium CVE-2022-3821 fixed in 247.3-7+deb11u2
  • Medium CVE-2022-4415 fixed in 247.3-7+deb11u2
  • Medium CVE-2026-29111 fixed in 247.3-7+deb11u8
  • Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
  • Medium CVE-2026-40225 fixed in 247.3-7+deb11u8
  • Medium CVE-2026-40226 fixed in 247.3-7+deb11u8
  • Medium CVE-2026-4105 fixed in 247.3-7+deb11u8
  • Low CVE-2013-4392 fixed in no fix yet
  • Low CVE-2020-13529 fixed in no fix yet
  • Low CVE-2023-31437 fixed in no fix yet
  • Low CVE-2023-31438 fixed in no fix yet
  • Low CVE-2023-31439 fixed in no fix yet
High 15 known vulnerabilities in aa_ER@saaho (openlmis/debezium-connect) Security · 15 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether openlmis/debezium-connect needs aa_ER at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-4046 fixed in no fix yet
  • High CVE-2024-33599 fixed in 2.17-326.el7_9.3
  • High CVE-2024-2961 fixed in 2.17-326.el7_9.3
  • Medium CVE-2015-8983 fixed in no fix yet
  • Medium CVE-2019-25013 fixed in 2.17-322.el7_9
  • Medium CVE-2024-33600 fixed in 2.17-326.el7_9.3
  • Medium CVE-2020-10029 fixed in 2.17-322.el7_9
  • Medium CVE-2009-5155 fixed in no fix yet
  • Medium CVE-2020-29573 fixed in 2.17-322.el7_9
  • Low CVE-2015-8984 fixed in no fix yet
  • Low CVE-2015-8985 fixed in no fix yet
  • Low CVE-2015-8982 fixed in no fix yet
  • Low CVE-2019-19126 fixed in 2.17-317.el7
  • Low CVE-2024-33601 fixed in 2.17-326.el7_9.3
  • Low CVE-2024-33602 fixed in 2.17-326.el7_9.3
High 15 known vulnerabilities in expat@2.1.0-11.el7 (openlmis/debezium-connect) Security · 15 CVEs

How to fix

Update expat from 2.1.0-11.el7 to 2.1.0-15.el7_9 or later in openlmis/debezium-connect. If the 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.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-2022-40674 fixed in 2.1.0-15.el7_9
  • High CVE-2022-22822 fixed in 2.1.0-14.el7_9
  • High CVE-2022-22823 fixed in 2.1.0-14.el7_9
  • High CVE-2022-22824 fixed in 2.1.0-14.el7_9
  • High CVE-2022-25235 fixed in 2.1.0-14.el7_9
  • High CVE-2022-25236 fixed in 2.1.0-14.el7_9
  • High CVE-2022-25315 fixed in 2.1.0-14.el7_9
  • Medium CVE-2018-20843 fixed in 2.1.0-12.el7
  • Medium CVE-2021-46143 fixed in 2.1.0-14.el7_9
  • Medium CVE-2021-45960 fixed in 2.1.0-14.el7_9
  • Medium CVE-2022-22825 fixed in 2.1.0-14.el7_9
  • Medium CVE-2022-22826 fixed in 2.1.0-14.el7_9
  • Medium CVE-2022-22827 fixed in 2.1.0-14.el7_9
  • Medium CVE-2022-23852 fixed in 2.1.0-14.el7_9
  • Low CVE-2019-15903 fixed in 2.1.0-12.el7
High 15 known vulnerabilities in netty-codec-http@4.1.51.Final (openlmis/debezium-connect) Security · 15 CVEs

How to fix

Update netty-codec-http from 4.1.51.Final to 4.1.133.Final or later in openlmis/debezium-connect. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.133.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-42584 fixed in 4.1.133.Final
  • High CVE-2026-33870 fixed in 4.1.132.Final
  • High CVE-2026-42587 fixed in 4.1.133.Final
  • Medium CVE-2024-29025 fixed in 4.1.108.Final
  • Medium CVE-2026-41417 fixed in 4.1.133.Final
  • Medium CVE-2022-24823 fixed in 4.1.77.Final
  • Medium CVE-2026-42581 fixed in 4.1.133.Final
  • Medium CVE-2021-21295 fixed in 4.1.61.Final
  • Medium CVE-2021-21409 fixed in 4.1.61.Final
  • Medium CVE-2021-21290 fixed in 4.1.59.Final
  • Medium CVE-2021-43797 fixed in 4.1.71.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Medium CVE-2026-42580 fixed in 4.1.133.Final
  • Medium CVE-2026-42585 fixed in 4.1.133.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
High 15 known vulnerabilities in postgresql@42.2.8 (openlmis/debezium-connect) Security · 15 CVEs

How to fix

Update postgresql from 42.2.8 to 42.2.25 or later in openlmis/debezium-connect. If the 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-21724 fixed in 42.2.25
  • High CVE-2022-31197 fixed in 42.2.26
  • High CVE-2022-31197 fixed in 42.2.26
  • High CVE-2026-42198 fixed in 42.7.11
  • High CVE-2026-42198 fixed in 42.7.11
  • High CVE-2020-13692 fixed in 42.2.13
  • High CVE-2024-1597 fixed in 42.2.28
  • High CVE-2024-1597 fixed in 42.2.28
  • Medium GHSA-673j-qm5f-xpv8 fixed in 42.3.3
  • Medium GHSA-673j-qm5f-xpv8 fixed in 42.3.3
  • Medium CVE-2022-41946 fixed in 42.2.27
  • Medium CVE-2022-41946 fixed in 42.2.27
  • Low CVE-2022-26520 fixed in 42.3.3
  • Low CVE-2022-26520 fixed in 42.3.3
High 15 known vulnerabilities in libpng1.6@1.6.37-3 (openlmis/postgres:12-debezium) Security · 15 CVEs

How to fix

Update libpng1.6 from 1.6.37-3 to 1.6.37-3+deb11u1 or later in openlmis/postgres:12-debezium. If the 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.37-3+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-64720 fixed in 1.6.37-3+deb11u1
  • High CVE-2025-65018 fixed in 1.6.37-3+deb11u1
  • High CVE-2025-66293 fixed in 1.6.37-3+deb11u1
  • High CVE-2026-33416 fixed in 1.6.37-3+deb11u3
  • High CVE-2026-33636 fixed in 1.6.37-3+deb11u3
  • High CVE-2026-25646 fixed in 1.6.37-3+deb11u2
  • Medium CVE-2026-34757 fixed in 1.6.37-3+deb11u4
  • Medium CVE-2025-64505 fixed in 1.6.37-3+deb11u1
  • Medium CVE-2025-64506 fixed in 1.6.37-3+deb11u1
  • Medium CVE-2026-22695 fixed in 1.6.37-3+deb11u2
  • Medium CVE-2026-22801 fixed in 1.6.37-3+deb11u2
  • Low CVE-2019-6129 fixed in no fix yet
  • Low CVE-2021-4214 fixed in no fix yet
  • Low CVE-2025-28164 fixed in no fix yet
  • Low CVE-2026-3713 fixed in no fix yet
High 13 known vulnerabilities in openssl@1.0.2j-r0 (gliderlabs/consul-server) Security · 13 CVEs

How to fix

Update openssl from 1.0.2j-r0 to 1.0.2k-r0 or later in gliderlabs/consul-server. If the 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-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-2017-3731 fixed in 1.0.2k-r0
  • High CVE-2018-0732 fixed in 1.0.2o-r1
  • Medium CVE-2018-5407 fixed in 1.0.2q-r0
  • Medium CVE-2017-3735 fixed in 1.0.2m-r0
  • Medium CVE-2016-7055 fixed in 1.0.2k-r0
  • Medium CVE-2017-3732 fixed in 1.0.2k-r0
  • Medium CVE-2017-3737 fixed in 1.0.2n-r0
  • Medium CVE-2017-3738 fixed in 1.0.2n-r0
  • Medium CVE-2018-0733 fixed in 1.0.2o-r0
  • Medium CVE-2018-0734 fixed in 1.0.2q-r0
  • Medium CVE-2018-0737 fixed in 1.0.2o-r2
  • Medium CVE-2017-3736 fixed in 1.0.2m-r0
  • Medium CVE-2018-0739 fixed in 1.0.2o-r0
High 13 known vulnerabilities in jetty-server@7.3.0.v20110203 (openlmis/bmp) Security · 13 CVEs

How to fix

Update jetty-server from 7.3.0.v20110203 to 9.4.33.v20201020, or later in openlmis/bmp. If the 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.4.33.v20201020,); if 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-27216 fixed in 9.4.33.v20201020,
  • High CVE-2015-2080 fixed in 9.2.9.v20150224
  • High CVE-2017-7656 fixed in 9.3.24.v20180605
  • High CVE-2017-9735 fixed in 9.2.22.v20170606
  • High CVE-2021-28165 fixed in 9.4.39
  • High CVE-2017-7657 fixed in 9.2.25.v20180606
  • High CVE-2017-7658 fixed in 9.2.25.v20180606
  • Medium CVE-2011-4461 fixed in 8.1.0.RC4
  • Medium CVE-2019-10247 fixed in 9.2.28.v20190418
  • Medium CVE-2023-26048 fixed in 9.4.51.v20230217
  • Medium CVE-2019-10241 fixed in 9.2.27.v20190403
  • Low CVE-2023-26049 fixed in 9.4.51.v20230217
  • Low CVE-2021-34428 fixed in 9.4.41
High 13 known vulnerabilities in jackson-databind@2.10.5 (openlmis/debezium-connect) Security · 13 CVEs

How to fix

Update jackson-databind from 2.10.5 to 2.10.5.1 or later in openlmis/debezium-connect. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.10.5.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2020-25649 fixed in 2.10.5.1
  • High CVE-2020-36518 fixed in 2.12.6.1
  • High CVE-2020-36518 fixed in 2.12.6.1
  • High CVE-2020-36518 fixed in 2.12.6.1
  • High CVE-2021-46877 fixed in 2.12.6
  • High CVE-2021-46877 fixed in 2.12.6
  • High CVE-2021-46877 fixed in 2.12.6
  • High CVE-2022-42003 fixed in 2.12.7.1
  • High CVE-2022-42003 fixed in 2.12.7.1
  • High CVE-2022-42003 fixed in 2.12.7.1
  • High CVE-2022-42004 fixed in 2.12.7.1
  • High CVE-2022-42004 fixed in 2.12.7.1
  • High CVE-2022-42004 fixed in 2.12.7.1
High 13 known vulnerabilities in nss@3.44.0-7.el7_7 (openlmis/debezium-connect) Security · 13 CVEs

How to fix

Update nss from 3.44.0-7.el7_7 to 3.79.0-5.el7_9 or later in openlmis/debezium-connect. If the 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.79.0-5.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-2023-0767 fixed in 3.79.0-5.el7_9
  • High CVE-2021-43527 fixed in 3.67.0-4.el7_9
  • Medium CVE-2020-12400 fixed in 3.53.1-3.el7_9
  • Medium CVE-2020-12401 fixed in 3.53.1-3.el7_9
  • Medium CVE-2020-12402 fixed in 3.53.1-3.el7_9
  • Medium CVE-2020-6829 fixed in 3.53.1-3.el7_9
  • Medium CVE-2019-11756 fixed in 3.53.1-3.el7_9
  • Medium CVE-2020-12403 fixed in 3.53.1-3.el7_9
  • Medium CVE-2019-11719 fixed in 3.53.1-3.el7_9
  • Medium CVE-2020-25648 fixed in 3.53.1-7.el7_9
  • Medium CVE-2019-17006 fixed in 3.53.1-3.el7_9
  • Low CVE-2019-11727 fixed in 3.53.1-3.el7_9
  • Low CVE-2019-17023 fixed in 3.53.1-3.el7_9
High 13 known vulnerabilities in nss@2%3A3.61-1%2Bdeb11u1 (openlmis/postgres:12-debezium) Security · 13 CVEs

How to fix

Update nss from 2%3A3.61-1%2Bdeb11u1 to 2:3.61-1+deb11u4 or later in openlmis/postgres:12-debezium. If the 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.61-1+deb11u4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-0743 fixed in 2:3.61-1+deb11u4
  • High CVE-2026-6766 fixed in no fix yet
  • High CVE-2026-6772 fixed in no fix yet
  • High CVE-2023-0767 fixed in 2:3.61-1+deb11u3
  • High CVE-2024-6609 fixed in 2:3.61-1+deb11u4
  • High CVE-2024-6602 fixed in 2:3.61-1+deb11u4
  • High CVE-2026-2781 fixed in 2:3.61-1+deb11u5
  • Medium CVE-2026-6767 fixed in no fix yet
  • Medium CVE-2022-22747 fixed in 2:3.61-1+deb11u2
  • Low CVE-2017-11695 fixed in no fix yet
  • Low CVE-2017-11696 fixed in no fix yet
  • Low CVE-2017-11697 fixed in no fix yet
  • Low CVE-2017-11698 fixed in no fix yet
High 13 known vulnerabilities in openssl@1.0.2j-r0 (openlmis/rsyslog:1) Security · 13 CVEs

How to fix

Update openssl from 1.0.2j-r0 to 1.0.2k-r0 or later in openlmis/rsyslog: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.2k-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-2017-3731 fixed in 1.0.2k-r0
  • High CVE-2018-0732 fixed in 1.0.2o-r1
  • Medium CVE-2018-5407 fixed in 1.0.2q-r0
  • Medium CVE-2017-3735 fixed in 1.0.2m-r0
  • Medium CVE-2016-7055 fixed in 1.0.2k-r0
  • Medium CVE-2017-3732 fixed in 1.0.2k-r0
  • Medium CVE-2017-3737 fixed in 1.0.2n-r0
  • Medium CVE-2017-3738 fixed in 1.0.2n-r0
  • Medium CVE-2018-0733 fixed in 1.0.2o-r0
  • Medium CVE-2018-0734 fixed in 1.0.2q-r0
  • Medium CVE-2018-0737 fixed in 1.0.2o-r1
  • Medium CVE-2017-3736 fixed in 1.0.2m-r0
  • Medium CVE-2018-0739 fixed in 1.0.2o-r0
High 12 known vulnerabilities in systemd@252.12-1~deb12u1 (driesva/proftpd) Security · 12 CVEs

How to fix

Update systemd from 252.12-1~deb12u1 to 252.23-1~deb12u1 or later in driesva/proftpd. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 252.23-1~deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-50387 fixed in 252.23-1~deb12u1
  • High CVE-2023-50868 fixed in 252.23-1~deb12u1
  • Medium CVE-2025-4598 fixed in 252.38-1~deb12u1
  • Medium CVE-2026-29111 fixed in 252.39-1~deb12u2
  • Medium CVE-2023-7008 fixed in 252.21-1~deb12u1
  • Medium CVE-2026-40225 fixed in 252.39-1~deb12u2
  • Medium CVE-2026-40226 fixed in 252.39-1~deb12u2
  • Medium CVE-2026-4105 fixed in 252.39-1~deb12u2
  • Low CVE-2013-4392 fixed in no fix yet
  • Low CVE-2023-31437 fixed in no fix yet
  • Low CVE-2023-31438 fixed in no fix yet
  • Low CVE-2023-31439 fixed in no fix yet
High 12 known vulnerabilities in protobuf-java@3.13.0 (openlmis/debezium-connect) Security · 12 CVEs

How to fix

Update protobuf-java from 3.13.0 to 3.16.1 or later in openlmis/debezium-connect. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.16.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-2021-22569 fixed in 3.16.1
  • High CVE-2021-22569 fixed in 3.16.1
  • High CVE-2022-3509 fixed in 3.16.3
  • High CVE-2022-3509 fixed in 3.16.3
  • High CVE-2022-3510 fixed in 3.16.3
  • High CVE-2022-3510 fixed in 3.16.3
  • High CVE-2024-7254 fixed in 3.25.5
  • High CVE-2024-7254 fixed in 3.25.5
  • Medium CVE-2021-22570 fixed in 3.15.0
  • Medium CVE-2021-22570 fixed in 3.15.0
  • Medium CVE-2022-3171 fixed in 3.16.3
  • Medium CVE-2022-3171 fixed in 3.16.3

and 177 more groups with 605 findings

Medium 501

Medium 152 known vulnerabilities in openjdk-8@8u111-b14-2ubuntu0.16.04.2 (openlmis/bmp) Security · 152 CVEs

How to fix

Update openjdk-8 from 8u111-b14-2ubuntu0.16.04.2 to 8u272-b10-0ubuntu1~16.04 or later in openlmis/bmp. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8u272-b10-0ubuntu1~16.04); if 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-14779 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14781 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14782 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14792 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14796 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14797 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14798 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2020-14803 fixed in 8u272-b10-0ubuntu1~16.04
  • Medium CVE-2021-2163 fixed in 8u292-b10-0ubuntu1~16.04.1
  • Medium CVE-2017-10193 fixed in 8u131-b11-2ubuntu1.16.04.2
  • Medium CVE-2017-10345 fixed in 8u151-b12-0ubuntu0.16.04.2
  • Medium CVE-2018-3139 fixed in 8u181-b13-1ubuntu0.16.04.1
  • Medium CVE-2019-2945 fixed in 8u232-b09-0ubuntu1~16.04.1
  • Medium CVE-2018-3136 fixed in 8u181-b13-1ubuntu0.16.04.1
  • Medium CVE-2019-2786 fixed in 8u222-b10-1ubuntu1~16.04.1
  • Medium CVE-2018-2579 fixed in 8u162-b12-0ubuntu0.16.04.2
  • Medium CVE-2018-2952 fixed in 8u181-b13-0ubuntu0.16.04.1
  • Medium CVE-2019-2842 fixed in 8u222-b10-1ubuntu1~16.04.1
  • Medium CVE-2019-2894 fixed in 8u232-b09-0ubuntu1~16.04.1
  • Medium CVE-2019-2962 fixed in 8u232-b09-0ubuntu1~16.04.1
  • and 132 more
Medium 24 known vulnerabilities in sqlite3@3.11.0-1ubuntu1 (openlmis/bmp) Security · 24 CVEs

How to fix

Update sqlite3 from 3.11.0-1ubuntu1 to 3.11.0-1ubuntu1.5 or later in openlmis/bmp. If the 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.11.0-1ubuntu1.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-2020-13434 fixed in 3.11.0-1ubuntu1.5
  • Medium CVE-2020-13632 fixed in 3.11.0-1ubuntu1.5
  • Medium CVE-2019-13750 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2019-13751 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2019-13752 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2019-13753 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2020-13630 fixed in 3.11.0-1ubuntu1.5
  • Medium CVE-2019-19926 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2019-9936 fixed in 3.11.0-1ubuntu1.2
  • Medium CVE-2018-20346 fixed in 3.11.0-1ubuntu1.2
  • Medium CVE-2018-20506 fixed in 3.11.0-1ubuntu1.2
  • Medium CVE-2019-13734 fixed in 3.11.0-1ubuntu1.4
  • Medium CVE-2019-8457 fixed in 3.11.0-1ubuntu1.2
  • Low CVE-2017-13685 fixed in 3.11.0-1ubuntu1.2
  • Low CVE-2016-6153 fixed in 3.11.0-1ubuntu1.2
  • Low CVE-2019-16168 fixed in 3.11.0-1ubuntu1.3
  • Low CVE-2018-8740 fixed in 3.11.0-1ubuntu1.1
  • Low CVE-2019-20218 fixed in 3.11.0-1ubuntu1.4
  • Low CVE-2019-9937 fixed in 3.11.0-1ubuntu1.2
  • Low CVE-2019-5827 fixed in 3.11.0-1ubuntu1.3
  • and 4 more
Medium 23 known vulnerabilities in nss@2%3A3.23-0ubuntu0.16.04.1 (openlmis/bmp) Security · 23 CVEs

How to fix

Update nss from 2%3A3.23-0ubuntu0.16.04.1 to 2:3.28.4-0ubuntu0.16.04.11 or later in openlmis/bmp. If the 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.28.4-0ubuntu0.16.04.11); if 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-12399 fixed in 2:3.28.4-0ubuntu0.16.04.11
  • Medium CVE-2020-12402 fixed in 2:3.28.4-0ubuntu0.16.04.12
  • Medium CVE-2020-12400 fixed in 2:3.28.4-0ubuntu0.16.04.13
  • Medium CVE-2020-12401 fixed in 2:3.28.4-0ubuntu0.16.04.13
  • Medium CVE-2017-5462 fixed in 2:3.28.4-0ubuntu0.16.04.1
  • Medium CVE-2020-6829 fixed in 2:3.28.4-0ubuntu0.16.04.13
  • Medium CVE-2016-8635 fixed in 2:3.26.2-0ubuntu0.16.04.2
  • Medium CVE-2016-9074 fixed in 2:3.26.2-0ubuntu0.16.04.2
  • Medium CVE-2018-12404 fixed in 2:3.28.4-0ubuntu0.16.04.4
  • Medium CVE-2018-18508 fixed in 2:3.28.4-0ubuntu0.16.04.5
  • Medium CVE-2016-5285 fixed in 2:3.26.2-0ubuntu0.16.04.2
  • Medium CVE-2017-7502 fixed in 2:3.28.4-0ubuntu0.16.04.2
  • Medium CVE-2017-7805 fixed in 2:3.28.4-0ubuntu0.16.04.3
  • Medium CVE-2019-11719 fixed in 2:3.28.4-0ubuntu0.16.04.6
  • Medium CVE-2019-11729 fixed in 2:3.28.4-0ubuntu0.16.04.6
  • Medium CVE-2019-17007 fixed in 2:3.28.4-0ubuntu0.16.04.9
  • Medium CVE-2019-11745 fixed in 2:3.28.4-0ubuntu0.16.04.8
  • Medium CVE-2020-12403 fixed in 2:3.28.4-0ubuntu0.16.04.14
  • Medium CVE-2017-5461 fixed in 2:3.28.4-0ubuntu0.16.04.1
  • Medium CVE-2019-17006 fixed in 2:3.28.4-0ubuntu0.16.04.10
  • and 3 more
Medium 15 known vulnerabilities in perl@5.22.1-9 (openlmis/bmp) Security · 15 CVEs

How to fix

Update perl from 5.22.1-9 to 5.22.1-9ubuntu0.2 or later in openlmis/bmp. If the 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.22.1-9ubuntu0.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-2017-12837 fixed in 5.22.1-9ubuntu0.2
  • Medium CVE-2018-12015 fixed in 5.22.1-9ubuntu0.5
  • Medium CVE-2018-6798 fixed in 5.22.1-9ubuntu0.3
  • Medium CVE-2017-12883 fixed in 5.22.1-9ubuntu0.2
  • Medium CVE-2018-18313 fixed in 5.22.1-9ubuntu0.6
  • Medium CVE-2018-18311 fixed in 5.22.1-9ubuntu0.6
  • Medium CVE-2018-18312 fixed in 5.22.1-9ubuntu0.6
  • Medium CVE-2018-18314 fixed in 5.22.1-9ubuntu0.6
  • Medium CVE-2018-6797 fixed in 5.22.1-9ubuntu0.3
  • Medium CVE-2018-6913 fixed in 5.22.1-9ubuntu0.3
  • Low CVE-2017-6512 fixed in 5.22.1-9ubuntu0.3
  • Low CVE-2020-12723 fixed in 5.22.1-9ubuntu0.9
  • Low CVE-2016-6185 fixed in 5.22.1-9ubuntu0.3
  • Low CVE-2020-10543 fixed in 5.22.1-9ubuntu0.9
  • Low CVE-2020-10878 fixed in 5.22.1-9ubuntu0.9
Medium 12 known vulnerabilities in cups@2.1.3-4 (openlmis/bmp) Security · 12 CVEs

How to fix

Update cups from 2.1.3-4 to 2.1.3-4ubuntu0.6 or later in openlmis/bmp. If the 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.3-4ubuntu0.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-2018-4700 fixed in 2.1.3-4ubuntu0.6
  • Medium CVE-2017-18248 fixed in 2.1.3-4ubuntu0.5
  • Medium CVE-2018-4181 fixed in 2.1.3-4ubuntu0.5
  • Medium CVE-2018-4300 fixed in 2.1.3-4ubuntu0.6
  • Medium CVE-2017-18190 fixed in 2.1.3-4ubuntu0.4
  • Medium CVE-2018-4180 fixed in 2.1.3-4ubuntu0.5
  • Medium CVE-2020-3898 fixed in 2.1.3-4ubuntu0.11
  • Medium CVE-2018-6553 fixed in 2.1.3-4ubuntu0.5
  • Medium CVE-2019-8675 fixed in 2.1.3-4ubuntu0.10
  • Medium CVE-2019-8696 fixed in 2.1.3-4ubuntu0.10
  • Low CVE-2019-2180 fixed in 2.1.3-4ubuntu0.10
  • Low CVE-2019-2228 fixed in 2.1.3-4ubuntu0.11
Medium 11 known vulnerabilities in gnutls28@3.4.10-4ubuntu1.1 (openlmis/bmp) Security · 11 CVEs

How to fix

Update gnutls28 from 3.4.10-4ubuntu1.1 to 3.4.10-4ubuntu1.5 or later in openlmis/bmp. If the 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.10-4ubuntu1.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-2018-10846 fixed in 3.4.10-4ubuntu1.5
  • Medium CVE-2018-10844 fixed in 3.4.10-4ubuntu1.5
  • Medium CVE-2018-10845 fixed in 3.4.10-4ubuntu1.5
  • Medium CVE-2017-5335 fixed in 3.4.10-4ubuntu1.2
  • Medium CVE-2017-7507 fixed in 3.4.10-4ubuntu1.3
  • Medium CVE-2017-5334 fixed in 3.4.10-4ubuntu1.2
  • Medium CVE-2017-5336 fixed in 3.4.10-4ubuntu1.2
  • Medium CVE-2017-5337 fixed in 3.4.10-4ubuntu1.2
  • Low CVE-2016-7444 fixed in 3.4.10-4ubuntu1.2
  • Low CVE-2016-8610 fixed in 3.4.10-4ubuntu1.2
  • Low CVE-2017-7869 fixed in 3.4.10-4ubuntu1.3
Medium 10 known vulnerabilities in nspr@4.21.0-1.el7 (openlmis/debezium-connect) Security · 10 CVEs

How to fix

Update nspr from 4.21.0-1.el7 to 4.25.0-2.el7_9 or later in openlmis/debezium-connect. If the 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.25.0-2.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-12400 fixed in 4.25.0-2.el7_9
  • Medium CVE-2020-12401 fixed in 4.25.0-2.el7_9
  • Medium CVE-2020-12402 fixed in 4.25.0-2.el7_9
  • Medium CVE-2020-6829 fixed in 4.25.0-2.el7_9
  • Medium CVE-2019-11756 fixed in 4.25.0-2.el7_9
  • Medium CVE-2020-12403 fixed in 4.25.0-2.el7_9
  • Medium CVE-2019-11719 fixed in 4.25.0-2.el7_9
  • Medium CVE-2019-17006 fixed in 4.25.0-2.el7_9
  • Low CVE-2019-11727 fixed in 4.25.0-2.el7_9
  • Low CVE-2019-17023 fixed in 4.25.0-2.el7_9
Medium 10 known vulnerabilities in nss-softokn@3.44.0-8.el7_7 (openlmis/debezium-connect) Security · 10 CVEs

How to fix

Update nss-softokn from 3.44.0-8.el7_7 to 3.53.1-6.el7_9 or later in openlmis/debezium-connect. If the 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.53.1-6.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-12400 fixed in 3.53.1-6.el7_9
  • Medium CVE-2020-12401 fixed in 3.53.1-6.el7_9
  • Medium CVE-2020-12402 fixed in 3.53.1-6.el7_9
  • Medium CVE-2020-6829 fixed in 3.53.1-6.el7_9
  • Medium CVE-2019-11756 fixed in 3.53.1-6.el7_9
  • Medium CVE-2020-12403 fixed in 3.53.1-6.el7_9
  • Medium CVE-2019-11719 fixed in 3.53.1-6.el7_9
  • Medium CVE-2019-17006 fixed in 3.53.1-6.el7_9
  • Low CVE-2019-11727 fixed in 3.53.1-6.el7_9
  • Low CVE-2019-17023 fixed in 3.53.1-6.el7_9
Medium 10 known vulnerabilities in nss-util@3.44.0-4.el7_7 (openlmis/debezium-connect) Security · 10 CVEs

How to fix

Update nss-util from 3.44.0-4.el7_7 to 3.53.1-1.el7_9 or later in openlmis/debezium-connect. If the 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.53.1-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-12400 fixed in 3.53.1-1.el7_9
  • Medium CVE-2020-12401 fixed in 3.53.1-1.el7_9
  • Medium CVE-2020-12402 fixed in 3.53.1-1.el7_9
  • Medium CVE-2020-6829 fixed in 3.53.1-1.el7_9
  • Medium CVE-2019-11756 fixed in 3.53.1-1.el7_9
  • Medium CVE-2020-12403 fixed in 3.53.1-1.el7_9
  • Medium CVE-2019-11719 fixed in 3.53.1-1.el7_9
  • Medium CVE-2019-17006 fixed in 3.53.1-1.el7_9
  • Low CVE-2019-11727 fixed in 3.53.1-1.el7_9
  • Low CVE-2019-17023 fixed in 3.53.1-1.el7_9
Medium 8 known vulnerabilities in krb5@1.13.2%2Bdfsg-5 (openlmis/bmp) Security · 8 CVEs

How to fix

Update krb5 from 1.13.2%2Bdfsg-5 to 1.13.2+dfsg-5ubuntu2.1 or later in openlmis/bmp. If the 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.13.2+dfsg-5ubuntu2.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-2016-3119 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Medium CVE-2016-3120 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Medium CVE-2017-11368 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Medium CVE-2020-28196 fixed in 1.13.2+dfsg-5ubuntu2.2
  • Low CVE-2018-5730 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Low CVE-2018-5729 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Low CVE-2018-5710 fixed in 1.13.2+dfsg-5ubuntu2.1
  • Low CVE-2017-11462 fixed in 1.13.2+dfsg-5ubuntu2.1
Medium 7 known vulnerabilities in libx11@2%3A1.6.3-1ubuntu2 (openlmis/bmp) Security · 7 CVEs

How to fix

Update libx11 from 2%3A1.6.3-1ubuntu2 to 2:1.6.3-1ubuntu2.2 or later in openlmis/bmp. If the 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.6.3-1ubuntu2.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-2020-14344 fixed in 2:1.6.3-1ubuntu2.2
  • Medium CVE-2018-14598 fixed in 2:1.6.3-1ubuntu2.1
  • Medium CVE-2020-14363 fixed in 2:1.6.3-1ubuntu2.2
  • Medium CVE-2018-14599 fixed in 2:1.6.3-1ubuntu2.1
  • Medium CVE-2018-14600 fixed in 2:1.6.3-1ubuntu2.1
  • Low CVE-2016-7942 fixed in 2:1.6.3-1ubuntu2.1
  • Low CVE-2016-7943 fixed in 2:1.6.3-1ubuntu2.1
Medium 7 known vulnerabilities in bcprov-jdk15on@1.60 (openlmis/dev:5.1) Security · 7 CVEs

How to fix

Update bcprov-jdk15on from 1.60 to 1.66 or later in openlmis/dev:5.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-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 sqlite3@3.34.1-3 (openlmis/postgres:12-debezium) Security · 7 CVEs

How to fix

Update sqlite3 from 3.34.1-3 to 3.34.1-3+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.34.1-3+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-7104 fixed in 3.34.1-3+deb11u1
  • Low CVE-2021-36690 fixed in 3.34.1-3+deb11u1
  • Low CVE-2021-45346 fixed in no fix yet
  • Low CVE-2022-35737 fixed in no fix yet
  • Low CVE-2025-29088 fixed in no fix yet
  • Low CVE-2025-52099 fixed in no fix yet
  • Low CVE-2025-70873 fixed in no fix yet
Medium 6 known vulnerabilities in wget@1.17.1-1ubuntu1.1 (openlmis/bmp) Security · 6 CVEs

How to fix

Update wget from 1.17.1-1ubuntu1.1 to 1.17.1-1ubuntu1.4 or later in openlmis/bmp. If the 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.1-1ubuntu1.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2018-0494 fixed in 1.17.1-1ubuntu1.4
  • Medium CVE-2017-13089 fixed in 1.17.1-1ubuntu1.3
  • Medium CVE-2017-13090 fixed in 1.17.1-1ubuntu1.3
  • Medium CVE-2019-5953 fixed in 1.17.1-1ubuntu1.5
  • Low CVE-2017-6508 fixed in 1.17.1-1ubuntu1.3
  • Low CVE-2016-7098 fixed in 1.17.1-1ubuntu1.3
Medium 6 known vulnerabilities in jetty-servlets@9.4.33.v20201020 (openlmis/debezium-connect) Security · 6 CVEs

How to fix

Update jetty-servlets from 9.4.33.v20201020 to 9.4.52.v20230823, or later in openlmis/debezium-connect. If the 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.4.52.v20230823,); if 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-41900 fixed in 9.4.52.v20230823,
  • Medium CVE-2021-28169 fixed in 9.4.41
  • Medium CVE-2023-26049 fixed in 9.4.51.v20230217,
  • Medium CVE-2023-40167 fixed in 9.4.52.v20230823,
  • Medium CVE-2024-9823 fixed in 9.4.54
  • Low CVE-2023-36479 fixed in 9.4.52
Medium 5 known vulnerabilities in procps@2%3A3.3.10-4ubuntu2.3 (openlmis/bmp) Security · 5 CVEs

How to fix

Update procps from 2%3A3.3.10-4ubuntu2.3 to 2:3.3.10-4ubuntu2.4 or later in openlmis/bmp. If the 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.10-4ubuntu2.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2018-1122 fixed in 2:3.3.10-4ubuntu2.4
  • Medium CVE-2018-1123 fixed in 2:3.3.10-4ubuntu2.4
  • Medium CVE-2018-1125 fixed in 2:3.3.10-4ubuntu2.4
  • Medium CVE-2018-1124 fixed in 2:3.3.10-4ubuntu2.4
  • Medium CVE-2018-1126 fixed in 2:3.3.10-4ubuntu2.4
Medium 5 known vulnerabilities in binutils@2.27-43.base.el7 (openlmis/debezium-connect) Security · 5 CVEs

How to fix

No fixed version of binutils is available yet. Check whether openlmis/debezium-connect needs binutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-7546 fixed in no fix yet
  • Medium CVE-2021-42574 fixed in 2.27-44.base.el7_9.1
  • Low CVE-2014-9939 fixed in no fix yet
  • Low CVE-2022-38126 fixed in no fix yet
  • Low CVE-2019-17450 fixed in no fix yet
Medium 5 known vulnerabilities in libxml2@2.9.1-6.el7.4 (openlmis/debezium-connect) Security · 5 CVEs

How to fix

Update libxml2 from 2.9.1-6.el7.4 to 2.9.1-6.el7_9.6 or later in openlmis/debezium-connect. If the 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.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

  • Medium CVE-2016-4658 fixed in 2.9.1-6.el7_9.6
  • Medium CVE-2025-9714 fixed in no fix yet
  • Medium CVE-2019-19956 fixed in 2.9.1-6.el7.5
  • Medium CVE-2019-20388 fixed in 2.9.1-6.el7.5
  • Medium CVE-2020-7595 fixed in 2.9.1-6.el7.5
Medium 5 known vulnerabilities in uriparser@0.9.4%2Bdfsg-1 (openlmis/postgres:12-debezium) Security · 5 CVEs

How to fix

No fixed version of uriparser is available yet. Check whether openlmis/postgres:12-debezium needs uriparser 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-2026-42371 fixed in no fix yet
  • Medium CVE-2021-46141 fixed in 0.9.4+dfsg-1+deb11u1
  • Medium CVE-2021-46142 fixed in 0.9.4+dfsg-1+deb11u1
  • Low CVE-2026-44927 fixed in no fix yet
  • Low CVE-2026-44928 fixed in no fix yet
Medium 5 known vulnerabilities in util-linux@2.36.1-8 (openlmis/postgres:12-debezium) Security · 5 CVEs

How to fix

Update util-linux from 2.36.1-8 to 2.36.1-8+deb11u1 or later in openlmis/postgres:12-debezium. If the 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.36.1-8+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2021-3995 fixed in 2.36.1-8+deb11u1
  • Medium CVE-2021-3996 fixed in 2.36.1-8+deb11u1
  • Low CVE-2022-0563 fixed in no fix yet
  • Low CVE-2025-14104 fixed in no fix yet
  • Low CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Medium 5 known vulnerabilities in pip@22.0.4 (openlmis/scalyr) Security · 5 CVEs

How to fix

Update pip from 22.0.4 to 26.1 or later in openlmis/scalyr. If the 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.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-3219 fixed in 26.1
  • Medium CVE-2026-6357 fixed in 26.1
  • 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 4 known vulnerabilities in bash@4.3-14ubuntu1.1 (openlmis/bmp) Security · 4 CVEs

How to fix

Update bash from 4.3-14ubuntu1.1 to 4.3-14ubuntu1.2 or later in openlmis/bmp. If the 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-14ubuntu1.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-2016-7543 fixed in 4.3-14ubuntu1.2
  • Low CVE-2016-9401 fixed in 4.3-14ubuntu1.2
  • Low CVE-2016-0634 fixed in 4.3-14ubuntu1.2
  • Low CVE-2019-9924 fixed in 4.3-14ubuntu1.4
Medium 4 known vulnerabilities in libgcrypt20@1.6.5-2ubuntu0.2 (openlmis/bmp) Security · 4 CVEs

How to fix

Update libgcrypt20 from 1.6.5-2ubuntu0.2 to 1.6.5-2ubuntu0.6 or later in openlmis/bmp. If the 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.5-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-2019-13627 fixed in 1.6.5-2ubuntu0.6
  • Medium CVE-2017-7526 fixed in 1.6.5-2ubuntu0.3
  • Low CVE-2018-0495 fixed in 1.6.5-2ubuntu0.5
  • Low CVE-2017-9526 fixed in 1.6.5-2ubuntu0.3
Medium 4 known vulnerabilities in libjpeg-turbo@1.4.2-0ubuntu3 (openlmis/bmp) Security · 4 CVEs

How to fix

Update libjpeg-turbo from 1.4.2-0ubuntu3 to 1.4.2-0ubuntu3.3 or later in openlmis/bmp. If the 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.2-0ubuntu3.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-2019-2201 fixed in 1.4.2-0ubuntu3.3
  • Medium CVE-2020-13790 fixed in 1.4.2-0ubuntu3.4
  • Low CVE-2018-1152 fixed in 1.4.2-0ubuntu3.1
  • Low CVE-2018-14498 fixed in 1.4.2-0ubuntu3.3
Medium 4 known vulnerabilities in curl@7.29.0-57.el7 (openlmis/debezium-connect) Security · 4 CVEs

How to fix

Update curl from 7.29.0-57.el7 to 7.29.0-59.el7_9.1 or later in openlmis/debezium-connect. If the 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.29.0-59.el7_9.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-8177 fixed in 7.29.0-59.el7_9.1
  • Medium CVE-2019-5482 fixed in 7.29.0-59.el7
  • Medium CVE-2021-22946 fixed in no fix yet
  • Low CVE-2022-43552 fixed in 7.29.0-59.el7_9.2
Medium 4 known vulnerabilities in netty-common@4.1.51.Final (openlmis/debezium-connect) Security · 4 CVEs

How to fix

Update netty-common from 4.1.51.Final to 4.1.115.Final or later in openlmis/debezium-connect. If the 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-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 4 known vulnerabilities in netty-handler@4.1.51.Final (openlmis/debezium-connect) Security · 4 CVEs

How to fix

Update netty-handler from 4.1.51.Final to 4.1.59.Final or later in openlmis/debezium-connect. If the 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 4 known vulnerabilities in openldap@2.4.44-21.el7_6 (openlmis/debezium-connect) Security · 4 CVEs

How to fix

Update openldap from 2.4.44-21.el7_6 to 2.4.44-22.el7 or later in openlmis/debezium-connect. If the 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.44-22.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-2020-12243 fixed in 2.4.44-22.el7
  • Medium CVE-2020-25692 fixed in 2.4.44-23.el7_9
  • Medium CVE-2020-25709 fixed in 2.4.44-25.el7_9
  • Medium CVE-2020-25710 fixed in 2.4.44-25.el7_9
Medium 4 known vulnerabilities in requests@2.21.0 (openlmis/dev:5.1) Security · 4 CVEs

How to fix

Update requests from 2.21.0 to 2.33.0 or later in openlmis/dev:5.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.33.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-25645 fixed in 2.33.0
  • Medium CVE-2024-47081 fixed in 2.32.4
  • Medium CVE-2024-35195 fixed in 2.32.0
  • Medium CVE-2023-32681 fixed in 2.31.0
Medium 4 known vulnerabilities in dbus@1.12.20-2 (openlmis/postgres:12-debezium) Security · 4 CVEs

How to fix

Update dbus from 1.12.20-2 to 1.12.24-0+deb11u1 or later in openlmis/postgres:12-debezium. If the 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.12.24-0+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2022-42010 fixed in 1.12.24-0+deb11u1
  • Medium CVE-2022-42011 fixed in 1.12.24-0+deb11u1
  • Medium CVE-2022-42012 fixed in 1.12.24-0+deb11u1
  • Medium CVE-2023-34969 fixed in 1.12.28-0+deb11u1
Medium 4 known vulnerabilities in shadow@1%3A4.8.1-1 (openlmis/postgres:12-debezium) Security · 4 CVEs

How to fix

Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1:4.8.1-1+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-4641 fixed in 1:4.8.1-1+deb11u1
  • Low CVE-2007-5686 fixed in no fix yet
  • Low CVE-2013-4235 fixed in no fix yet
  • Low CVE-2023-29383 fixed in 1:4.8.1-1+deb11u1
Medium 4 known vulnerabilities in requests@2.28.1 (openlmis/scalyr) Security · 4 CVEs

How to fix

Update requests from 2.28.1 to 2.33.0 or later in openlmis/scalyr. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.33.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-25645 fixed in 2.33.0
  • Medium CVE-2024-47081 fixed in 2.32.4
  • Medium CVE-2024-35195 fixed in 2.32.0
  • Medium CVE-2023-32681 fixed in 2.31.0
Medium 3 known vulnerabilities in shadow@1%3A4.13%2Bdfsg1-1 (driesva/proftpd) Security · 3 CVEs

How to fix

Update shadow from 1%3A4.13%2Bdfsg1-1 to 1:4.13+dfsg1-1+deb12u1 or later in driesva/proftpd. If the 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.13+dfsg1-1+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-4641 fixed in 1:4.13+dfsg1-1+deb12u1
  • Low CVE-2007-5686 fixed in no fix yet
  • Low CVE-2023-29383 fixed in 1:4.13+dfsg1-1+deb12u1
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1.2 (driesva/proftpd) Security · 3 CVEs

How to fix

Update tar from 1.34%2Bdfsg-1.2 to 1.34+dfsg-1.2+deb12u1 or later in driesva/proftpd. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.34+dfsg-1.2+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-39804 fixed in 1.34+dfsg-1.2+deb12u1
  • Low CVE-2005-2541 fixed in no fix yet
  • Low CVE-2022-48303 fixed in 1.34+dfsg-1.2+deb12u1
Medium 3 known vulnerabilities in expat@2.1.0-7ubuntu0.16.04.2 (openlmis/bmp) Security · 3 CVEs

How to fix

Update expat from 2.1.0-7ubuntu0.16.04.2 to 2.1.0-7ubuntu0.16.04.3 or later in openlmis/bmp. If the 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-7ubuntu0.16.04.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-2017-9233 fixed in 2.1.0-7ubuntu0.16.04.3
  • Medium CVE-2019-15903 fixed in 2.1.0-7ubuntu0.16.04.5
  • Low CVE-2018-20843 fixed in 2.1.0-7ubuntu0.16.04.4
Medium 3 known vulnerabilities in guava@20.0 (openlmis/bmp) Security · 3 CVEs

How to fix

Update guava from 20.0 to 32.0.0-android or later in openlmis/bmp. If the 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 libtasn1-6@4.7-3ubuntu0.16.04.1 (openlmis/bmp) Security · 3 CVEs

How to fix

Update libtasn1-6 from 4.7-3ubuntu0.16.04.1 to 4.7-3ubuntu0.16.04.3 or later in openlmis/bmp. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.7-3ubuntu0.16.04.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2018-6003 fixed in 4.7-3ubuntu0.16.04.3
  • Medium CVE-2017-6891 fixed in 4.7-3ubuntu0.16.04.2
  • Low CVE-2017-10790 fixed in 4.7-3ubuntu0.16.04.3
Medium 3 known vulnerabilities in kafka-clients@2.7.0 (openlmis/debezium-connect) Security · 3 CVEs

How to fix

Update kafka-clients from 2.7.0 to 3.9.2 or later in openlmis/debezium-connect. If the 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.9.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-2026-33558 fixed in 3.9.2
  • Medium CVE-2021-38153 fixed in 2.7.2
  • Medium CVE-2024-31141 fixed in 3.7.1
Medium 3 known vulnerabilities in lcms2@2.12~rc1-2 (openlmis/postgres:12-debezium) Security · 3 CVEs

How to fix

Update lcms2 from 2.12~rc1-2 to 2.12~rc1-2+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.12~rc1-2+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-41254 fixed in 2.12~rc1-2+deb11u1
  • Low CVE-2025-29069 fixed in no fix yet
  • Low CVE-2025-29070 fixed in no fix yet
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (openlmis/postgres:12-debezium) Security · 3 CVEs

How to fix

Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.34+dfsg-1+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-39804 fixed in 1.34+dfsg-1+deb11u1
  • Low CVE-2005-2541 fixed in no fix yet
  • Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1

and 69 more groups with 95 findings

Low 156

Low 102 known vulnerabilities in hdf5@1.10.6%2Brepack-4%2Bdeb11u1 (openlmis/postgres:12-debezium) Security · 102 CVEs

How to fix

No fixed version of hdf5 is available yet. Check whether openlmis/postgres:12-debezium needs hdf5 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-17507 fixed in no fix yet
  • Low CVE-2018-13869 fixed in no fix yet
  • Low CVE-2018-13870 fixed in no fix yet
  • Low CVE-2018-14031 fixed in no fix yet
  • Low CVE-2018-14033 fixed in no fix yet
  • Low CVE-2018-14034 fixed in no fix yet
  • Low CVE-2018-14035 fixed in no fix yet
  • Low CVE-2018-14460 fixed in no fix yet
  • Low CVE-2018-15671 fixed in no fix yet
  • Low CVE-2018-16438 fixed in no fix yet
  • Low CVE-2018-17432 fixed in no fix yet
  • Low CVE-2018-17433 fixed in no fix yet
  • Low CVE-2018-17435 fixed in no fix yet
  • Low CVE-2018-17436 fixed in no fix yet
  • Low CVE-2018-17439 fixed in no fix yet
  • Low CVE-2019-8396 fixed in no fix yet
  • Low CVE-2019-8397 fixed in no fix yet
  • Low CVE-2019-8398 fixed in no fix yet
  • Low CVE-2019-9151 fixed in no fix yet
  • Low CVE-2019-9152 fixed in no fix yet
  • and 82 more
Low 6 known vulnerabilities in util-linux@2.38.1-5%2Bb1 (driesva/proftpd) Security · 6 CVEs

How to fix

No fixed version of util-linux is available yet. Check whether driesva/proftpd needs util-linux at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2022-0563 fixed in no fix yet
  • Low CVE-2022-0563 fixed in no fix yet
  • Low CVE-2025-14104 fixed in no fix yet
  • Low CVE-2025-14104 fixed in no fix yet
  • Low CVE-2024-28085 fixed in 2.38.1-5+deb12u1
  • Low CVE-2024-28085 fixed in 2.38.1-5+deb12u1
Low 5 known vulnerabilities in pcre3@2%3A8.39-13 (openlmis/postgres:12-debezium) Security · 5 CVEs

How to fix

No fixed version of pcre3 is available yet. Check whether openlmis/postgres:12-debezium needs pcre3 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2017-11164 fixed in no fix yet
  • Low CVE-2017-16231 fixed in no fix yet
  • Low CVE-2017-7245 fixed in no fix yet
  • Low CVE-2017-7246 fixed in no fix yet
  • Low CVE-2019-20838 fixed in no fix yet
Low 4 known vulnerabilities in unzip@6.0-20ubuntu1 (openlmis/bmp) Security · 4 CVEs

How to fix

Update unzip from 6.0-20ubuntu1 to 6.0-20ubuntu1.1 or later in openlmis/bmp. If the 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-20ubuntu1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2019-13232 fixed in 6.0-20ubuntu1.1
  • Low CVE-2014-9913 fixed in 6.0-20ubuntu1.1
  • Low CVE-2016-9844 fixed in 6.0-20ubuntu1.1
  • Low CVE-2018-1000035 fixed in 6.0-20ubuntu1.1
Low 4 known vulnerabilities in zlib@1%3A1.2.8.dfsg-2ubuntu4 (openlmis/bmp) Security · 4 CVEs

How to fix

Update zlib from 1%3A1.2.8.dfsg-2ubuntu4 to 1:1.2.8.dfsg-2ubuntu4.3 or later in openlmis/bmp. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1:1.2.8.dfsg-2ubuntu4.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2016-9840 fixed in 1:1.2.8.dfsg-2ubuntu4.3
  • Low CVE-2016-9842 fixed in 1:1.2.8.dfsg-2ubuntu4.3
  • Low CVE-2016-9841 fixed in 1:1.2.8.dfsg-2ubuntu4.3
  • Low CVE-2016-9843 fixed in 1:1.2.8.dfsg-2ubuntu4.3
Low 4 known vulnerabilities in libsepol@3.1-1 (openlmis/postgres:12-debezium) Security · 4 CVEs

How to fix

Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in openlmis/postgres:12-debezium. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1-1+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2021-36084 fixed in 3.1-1+deb11u1
  • Low CVE-2021-36085 fixed in 3.1-1+deb11u1
  • Low CVE-2021-36086 fixed in 3.1-1+deb11u1
  • Low CVE-2021-36087 fixed in 3.1-1+deb11u1
Low 3 known vulnerabilities in libgcrypt20@1.10.1-3 (driesva/proftpd) Security · 3 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether driesva/proftpd needs libgcrypt20 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2018-6829 fixed in no fix yet
  • Low CVE-2024-2236 fixed in no fix yet
  • Low CVE-2026-41989 fixed in no fix yet
Low 2 known vulnerabilities in coreutils@9.1-1 (driesva/proftpd) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether driesva/proftpd needs coreutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2017-18018 fixed in no fix yet
  • Low CVE-2025-5278 fixed in no fix yet
Low 2 known vulnerabilities in gcc-12@12.2.0-14 (driesva/proftpd) Security · 2 CVEs

How to fix

No fixed version of gcc-12 is available yet. Check whether driesva/proftpd needs gcc-12 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-27943 fixed in no fix yet
  • Low CVE-2023-4039 fixed in 12.2.0-14+deb12u1
Low 2 known vulnerabilities in tar@1.28-2.1ubuntu0.1 (openlmis/bmp) Security · 2 CVEs

How to fix

Update tar from 1.28-2.1ubuntu0.1 to 1.28-2.1ubuntu0.2 or later in openlmis/bmp. If the 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.28-2.1ubuntu0.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2018-20482 fixed in 1.28-2.1ubuntu0.2
  • Low CVE-2019-9923 fixed in 1.28-2.1ubuntu0.2
Low 2 known vulnerabilities in coreutils@8.22-24.el7 (openlmis/debezium-connect) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether openlmis/debezium-connect needs coreutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2015-4041 fixed in no fix yet
  • Low CVE-2015-4042 fixed in no fix yet
Low 2 known vulnerabilities in gcc@4.8.5-39.el7 (openlmis/debezium-connect) Security · 2 CVEs

How to fix

No fixed version of gcc is available yet. Check whether openlmis/debezium-connect needs gcc 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-2020-35536 fixed in no fix yet
  • Low CVE-2020-35537 fixed in no fix yet
Low 2 known vulnerabilities in coreutils@8.32-4%2Bb1 (openlmis/postgres:12-debezium) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether openlmis/postgres:12-debezium needs coreutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2017-18018 fixed in no fix yet
  • Low CVE-2025-5278 fixed in no fix yet
Low 2 known vulnerabilities in libgcrypt20@1.8.7-6 (openlmis/postgres:12-debezium) Security · 2 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether openlmis/postgres:12-debezium needs libgcrypt20 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2018-6829 fixed in no fix yet
  • Low CVE-2024-2236 fixed in no fix yet
Low 1 known vulnerability in apt@2.6.1 (driesva/proftpd) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether driesva/proftpd needs apt at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2011-3374 fixed in no fix yet
Low 1 known vulnerability in hiredis@0.14.1-3 (driesva/proftpd) Security · 1 CVE

How to fix

No fixed version of hiredis is available yet. Check whether driesva/proftpd needs hiredis 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-29479 fixed in no fix yet
Low 1 known vulnerability in sed@4.9-1 (driesva/proftpd) Security · 1 CVE

How to fix

Update sed from 4.9-1 to 4.9-1+deb12u1 or later in driesva/proftpd. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.9-1+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2026-5958 fixed in 4.9-1+deb12u1
Low 1 known vulnerability in xz-utils@5.4.1-0.2 (driesva/proftpd) Security · 1 CVE

How to fix

Update xz-utils from 5.4.1-0.2 to 5.4.1-1 or later in driesva/proftpd. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.4.1-1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2025-31115 fixed in 5.4.1-1
Low 1 known vulnerability in libpng@1.2.54-1ubuntu1 (openlmis/bmp) Security · 1 CVE

How to fix

Update libpng from 1.2.54-1ubuntu1 to 1.2.54-1ubuntu1.1 or later in openlmis/bmp. If the 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.54-1ubuntu1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2016-10087 fixed in 1.2.54-1ubuntu1.1
Low 1 known vulnerability in netty-handler-proxy@4.1.51.Final (openlmis/debezium-connect) Security · 1 CVE

How to fix

Update netty-handler-proxy from 4.1.51.Final to 4.1.133.Final or later in openlmis/debezium-connect. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.133.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2026-42578 fixed in 4.1.133.Final
Low 1 known vulnerability in chownr@1.0.1 (openlmis/dev:5.1) Security · 1 CVE

How to fix

Update chownr from 1.0.1 to 1.1.0 or later in openlmis/dev:5.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.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-2017-18869 fixed in 1.1.0
Low 1 known vulnerability in rhino@1.7.10 (openlmis/dev:5.1) Security · 1 CVE

How to fix

Update rhino from 1.7.10 to 1.7.14.1 or later in openlmis/dev:5.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.7.14.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low CVE-2025-66453 fixed in 1.7.14.1
Low 1 known vulnerability in apt@2.2.4 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether openlmis/postgres:12-debezium needs apt at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2011-3374 fixed in no fix yet
Low 1 known vulnerability in gcc-10@10.2.1-6 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of gcc-10 is available yet. Check whether openlmis/postgres:12-debezium needs gcc-10 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2023-4039 fixed in no fix yet
Low 1 known vulnerability in gcc-9@9.3.0-22 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of gcc-9 is available yet. Check whether openlmis/postgres:12-debezium needs gcc-9 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2023-4039 fixed in no fix yet
Low 1 known vulnerability in jbigkit@2.1-3.1 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of jbigkit is available yet. Check whether openlmis/postgres:12-debezium needs jbigkit 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-9937 fixed in no fix yet
Low 1 known vulnerability in software-properties@0.96.20.2-2.1 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of software-properties is available yet. Check whether openlmis/postgres:12-debezium needs software-properties 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-2020-15709 fixed in no fix yet
Low 1 known vulnerability in unixodbc@2.3.6-0.1 (openlmis/postgres:12-debezium) Security · 1 CVE

How to fix

No fixed version of unixodbc is available yet. Check whether openlmis/postgres:12-debezium needs unixodbc 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-1013 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 21 May 2026; it may have changed since.

Scan your own repository

InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.