InfraScan Cloud

Repository scan

openhim-console

jembi/openhim-console · branch master · scanned 22 Apr 2026

COverall
CSecurity
–Reliability · N/A
ACost
232findings · 0 critical, 124 high
—no cost findings with a savings estimate

High 212

High 114 known vulnerabilities in stdlib@1.13.10 (mongo:4.0) Security · 114 CVEs

How to fix

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

Vulnerabilities

  • High CVE-2021-33195 fixed in 1.15.13
  • High CVE-2023-24539 fixed in 1.19.9
  • High CVE-2023-29400 fixed in 1.19.9
  • High CVE-2020-16845 fixed in 1.13.15
  • High CVE-2021-27918 fixed in 1.15.9
  • High CVE-2021-33196 fixed in 1.15.13
  • High CVE-2021-33198 fixed in 1.15.13
  • 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
  • and 94 more
High 11 known vulnerabilities in openssl@3.0.15-r1 (jembi/openhim-core:latest) Security · 11 CVEs

How to fix

Update openssl from 3.0.15-r1 to 3.0.19-r0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.19-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-69419 fixed in 3.0.19-r0
  • High CVE-2025-69420 fixed in 3.0.19-r0
  • High CVE-2025-69421 fixed in 3.0.19-r0
  • High CVE-2025-9230 fixed in 3.0.19-r0
  • High CVE-2025-15467 fixed in 3.0.19-r0
  • Medium CVE-2025-69418 fixed in 3.0.19-r0
  • Medium CVE-2024-13176 fixed in 3.0.19-r0
  • Medium CVE-2025-68160 fixed in 3.0.19-r0
  • Medium CVE-2026-22796 fixed in 3.0.19-r0
  • Medium CVE-2026-22795 fixed in 3.0.19-r0
  • Medium CVE-2025-9232 fixed in 3.0.19-r0
High 10 known vulnerabilities in curl@8.17.0-r1 (harbor.jembidev.org/platform/openhim-console:latest) Security · 10 CVEs

How to fix

No fixed version of curl is available yet. Check whether harbor.jembidev.org/platform/openhim-console:latest needs curl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-3805 fixed in no fix yet
  • Medium CVE-2025-14524 fixed in no fix yet
  • Medium CVE-2025-14819 fixed in no fix yet
  • Medium CVE-2025-15079 fixed in no fix yet
  • Medium CVE-2026-3783 fixed in no fix yet
  • Medium CVE-2025-13034 fixed in no fix yet
  • Medium CVE-2025-14017 fixed in no fix yet
  • Medium CVE-2026-1965 fixed in no fix yet
  • Medium CVE-2026-3784 fixed in no fix yet
  • Low CVE-2025-15224 fixed in no fix yet
High 8 known vulnerabilities in handlebars@4.7.8 (jembi/openhim-core:latest) Security · 8 CVEs

How to fix

Update handlebars from 4.7.8 to 4.7.9 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.7.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-2026-33939 fixed in 4.7.9
  • High CVE-2026-33938 fixed in 4.7.9
  • High CVE-2026-33940 fixed in 4.7.9
  • High CVE-2026-33941 fixed in 4.7.9
  • High CVE-2026-33937 fixed in 4.7.9
  • Medium CVE-2026-33916 fixed in 4.7.9
  • Medium GHSA-7rx3-28cr-v5wh fixed in 4.7.9
  • Low GHSA-442j-39wm-28r2 fixed in 4.7.9
High 7 known vulnerabilities in tar@4.4.19 (jembi/openhim-core:latest) Security · 7 CVEs

How to fix

Update tar from 4.4.19 to 7.5.8 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 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-23745 fixed in 7.5.3
  • High CVE-2026-24842 fixed in 7.5.7
  • High CVE-2026-29786 fixed in 7.5.10
  • High CVE-2026-31802 fixed in 7.5.11
  • High CVE-2026-23950 fixed in 7.5.4
  • Medium CVE-2024-28863 fixed in 6.2.1
High 6 known vulnerabilities in axios@0.21.4 (jembi/openhim-core:latest) Security · 6 CVEs

How to fix

Update axios from 0.21.4 to 1.12.0, or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.12.0,); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-58754 fixed in 1.12.0,
  • High CVE-2026-25639 fixed in 1.13.5
  • High CVE-2025-27152 fixed in 1.8.2
  • Medium CVE-2026-40175 fixed in 0.31.0
  • Medium CVE-2025-62718 fixed in 0.31.0
  • Medium CVE-2023-45857 fixed in 0.28.0
High 5 known vulnerabilities in openssl@3.5.5-r0 (harbor.jembidev.org/platform/openhim-console:latest) Security · 5 CVEs

How to fix

Update openssl from 3.5.5-r0 to 3.5.6-r0 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.5.6-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-2673 fixed in 3.5.6-r0
  • High CVE-2026-28388 fixed in 3.5.6-r0
  • High CVE-2026-28389 fixed in 3.5.6-r0
  • High CVE-2026-28390 fixed in 3.5.6-r0
  • High CVE-2026-31790 fixed in 3.5.6-r0
High 5 known vulnerabilities in fast-xml-parser@4.2.5 (jembi/openhim-core:latest) Security · 5 CVEs

How to fix

Update fast-xml-parser from 4.2.5 to 5.3.6 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.3.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-2026-26278 fixed in 5.3.6
  • High CVE-2026-33036 fixed in 5.5.6
  • High CVE-2026-25896 fixed in 5.3.5
  • Medium CVE-2026-33349 fixed in 5.5.7
  • Low CVE-2026-27942 fixed in 5.3.8
High 4 known vulnerabilities in expat@2.7.4-r0 (harbor.jembidev.org/platform/openhim-console:latest) Security · 4 CVEs

How to fix

Update expat from 2.7.4-r0 to 2.7.5-r0 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.5-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-2026-32767 fixed in 2.7.5-r0
  • Medium CVE-2026-32776 fixed in 2.7.5-r0
  • Medium CVE-2026-32777 fixed in 2.7.5-r0
  • Low CVE-2026-32778 fixed in 2.7.5-r0
High 4 known vulnerabilities in koa@2.15.0 (jembi/openhim-core:latest) Security · 4 CVEs

How to fix

Update koa from 2.15.0 to 2.16.4 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.16.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-27959 fixed in 2.16.4
  • High CVE-2025-25200 fixed in 2.15.4
  • Medium CVE-2025-32379 fixed in 2.16.1
  • Low CVE-2025-8129 fixed in 3.0.1
High 4 known vulnerabilities in nodemailer@6.9.12 (jembi/openhim-core:latest) Security · 4 CVEs

How to fix

Update nodemailer from 6.9.12 to 7.0.11 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.0.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

  • High CVE-2025-14874 fixed in 7.0.11
  • Medium GHSA-vvjj-xcjg-gr5g fixed in 8.0.5
  • Medium CVE-2025-13033 fixed in 7.0.7
  • Low GHSA-c7w3-x93f-qmm8 fixed in 8.0.4
High 3 known vulnerabilities in libpng@1.6.55-r0 (harbor.jembidev.org/platform/openhim-console:latest) Security · 3 CVEs

How to fix

Update libpng from 1.6.55-r0 to 1.6.56-r0 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.6.56-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-2026-33416 fixed in 1.6.56-r0
  • High CVE-2026-33636 fixed in 1.6.56-r0
  • Medium CVE-2026-34757 fixed in 1.6.57-r0
High 3 known vulnerabilities in lodash@4.17.21 (jembi/openhim-core:latest) Security · 3 CVEs

How to fix

Update lodash from 4.17.21 to 4.18.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-4800 fixed in 4.18.0
  • Medium CVE-2026-2950 fixed in 4.18.0
  • Medium CVE-2025-13465 fixed in 4.17.23
High 3 known vulnerabilities in minimatch@3.1.2 (jembi/openhim-core:latest) Security · 3 CVEs

How to fix

Update minimatch from 3.1.2 to 3.1.3 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-27903 fixed in 3.1.3
  • High CVE-2026-27904 fixed in 3.1.4
  • High CVE-2026-26996 fixed in 10.2.1
High 2 known vulnerabilities in musl@1.2.5-r21 (harbor.jembidev.org/platform/openhim-console:latest) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r21 to 1.2.5-r23 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.5-r23); if 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-40200 fixed in 1.2.5-r23
  • Medium CVE-2026-6042 fixed in 1.2.5-r22
High 2 known vulnerabilities in ansi-regex@4.1.0 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update ansi-regex from 4.1.0 to 4.1.1 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.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

  • High CVE-2021-3807 fixed in 4.1.1
  • High CVE-2021-3807 fixed in 3.0.1
High 2 known vulnerabilities in braces@3.0.2 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update braces from 3.0.2 to 3.0.3 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-4068 fixed in 3.0.3
  • High CVE-2024-4068 fixed in 3.0.3
High 2 known vulnerabilities in form-data@2.3.3 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update form-data from 2.3.3 to 2.5.4 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.5.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-7783 fixed in 2.5.4
  • High CVE-2025-7783 fixed in 3.0.4
High 2 known vulnerabilities in ip@1.1.5 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

No fixed version of ip is available yet. Check whether jembi/openhim-core:latest needs ip 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-2024-29415 fixed in no fix yet
  • Low CVE-2023-42282 fixed in 1.1.9
High 2 known vulnerabilities in mongoose@6.12.7 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update mongoose from 6.12.7 to 6.13.5 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.13.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-53900 fixed in 6.13.5
  • High CVE-2025-23061 fixed in 6.13.6
High 2 known vulnerabilities in picomatch@2.3.1 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update picomatch from 2.3.1 to 2.3.2 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.3.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33671 fixed in 2.3.2
  • Medium CVE-2026-33672 fixed in 2.3.2
High 1 known vulnerability in nghttp2@1.68.0-r0 (harbor.jembidev.org/platform/openhim-console:latest) Security · 1 CVE

How to fix

No fixed version of nghttp2 is available yet. Check whether harbor.jembidev.org/platform/openhim-console:latest needs nghttp2 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-27135 fixed in no fix yet
High 1 known vulnerability in async@1.5.2 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update async from 1.5.2 to 2.6.4, or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.6.4,); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-43138 fixed in 2.6.4,
High 1 known vulnerability in cross-spawn@5.1.0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update cross-spawn from 5.1.0 to 6.0.6 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.0.6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-21538 fixed in 6.0.6
High 1 known vulnerability in execa@0.7.0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update execa from 0.7.0 to 2.0.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High GMS-2020-2 fixed in 2.0.0
High 1 known vulnerability in glob-parent@3.1.0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update glob-parent from 3.1.0 to 5.1.2 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.1.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2020-28469 fixed in 5.1.2
High 1 known vulnerability in http-cache-semantics@3.8.1 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update http-cache-semantics from 3.8.1 to 4.1.1 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.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

  • High CVE-2022-25881 fixed in 4.1.1
High 1 known vulnerability in jws@3.2.2 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update jws from 3.2.2 to 3.2.3 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.2.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-65945 fixed in 3.2.3
High 1 known vulnerability in musl@1.2.3-r5 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update musl from 1.2.3-r5 to 1.2.3-r6 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.3-r6); if 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-26519 fixed in 1.2.3-r6
High 1 known vulnerability in path-to-regexp@1.8.0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update path-to-regexp from 1.8.0 to 1.9.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.9.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-45296 fixed in 1.9.0
High 1 known vulnerability in semver@5.7.1 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update semver from 5.7.1 to 5.7.2 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.7.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-2022-25883 fixed in 5.7.2
High 1 known vulnerability in xmldom@0.8.10 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update xmldom from 0.8.10 to 0.8.12 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.8.12); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-34601 fixed in 0.8.12

Medium 18

Medium 3 known vulnerabilities in qs@6.12.0 (jembi/openhim-core:latest) Security · 3 CVEs

How to fix

Update qs from 6.12.0 to 6.14.1 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.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

  • Medium CVE-2025-15284 fixed in 6.14.1
  • Medium CVE-2025-15284 fixed in 6.14.1
  • Low CVE-2026-2391 fixed in 6.14.2
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (harbor.jembidev.org/platform/openhim-console:latest) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.3.2-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 2 known vulnerabilities in brace-expansion@1.1.11 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update brace-expansion from 1.1.11 to 5.0.5 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.0.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-2026-33750 fixed in 5.0.5
  • Low CVE-2025-5889 fixed in 1.1.12
Medium 2 known vulnerabilities in follow-redirects@1.15.5 (jembi/openhim-core:latest) Security · 2 CVEs

How to fix

Update follow-redirects from 1.15.5 to 1.15.6 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.15.6); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2024-28849 fixed in 1.15.6
  • Medium GHSA-r4q5-vmmm-2653 fixed in 1.16.0
Medium 1 known vulnerability in busybox@1.37.0-r30 (harbor.jembidev.org/platform/openhim-console:latest) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether harbor.jembidev.org/platform/openhim-console:latest needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
Medium 1 known vulnerability in util-linux@2.41.2-r0 (harbor.jembidev.org/platform/openhim-console:latest) Security · 1 CVE

How to fix

Update util-linux from 2.41.2-r0 to 2.41.4-r0 or later in harbor.jembidev.org/platform/openhim-console:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.41.4-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-27456 fixed in 2.41.4-r0
Medium 1 known vulnerability in ajv@6.12.6 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update ajv from 6.12.6 to 8.18.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2025-69873 fixed in 8.18.0
Medium 1 known vulnerability in gcc@12.2.1_git20220924-r4 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

No fixed version of gcc is available yet. Check whether jembi/openhim-core:latest 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

  • Medium CVE-2023-4039 fixed in no fix yet
Medium 1 known vulnerability in got@6.7.1 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update got from 6.7.1 to 11.8.5 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 11.8.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-2022-33987 fixed in 11.8.5
Medium 1 known vulnerability in micromatch@3.1.10 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update micromatch from 3.1.10 to 4.0.8 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.0.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2024-4067 fixed in 4.0.8
Medium 1 known vulnerability in request@2.88.2 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

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

Vulnerabilities

  • Medium CVE-2023-28155 fixed in no fix yet
Medium 1 known vulnerability in tough-cookie@2.5.0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update tough-cookie from 2.5.0 to 4.1.3 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-26136 fixed in 4.1.3
Medium 1 known vulnerability in zlib@1.2.13-r0 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

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

Vulnerabilities

  • Medium CVE-2023-6992 fixed in no fix yet

Low 2

Low 1 known vulnerability in config-resolver@2.1.5 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update config-resolver from 2.1.5 to 4.4.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.4.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Low GHSA-6475-r3vj-m8vf fixed in 4.4.0
Low 1 known vulnerability in cookie@0.4.2 (jembi/openhim-core:latest) Security · 1 CVE

How to fix

Update cookie from 0.4.2 to 0.7.0 or later in jembi/openhim-core:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.7.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-2024-47764 fixed in 0.7.0

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 22 Apr 2026; it may have changed since.

Scan your own repository

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