InfraScan Cloud

Repository scan

knowledge-platform

pallakartheekreddy/knowledge-platform · branch main · scanned 31 Mar 2026 · 30 resources

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

High 304

High 107 known vulnerabilities in stdlib@1.13.10 (redis:6.0.8) Security · 107 CVEs

How to fix

Update stdlib from 1.13.10 to 1.15.13 or later in redis:6.0.8. If the 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 87 more
High 20 known vulnerabilities in protobuf-java@3.7.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 20 CVEs

How to fix

Update protobuf-java from 3.7.1 to 3.16.1 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.19.6
  • High CVE-2022-3509 fixed in 3.16.3
  • 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-2022-3510 fixed in 3.19.6
  • 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
  • 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
  • Medium CVE-2022-3171 fixed in 3.19.6
  • Medium CVE-2022-3171 fixed in 3.16.3
High 19 known vulnerabilities in stdlib@1.24.6 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 19 CVEs

How to fix

Update stdlib from 1.24.6 to 1.24.9 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.24.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-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • Medium CVE-2025-47912 fixed in 1.24.8
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-58186 fixed in 1.24.8
  • Medium CVE-2025-58189 fixed in 1.24.8
  • Medium CVE-2025-61724 fixed in 1.24.8
  • Medium CVE-2025-61730 fixed in 1.24.12
  • Medium CVE-2026-27142 fixed in 1.25.8
  • Medium CVE-2025-61727 fixed in 1.24.11
  • Medium CVE-2025-61728 fixed in 1.24.12
  • Low CVE-2026-27139 fixed in 1.25.8
High 13 known vulnerabilities in elasticsearch@7.17.8 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 13 CVEs

How to fix

Update elasticsearch from 7.17.8 to 7.17.13 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.17.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-31418 fixed in 7.17.13
  • Medium CVE-2023-31417 fixed in 7.17.13
  • Medium CVE-2023-49921 fixed in 7.17.16
  • Medium CVE-2024-23450 fixed in 7.17.19
  • Medium CVE-2024-52981 fixed in 7.17.24
  • Medium CVE-2025-37727 fixed in 8.18.8
  • Medium CVE-2023-31419 fixed in 7.17.13
  • Medium CVE-2023-46673 fixed in 7.17.14
  • Medium CVE-2024-43709 fixed in 7.17.21
  • Medium CVE-2024-52979 fixed in 7.17.25
  • Medium CVE-2024-52980 fixed in 8.15.1
  • Medium CVE-2025-37731 fixed in 8.19.8
  • Medium CVE-2024-23444 fixed in 7.17.23
High 12 known vulnerabilities in netty-codec-http@4.1.112.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 12 CVEs

How to fix

Update netty-codec-http from 4.1.112.Final to 4.1.132.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.132.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33870 fixed in 4.1.132.Final
  • High CVE-2026-33870 fixed in 4.1.132.Final
  • High CVE-2026-33870 fixed in 4.1.132.Final
  • Medium CVE-2024-29025 fixed in 4.1.108.Final
  • Medium CVE-2022-24823 fixed in 4.1.77.Final
  • Medium CVE-2021-43797 fixed in 4.1.71.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
High 12 known vulnerabilities in openssl@3.0.17-1~deb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 12 CVEs

How to fix

Update openssl from 3.0.17-1~deb12u1 to 3.0.18-1~deb12u2 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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-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
  • Medium CVE-2025-69418 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2025-68160 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2026-22796 fixed in 3.0.18-1~deb12u2
  • Medium CVE-2026-22795 fixed in 3.0.18-1~deb12u2
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2025-15467 fixed in 3.0.18-1~deb12u2
  • Low CVE-2025-27587 fixed in no fix yet
  • Low CVE-2025-9232 fixed in 3.0.17-1~deb12u3
High 11 known vulnerabilities in jackson-databind@2.10.4 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 11 CVEs

How to fix

Update jackson-databind from 2.10.4 to 2.10.5.1 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.13.2.1
  • High CVE-2021-46877 fixed in 2.12.6
  • High CVE-2021-46877 fixed in 2.13.1
  • High CVE-2022-42003 fixed in 2.12.7.1
  • High CVE-2022-42003 fixed in 2.13.4.2
  • High CVE-2022-42003 fixed in 2.13.4.2
  • High CVE-2022-42004 fixed in 2.12.7.1
  • High CVE-2022-42004 fixed in 2.13.4
  • High CVE-2022-42004 fixed in 2.13.4
High 10 known vulnerabilities in jackson-core@2.10.4 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 10 CVEs

How to fix

Update jackson-core from 2.10.4 to 2.15.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.15.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-52999 fixed in 2.15.0
  • High CVE-2025-52999 fixed in 2.15.0
  • High CVE-2025-52999 fixed in 2.15.0
  • Medium CVE-2025-49128 fixed in 2.13.0
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
  • Medium GHSA-72hv-8253-57qq fixed in 2.18.6
High 9 known vulnerabilities in logback-core@1.2.9 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 9 CVEs

How to fix

Update logback-core from 1.2.9 to 1.2.13 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-6378 fixed in 1.2.13
  • Medium CVE-2024-12798 fixed in 1.3.15
  • Medium CVE-2024-12798 fixed in 1.3.15
  • Medium CVE-2025-11226 fixed in 1.5.19
  • Medium CVE-2025-11226 fixed in 1.5.19
  • Low CVE-2026-1225 fixed in 1.5.25
  • Low CVE-2026-1225 fixed in 1.5.25
  • Low CVE-2024-12801 fixed in 1.3.15
  • Low CVE-2024-12801 fixed in 1.3.15
High 8 known vulnerabilities in snakeyaml@1.26 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 8 CVEs

How to fix

Update snakeyaml from 1.26 to 1.31 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.31); if 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-25857 fixed in 1.31
  • High CVE-2022-1471 fixed in 2.0
  • High CVE-2022-1471 fixed in 2.0
  • Medium CVE-2022-38750 fixed in 1.31
  • Medium CVE-2022-38749 fixed in 1.31
  • Medium CVE-2022-38751 fixed in 1.31
  • Medium CVE-2022-38752 fixed in 1.32
  • Medium CVE-2022-41854 fixed in 1.32
High 7 known vulnerabilities in jetty-server@9.4.54.v20240208 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 7 CVEs

How to fix

Update jetty-server from 9.4.54.v20240208 to 9.4.57.v20241219 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.57.v20241219); if 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-13009 fixed in 9.4.57.v20241219
  • High CVE-2024-13009 fixed in 9.4.57.v20241219
  • Medium CVE-2023-26048 fixed in 9.4.51.v20230217
  • Medium CVE-2023-40167 fixed in 9.4.52.v20230823,
  • Medium CVE-2024-8184 fixed in 9.4.56
  • Medium CVE-2024-8184 fixed in 9.4.56
  • Low CVE-2023-26049 fixed in 9.4.51.v20230217
High 6 known vulnerabilities in zookeeper@3.9.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 6 CVEs

How to fix

Update zookeeper from 3.9.2 to 3.9.5 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2026-24281 fixed in 3.9.5
  • High CVE-2026-24281 fixed in 3.8.6
  • High CVE-2026-24308 fixed in 3.8.6
  • High CVE-2026-24308 fixed in 3.9.5
  • High CVE-2024-51504 fixed in 3.9.3
  • Medium CVE-2025-58457 fixed in 3.9.4
High 5 known vulnerabilities in hadoop-common@3.3.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 5 CVEs

How to fix

Update hadoop-common from 3.3.2 to 3.3.3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.3.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-2022-25168 fixed in 3.3.3
  • High CVE-2022-26612 fixed in 3.3.3
  • Low CVE-2024-23454 fixed in 3.4.0
  • Low CVE-2024-23454 fixed in 3.4.0
  • Low CVE-2024-23454 fixed in 3.4.0
High 5 known vulnerabilities in netty-all@4.1.58.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 5 CVEs

How to fix

Update netty-all from 4.1.58.Final to 4.1.68 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.68); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-37136 fixed in 4.1.68
  • High CVE-2022-41881 fixed in 4.1.86
  • 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
High 5 known vulnerabilities in netty-codec@4.1.66.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 5 CVEs

How to fix

Update netty-codec from 4.1.66.Final to 4.1.68.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.68.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-37136 fixed in 4.1.68.Final
  • High CVE-2021-37137 fixed in 4.1.68.Final
  • Medium CVE-2025-58057 fixed in 4.1.125.Final
  • Medium CVE-2025-58057 fixed in 4.1.125.Final
  • Medium CVE-2025-58057 fixed in 4.1.125.Final
High 4 known vulnerabilities in cassandra-all@4.0.6 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update cassandra-all from 4.0.6 to 4.0.10 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2023-30601 fixed in 4.0.10
  • High CVE-2025-23015 fixed in 4.0.16
  • Medium CVE-2025-24860 fixed in 4.0.16
  • Medium CVE-2024-27137 fixed in 4.0.15
High 4 known vulnerabilities in json-smart@2.4.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update json-smart from 2.4.2 to 2.4.4 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-31684 fixed in 2.4.4
  • High CVE-2021-31684 fixed in 1.3.3
  • High CVE-2023-1370 fixed in 2.4.9
  • High CVE-2023-1370 fixed in 2.4.9
High 4 known vulnerabilities in netty-codec-http2@4.1.108.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update netty-codec-http2 from 4.1.108.Final to 4.1.124.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.124.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-2025-55163 fixed in 4.1.124.Final
  • High CVE-2025-55163 fixed in 4.1.124.Final
  • High CVE-2026-33871 fixed in 4.1.132.Final
  • High CVE-2026-33871 fixed in 4.1.132.Final
High 4 known vulnerabilities in perl@5.36.0-7%2Bdeb12u2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update perl from 5.36.0-7%2Bdeb12u2 to 5.36.0-7+deb12u3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.36.0-7+deb12u3); if 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-31484 fixed in 5.36.0-7+deb12u3
  • Medium CVE-2025-40909 fixed in 5.36.0-7+deb12u3
  • Low CVE-2011-4116 fixed in no fix yet
  • Low CVE-2023-31486 fixed in no fix yet
High 4 known vulnerabilities in snappy-java@1.1.2.6 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update snappy-java from 1.1.2.6 to 1.1.10.1 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.10.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-34455 fixed in 1.1.10.1
  • High CVE-2023-43642 fixed in 1.1.10.4
  • Medium CVE-2023-34453 fixed in 1.1.10.1
  • Medium CVE-2023-34454 fixed in 1.1.10.1
High 3 known vulnerabilities in avro@1.7.7 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 3 CVEs

How to fix

Update avro from 1.7.7 to 1.11.3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.11.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-2023-39410 fixed in 1.11.3
  • High CVE-2024-47561 fixed in 1.11.4
  • High CVE-2024-47561 fixed in 1.11.4
High 3 known vulnerabilities in netty-handler@4.1.108.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 3 CVEs

How to fix

Update netty-handler from 4.1.108.Final to 4.1.118.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.118.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-2025-24970 fixed in 4.1.118.Final
  • High CVE-2025-24970 fixed in 4.1.118.Final
  • Medium CVE-2023-34462 fixed in 4.1.94.Final
High 3 known vulnerabilities in nimbus-jose-jwt@9.8.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 3 CVEs

How to fix

Update nimbus-jose-jwt from 9.8.1 to 9.37.2 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.37.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-2023-52428 fixed in 9.37.2
  • Medium CVE-2025-53864 fixed in 10.0.2
  • Medium CVE-2025-53864 fixed in 10.0.2
High 2 known vulnerabilities in commons-io@2.11.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update commons-io from 2.11.0 to 2.14.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.14.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-47554 fixed in 2.14.0
  • High CVE-2024-47554 fixed in 2.14.0
High 2 known vulnerabilities in glibc@2.36-9%2Bdeb12u10 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update glibc from 2.36-9%2Bdeb12u10 to 2.36-9+deb12u11 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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+deb12u11); if 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-4802 fixed in 2.36-9+deb12u11
  • Medium CVE-2025-8058 fixed in 2.36-9+deb12u13
High 2 known vulnerabilities in gnupg2@2.2.40-1.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update gnupg2 from 2.2.40-1.1 to 2.2.40-1.1+deb12u2 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.40-1.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-68973 fixed in 2.2.40-1.1+deb12u2
  • Low CVE-2022-3219 fixed in no fix yet
High 2 known vulnerabilities in http2-common@9.4.53.v20231009 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update http2-common from 9.4.53.v20231009 to 9.4.54 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.54); if 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-22201 fixed in 9.4.54
  • High CVE-2025-5115 fixed in 9.4.58
High 2 known vulnerabilities in lz4-java@1.8.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

No fixed version of lz4-java is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs lz4-java at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-66566 fixed in no fix yet
  • High CVE-2025-12183 fixed in 1.8.1
High 2 known vulnerabilities in netty-codec-smtp@4.1.112.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update netty-codec-smtp from 4.1.112.Final to 4.1.128.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.128.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-2025-59419 fixed in 4.1.128.Final
  • High CVE-2025-59419 fixed in 4.1.128.Final
High 2 known vulnerabilities in pam@1.5.2-6%2Bdeb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update pam from 1.5.2-6%2Bdeb12u1 to 1.5.2-6+deb12u2 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.5.2-6+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-6020 fixed in 1.5.2-6+deb12u2
  • Medium CVE-2024-22365 fixed in 1.5.2-6+deb12u2
High 2 known vulnerabilities in spark-core_2.12@3.3.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update spark-core_2.12 from 3.3.2 to 3.5.7 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-54920 fixed in 3.5.7
  • High CVE-2023-22946 fixed in 3.3.3
High 2 known vulnerabilities in xmlsec@2.1.4 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update xmlsec from 2.1.4 to 2.1.7 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-40690 fixed in 2.1.7
  • Medium CVE-2023-44483 fixed in 2.2.6
High 1 known vulnerability in commons-beanutils@1.9.4 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update commons-beanutils from 1.9.4 to 1.11.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.11.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-48734 fixed in 1.11.0
High 1 known vulnerability in dnsjava@2.1.7 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update dnsjava from 2.1.7 to 3.6.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.6.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-25638 fixed in 3.6.0
High 1 known vulnerability in google-oauth-client@1.31.5 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update google-oauth-client from 1.31.5 to 1.33.3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.33.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-2021-22573 fixed in 1.33.3
High 1 known vulnerability in grpc-netty-shaded@1.66.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update grpc-netty-shaded from 1.66.0 to 1.175.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.175.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-55163 fixed in 1.175.0
High 1 known vulnerability in gson@2.8.7 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update gson from 2.8.7 to 2.8.9 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-25647 fixed in 2.8.9
High 1 known vulnerability in jackson-dataformat-cbor@2.10.4 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update jackson-dataformat-cbor from 2.10.4 to 2.11.4 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.11.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-2020-28491 fixed in 2.11.4
High 1 known vulnerability in kerb-admin@1.0.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update kerb-admin from 1.0.1 to 2.0.3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2023-25613 fixed in 2.0.3
High 1 known vulnerability in logback-classic@1.2.9 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update logback-classic from 1.2.9 to 1.2.13 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2023-6378 fixed in 1.2.13

Medium 118

Medium 14 known vulnerabilities in guava@14.0.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 14 CVEs

How to fix

Update guava from 14.0.1 to 32.0.0-android or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 32.0.0-android); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2023-2976 fixed in 32.0.0-android
  • Medium CVE-2018-10237 fixed in 24.1.1-android
  • Medium CVE-2018-10237 fixed in 24.1.1-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
  • Low CVE-2020-8908 fixed in 32.0.0-android
Medium 11 known vulnerabilities in jetty-http@9.4.48.v20220622 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 11 CVEs

How to fix

Update jetty-http from 9.4.48.v20220622 to 9.4.52 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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); if 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-40167 fixed in 9.4.52
  • Medium CVE-2023-40167 fixed in 9.4.52
  • Medium CVE-2024-6763 fixed in 12.0.12
  • Medium CVE-2024-6763 fixed in 12.0.12
  • Medium CVE-2024-6763 fixed in 12.0.12
  • Medium CVE-2024-6763 fixed in 12.0.12
  • Low CVE-2022-2047 fixed in 9.4.47
  • Low CVE-2025-11143 fixed in no fix yet
  • Low CVE-2025-11143 fixed in no fix yet
  • Low CVE-2025-11143 fixed in no fix yet
  • Low CVE-2025-11143 fixed in no fix yet
Medium 7 known vulnerabilities in jetty-webapp@9.4.51.v20230217 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 7 CVEs

How to fix

Update jetty-webapp from 9.4.51.v20230217 to 9.4.52.v20230823, or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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-2023-41900 fixed in 9.4.52.v20230823,
  • Medium CVE-2023-26049 fixed in 9.4.51.v20230217,
  • Medium CVE-2023-40167 fixed in 9.4.52.v20230823,
  • Medium CVE-2023-40167 fixed in 9.4.52.v20230823,
  • Low CVE-2023-36479 fixed in 9.4.52.v20230823,
  • Low CVE-2023-36479 fixed in 9.4.52.v20230823,
Medium 7 known vulnerabilities in netty-common@4.1.112.Final (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 7 CVEs

How to fix

Update netty-common from 4.1.112.Final to 4.1.115.Final or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.115.Final); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2024-47535 fixed in 4.1.115.Final
  • Medium CVE-2024-47535 fixed in 4.1.115.Final
  • Medium CVE-2024-47535 fixed in 4.1.115.Final
  • Medium CVE-2022-24823 fixed in 4.1.77.Final
  • Medium CVE-2025-25193 fixed in 4.1.118.Final
  • Medium CVE-2025-25193 fixed in 4.1.118.Final
  • Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 6 known vulnerabilities in bcprov-jdk15on@1.64 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 6 CVEs

How to fix

Update bcprov-jdk15on from 1.64 to 1.66 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.66); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2020-15522 fixed in 1.66
  • Medium CVE-2023-33201 fixed in no fix yet
  • Medium CVE-2024-29857 fixed in 1.78
  • Medium CVE-2024-30172 fixed in 1.78
  • Medium CVE-2023-33202 fixed in no fix yet
  • Medium CVE-2024-30171 fixed in 1.78
Medium 5 known vulnerabilities in jetty-servlets@9.4.48.v20220622 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 5 CVEs

How to fix

Update jetty-servlets from 9.4.48.v20220622 to 9.4.52.v20230823, or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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-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 systemd@252.38-1~deb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 5 CVEs

How to fix

No fixed version of systemd is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs systemd 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-29111 fixed in no fix yet
  • 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
Medium 4 known vulnerabilities in bc-fips@1.0.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update bc-fips from 1.0.2 to 1.0.2.1 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.0.2.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2020-15522 fixed in 1.0.2.1
  • Medium CVE-2024-29857 fixed in 1.0.2.5
  • Medium CVE-2022-45146 fixed in 1.0.2.4
  • Medium CVE-2025-8885 fixed in 2.1.0
Medium 4 known vulnerabilities in commons-configuration2@2.1.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update commons-configuration2 from 2.1.1 to 2.10.1 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2024-29131 fixed in 2.10.1
  • Medium CVE-2024-29131 fixed in 2.10.1
  • Medium CVE-2024-29133 fixed in 2.10.1
  • Medium CVE-2024-29133 fixed in 2.10.1
Medium 4 known vulnerabilities in commons-lang3@3.9 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 4 CVEs

How to fix

Update commons-lang3 from 3.9 to 3.18.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2025-48924 fixed in 3.18.0
  • Medium CVE-2025-48924 fixed in 3.18.0
  • Medium CVE-2025-48924 fixed in 3.18.0
  • Medium CVE-2025-48924 fixed in 3.18.0
Medium 3 known vulnerabilities in gnutls28@3.7.9-2%2Bdeb12u5 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 3 CVEs

How to fix

Update gnutls28 from 3.7.9-2%2Bdeb12u5 to 3.7.9-2+deb12u6 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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+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

  • Medium CVE-2025-9820 fixed in 3.7.9-2+deb12u6
  • Medium CVE-2025-14831 fixed in 3.7.9-2+deb12u6
  • Low CVE-2011-3389 fixed in no fix yet
Medium 2 known vulnerabilities in commons-compress@1.21 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update commons-compress from 1.21 to 1.26.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.26.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2024-25710 fixed in 1.26.0
  • Medium CVE-2024-26308 fixed in 1.26.0
Medium 2 known vulnerabilities in jetty-client@9.4.48.v20220622 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update jetty-client from 9.4.48.v20220622 to 9.4.51.v20230217, or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.51.v20230217,); if 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-26049 fixed in 9.4.51.v20230217,
  • Medium CVE-2023-26049 fixed in 9.4.51.v20230217,
Medium 2 known vulnerabilities in log4j-core@2.17.1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update log4j-core from 2.17.1 to 2.25.3 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.25.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2025-68161 fixed in 2.25.3
  • Medium CVE-2025-68161 fixed in 2.25.3
Medium 2 known vulnerabilities in net@0.42.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update net from 0.42.0 to 0.45.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.45.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-47911 fixed in 0.45.0
  • Medium CVE-2025-58190 fixed in 0.45.0
Medium 2 known vulnerabilities in tar@1.34%2Bdfsg-1.2%2Bdeb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

No fixed version of tar is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs tar 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-45582 fixed in no fix yet
  • Low CVE-2005-2541 fixed in no fix yet
Medium 1 known vulnerability in bcpkix-jdk15on@1.64 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update bcpkix-jdk15on from 1.64 to 1.79 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.79); if 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-8916 fixed in 1.79
Medium 1 known vulnerability in commons-lang@2.6 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

No fixed version of commons-lang is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs commons-lang 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-48924 fixed in no fix yet
Medium 1 known vulnerability in commons-net@3.6 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update commons-net from 3.6 to 3.9.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2021-37533 fixed in 3.9.0
Medium 1 known vulnerability in httpclient@4.5.10 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update httpclient from 4.5.10 to 4.5.13 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.5.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

  • Medium CVE-2020-13956 fixed in 4.5.13
Medium 1 known vulnerability in okio@1.6.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update okio from 1.6.0 to 1.17.6 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2023-3635 fixed in 1.17.6
Medium 1 known vulnerability in spark-network-common_2.12@3.3.2 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update spark-network-common_2.12 from 3.3.2 to 3.4.4 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2025-55039 fixed in 3.4.4
Medium 1 known vulnerability in woodstox-core@5.3.0 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update woodstox-core from 5.3.0 to 5.4.0 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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-2022-40152 fixed in 5.4.0
Medium 1 known vulnerability in x-pack-core@7.17.8 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update x-pack-core from 7.17.8 to 8.19.8 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.19.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2025-68390 fixed in 8.19.8
Medium 1 known vulnerability in x-pack-security@7.17.8 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

Update x-pack-security from 7.17.8 to 8.19.9 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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.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

  • Medium CVE-2025-68384 fixed in 8.19.9
Medium Ensure storage for critical data are encrypted with Customer Managed Key Security · 1 place

Ensure storage for critical data are encrypted with Customer Managed Key

Documentation

Where

Medium Ensure Storage logging is enabled for Blob service for read requests Security · 1 place

Ensure Storage logging is enabled for Blob service for read requests

Documentation

Where

Medium Ensure AKS cluster has Azure CNI networking enabled Security · 1 place

Ensure AKS cluster has Azure CNI networking enabled

Documentation

Where

Medium Ensure VNET subnet is configured with a Network Security Group (NSG) Security · 1 place

Ensure VNET subnet is configured with a Network Security Group (NSG)

Documentation

Where

Medium Ensure storage account is configured with private endpoint Security · 1 place

Ensure storage account is configured with private endpoint

Documentation

Where

Medium Ensure soft-delete is enabled on Azure storage account Security · 1 place

Ensure soft-delete is enabled on Azure storage account

Documentation

Where

Medium Ensure storage account is not configured with Shared Key authorization Security · 1 place

Ensure storage account is not configured with Shared Key authorization

Documentation

Where

Medium Ensure storage account is configured with SAS expiration policy Security · 1 place

Ensure storage account is configured with SAS expiration policy

Documentation

Where

Medium Ensure storage account is configured without blob anonymous access Security · 1 place

Ensure storage account is configured without blob anonymous access

Documentation

Where

Medium Ensure that AKS enables private clusters Security · 1 place

Ensure that AKS enables private clusters

Documentation

Where

Medium Ensure that AKS uses Azure Policies Add-on Security · 1 place

Ensure that AKS uses Azure Policies Add-on

Documentation

Where

Medium Ensure that AKS uses disk encryption set Security · 1 place

Ensure that AKS uses disk encryption set

Documentation

Where

Medium Ensure AKS local admin account is disabled Security · 1 place

Ensure AKS local admin account is disabled

Documentation

Where

Medium Ensure Azure Kubernetes Cluster (AKS) nodes should use a minimum number of 50 pods. Security · 1 place

Ensure Azure Kubernetes Cluster (AKS) nodes should use a minimum number of 50 pods.

Documentation

Where

Medium Ensure that AKS use the Paid Sku for its SLA Security · 1 place

Ensure that AKS use the Paid Sku for its SLA

Documentation

Where

and 14 more groups with 14 findings

Low 10

Low 2 known vulnerabilities in coreutils@9.1-1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 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 jetty-xml@9.4.51.v20230217 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

Update jetty-xml from 9.4.51.v20230217 to 9.4.52.v20230823 or later in docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21. If the 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

  • Low GHSA-58qw-p7qm-5rvh fixed in 9.4.52.v20230823
  • Low GHSA-58qw-p7qm-5rvh fixed in 9.4.52.v20230823
Low 2 known vulnerabilities in libgcrypt20@1.10.1-3 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 2 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 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 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 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 commons-configuration@1.10 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

No fixed version of commons-configuration is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs commons-configuration at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2025-46392 fixed in no fix yet
Low 1 known vulnerability in gcc-12@12.2.0-14%2Bdeb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 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 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-1%2Bdeb12u1 (docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether docker.io/bitnamilegacy/janusgraph:1.1.0-debian-12-r21 needs shadow at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2007-5686 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 31 Mar 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.