InfraScan Cloud

Repository scan

opg-digideps

ministryofjustice/opg-digideps · branch main · scanned 25 Jun 2026 · 387 resources

DOverall
FSecurity
–Reliability · N/A
BCost
765findings · 0 critical, 191 high
$7.60estimated savings per month, from the code

High 438

High 157 known vulnerabilities in unknown@unknown (redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0) Security · 157 CVEs

How to fix

No fixed version of unknown is available yet. Check whether redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0 needs unknown 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-2026-42012 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-42011 fixed in no fix yet
  • High CVE-2022-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • High CVE-2022-41722 fixed in no fix yet
  • High CVE-2022-41723 fixed in no fix yet
  • High CVE-2022-41724 fixed in no fix yet
  • High CVE-2022-41725 fixed in no fix yet
  • High CVE-2023-24534 fixed in no fix yet
  • and 137 more
High 119 known vulnerabilities in unknown@unknown (postgres:14.22@sha256:eba8ddbdd837ecfbb6ca8a26d8deec68a2f9b076660102ae641dba0f371c099b) Security · 119 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:14.22@sha256:eba8ddbdd837ecfbb6ca8a26d8deec68a2f9b076660102ae641dba0f371c099b needs unknown 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-2026-42012 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-42011 fixed in no fix yet
  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-33845 fixed in no fix yet
  • High CVE-2026-33846 fixed in no fix yet
  • High CVE-2026-34180 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-4046 fixed in no fix yet
  • High CVE-2026-42009 fixed in no fix yet
  • and 99 more
High 29 known vulnerabilities in unknown@unknown (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 29 CVEs

How to fix

No fixed version of unknown is available yet. Check whether infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2021-3572 fixed in no fix yet
  • High CVE-2023-43804 fixed in no fix yet
  • High CVE-2024-6345 fixed in no fix yet
  • High CVE-2026-30922 fixed in no fix yet
  • High GHSA-6v7p-g79w-8964 fixed in no fix yet
  • High CVE-2025-47273 fixed in no fix yet
  • High CVE-2026-44431 fixed in no fix yet
  • High CVE-2021-33503 fixed in no fix yet
  • High CVE-2022-40897 fixed in no fix yet
  • High CVE-2025-66418 fixed in no fix yet
  • High CVE-2025-66471 fixed in no fix yet
  • High CVE-2026-21441 fixed in no fix yet
  • Medium CVE-2024-37891 fixed in no fix yet
  • Medium CVE-2026-25645 fixed in no fix yet
  • Medium CVE-2026-3219 fixed in no fix yet
  • Medium CVE-2024-47081 fixed in no fix yet
  • Medium CVE-2025-50181 fixed in no fix yet
  • Medium CVE-2026-6357 fixed in no fix yet
  • Medium CVE-2026-8643 fixed in no fix yet
  • Medium CVE-2024-35195 fixed in no fix yet
  • and 9 more
High 17 known vulnerabilities in expat@2.2.10-r1 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 17 CVEs

How to fix

Update expat from 2.2.10-r1 to 2.2.10-r3 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the 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-r3); if 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-r3
  • High CVE-2022-25314 fixed in 2.2.10-r4
  • High CVE-2022-43680 fixed in 2.2.10-r8
  • High CVE-2021-46143 fixed in 2.2.10-r2
  • High CVE-2022-40674 fixed in 2.2.10-r7
  • High CVE-2021-45960 fixed in 2.2.10-r2
  • High CVE-2022-22825 fixed in 2.2.10-r2
  • High CVE-2022-22826 fixed in 2.2.10-r2
  • High CVE-2022-22827 fixed in 2.2.10-r2
  • High CVE-2022-22822 fixed in 2.2.10-r2
  • High CVE-2022-22823 fixed in 2.2.10-r2
  • High CVE-2022-22824 fixed in 2.2.10-r2
  • High CVE-2022-23852 fixed in 2.2.10-r3
  • High CVE-2022-25235 fixed in 2.2.10-r4
  • High CVE-2022-25236 fixed in 2.2.10-r4
  • High CVE-2022-25315 fixed in 2.2.10-r4
  • Medium CVE-2022-25313 fixed in 2.2.10-r4
High 15 known vulnerabilities in curl@8.17.0-r1 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 15 CVEs

How to fix

Update curl from 8.17.0-r1 to 8.19.0-r0 or later in composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d. If the 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.0-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-3805 fixed in 8.19.0-r0
  • High CVE-2026-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • Medium CVE-2025-14524 fixed in 8.19.0-r0
  • Medium CVE-2025-14819 fixed in 8.19.0-r0
  • Medium CVE-2026-3783 fixed in 8.19.0-r0
  • Medium CVE-2026-6429 fixed in no fix yet
  • Medium CVE-2026-7009 fixed in no fix yet
  • Medium CVE-2026-7168 fixed in no fix yet
  • Medium CVE-2026-4873 fixed in no fix yet
  • Medium CVE-2026-6253 fixed in no fix yet
  • Medium CVE-2025-14017 fixed in 8.19.0-r0
  • Medium CVE-2026-1965 fixed in 8.19.0-r0
  • Medium CVE-2026-3784 fixed in 8.19.0-r0
  • Medium CVE-2026-5545 fixed in no fix yet
High 15 known vulnerabilities in openssl@3.5.6-r0 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d. If the 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-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-34181 fixed in 3.5.7-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 15 known vulnerabilities in openssl@3.5.6-r0 (stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e. If the 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-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-34181 fixed in 3.5.7-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 14 known vulnerabilities in stdlib@1.18.2 (redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0. If the 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.18.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-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 13 known vulnerabilities in busybox@1.32.1-r6 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 13 CVEs

How to fix

Update busybox from 1.32.1-r6 to 1.32.1-r7 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the 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.32.1-r7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2021-42378 fixed in 1.32.1-r7
  • High CVE-2021-42379 fixed in 1.32.1-r7
  • High CVE-2021-42380 fixed in 1.32.1-r7
  • High CVE-2021-42381 fixed in 1.32.1-r7
  • High CVE-2021-42382 fixed in 1.32.1-r7
  • High CVE-2021-42383 fixed in 1.32.1-r7
  • High CVE-2021-42384 fixed in 1.32.1-r7
  • High CVE-2021-42385 fixed in 1.32.1-r7
  • High CVE-2021-42386 fixed in 1.32.1-r7
  • High CVE-2022-30065 fixed in 1.32.1-r9
  • High CVE-2022-28391 fixed in 1.32.1-r8
  • Medium CVE-2021-42374 fixed in 1.32.1-r7
  • Medium CVE-2021-42375 fixed in 1.32.1-r7
High 13 known vulnerabilities in unknown@unknown (stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e) Security · 13 CVEs

How to fix

No fixed version of unknown is available yet. Check whether stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e needs unknown 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-33671 fixed in no fix yet
  • High CVE-2026-6321 fixed in no fix yet
  • High CVE-2026-6322 fixed in no fix yet
  • High CVE-2026-44665 fixed in no fix yet
  • Medium CVE-2026-33672 fixed in no fix yet
  • Medium CVE-2026-42338 fixed in no fix yet
  • Medium CVE-2026-53550 fixed in no fix yet
  • Medium CVE-2026-44664 fixed in no fix yet
  • Medium CVE-2026-41907 fixed in no fix yet
  • Medium CVE-2026-8723 fixed in no fix yet
  • Medium CVE-2026-33750 fixed in no fix yet
  • Medium CVE-2026-45149 fixed in no fix yet
  • Medium CVE-2026-53655 fixed in no fix yet
High 7 known vulnerabilities in tar@1.35-r4 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 7 CVEs

How to fix

No fixed version of tar is available yet. Check whether composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d 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

  • High CVE-2026-26960 fixed in no fix yet
  • High CVE-2018-20834 fixed in no fix yet
  • High CVE-2026-23745 fixed in no fix yet
  • High CVE-2026-29786 fixed in no fix yet
  • High CVE-2026-31802 fixed in no fix yet
  • Medium CVE-2025-45582 fixed in no fix yet
  • Medium CVE-2024-28863 fixed in no fix yet
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:14.22@sha256:eba8ddbdd837ecfbb6ca8a26d8deec68a2f9b076660102ae641dba0f371c099b) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:14.22@sha256:eba8ddbdd837ecfbb6ca8a26d8deec68a2f9b076660102ae641dba0f371c099b. If the 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.25.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-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
High 5 known vulnerabilities in openssh@10.2_p1-r0 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 5 CVEs

How to fix

No fixed version of openssh is available yet. Check whether composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d needs openssh 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-35385 fixed in no fix yet
  • Medium CVE-2026-35414 fixed in no fix yet
  • Low CVE-2026-35388 fixed in no fix yet
  • Low CVE-2026-35387 fixed in no fix yet
  • Low CVE-2026-35386 fixed in no fix yet
High 4 known vulnerabilities in openssl@1.1.1k-r0 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 4 CVEs

How to fix

Update openssl from 1.1.1k-r0 to 1.1.1l-r0 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the 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.1l-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-2021-3712 fixed in 1.1.1l-r0
  • High CVE-2022-0778 fixed in 1.1.1n-r0
  • High CVE-2021-3711 fixed in 1.1.1l-r0
  • Medium CVE-2022-2097 fixed in 1.1.1q-r0
High 2 known vulnerabilities in sqlite@3.51.2-r0 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 2 CVEs

How to fix

No fixed version of sqlite is available yet. Check whether composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d needs sqlite 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-11822 fixed in no fix yet
  • High CVE-2026-11824 fixed in no fix yet
High 2 known vulnerabilities in zlib@1.2.11-r3 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 2 CVEs

How to fix

Update zlib from 1.2.11-r3 to 1.2.12-r0 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the 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.12-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-2018-25032 fixed in 1.2.12-r0
  • High CVE-2022-37434 fixed in 1.2.12-r2
High 1 known vulnerability in git@2.52.0-r0 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 1 CVE

How to fix

No fixed version of git is available yet. Check whether composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d needs git 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-66413 fixed in no fix yet
High 1 known vulnerability in unzip@6.0-r16 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 1 CVE

How to fix

No fixed version of unzip is available yet. Check whether composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d needs unzip 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-2008-0888 fixed in no fix yet
High 1 known vulnerability in apk-tools@2.12.5-r0 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 1 CVE

How to fix

Update apk-tools from 2.12.5-r0 to 2.12.6-r0 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the 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.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-2021-36159 fixed in 2.12.6-r0
High 1 known vulnerability in ncurses@6.2_p20210109-r0 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 1 CVE

How to fix

Update ncurses from 6.2_p20210109-r0 to 6.2_p20210109-r1 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.2_p20210109-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-29458 fixed in 6.2_p20210109-r1
High 1 known vulnerability in xz@5.2.5-r0 (infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36) Security · 1 CVE

How to fix

Update xz from 5.2.5-r0 to 5.2.5-r1 or later in infrastructureascode/aws-cli@sha256:891db48126b0f044f06263521acbd611dfa31aa9e549fed23b0b3ef890082b36. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.5-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2022-1271 fixed in 5.2.5-r1

Medium 318

Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 34 places
Medium Ensure that Security Groups are attached to another resource Security · 29 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 28 places
Medium Ensure IAM policies does not allow write access without constraints Security · 26 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 24 places
Medium Ensure every security group and rule has a description Security · 18 places
Medium AWS SSM Parameter should be Encrypted Security · 14 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 8 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 8 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 8 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 8 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 6 places
Medium Check encryption settings for Lambda environmental variable Security · 6 places
Medium Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled Security · 4 places
Medium Ensure S3 buckets should have event notifications enabled Security · 4 places
Medium Ensure AWS ACM Certificate domain name does not include wildcards Security · 4 places
Medium Ensure AWS ALB attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 4 places
Medium Ensure that RDS clusters has backup plan of AWS Backup Reliability · 4 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 4 places
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 4 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 4 places
Medium Ensure Create before destroy for ACM certificates Security · 4 places
Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 4 places
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit Security · 4 places
Medium Ensure S3 lifecycle configuration sets period for aborting failed uploads Security · 4 places
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token Security · 4 places
Medium Ensure no hard-coded secrets exist in lambda environment Security · 4 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 4 places
Medium Ensure Terraform module sources use a commit hash Security · 4 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 2 places
Medium Ensure that EC2 is EBS optimized Security · 2 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 2 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 2 places
Medium Ensure the S3 bucket has access logging enabled Security · 2 places
Medium Ensure all data stored in the SNS topic is encrypted Security · 2 places

Ensure all data stored in the SNS topic is encrypted

Documentation

Where

Medium Ensure RDS cluster configured to copy tags to snapshots Security · 2 places
Medium Ensure that RDS Cluster log capture is enabled Security · 2 places
Medium Ensure ECS Fargate services run on the latest Fargate platform version Security · 2 places
Medium Ensure that Network firewall encryption is via a CMK Security · 2 places
Medium Ensure Network Firewall Policy defines an encryption configuration that uses a customer managed Key (CMK) Security · 2 places

Ensure Network Firewall Policy defines an encryption configuration that uses a customer managed Key (CMK)

Documentation

Where

and 10 more groups with 15 findings

Low 9

Low 2 known vulnerabilities in expat@2.7.5-r0 (composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d) Security · 2 CVEs

How to fix

Update expat from 2.7.5-r0 to 2.8.1-r0 or later in composer:2.9.8@sha256:b09bccd91a78fe8a9ab4b33d707b862e8fe54fec17782e32683ad2a69c46867d. If the 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.1-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

  • Low CVE-2026-41080 fixed in 2.8.1-r0
  • Low CVE-2026-45186 fixed in 2.8.1-r0
Low Missing AWS Budget Cost · 2 places

No AWS budget configured. Budgets help monitor and control spending with alerts.

How to fix

Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.

Where

Low Route53 Health Checks Cost · 2 places

Route53 health checks incur monthly costs. May not be necessary for all resources.

How to fix

Remove health checks for non-critical resources or personal projects.

Where

Low 1 known vulnerability in gcc-12@12.2.0-14%2Bdeb12u1 (redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0 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 perl@5.36.0-7%2Bdeb12u3 (redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether redis:6.2.21@sha256:5443f35e8fc8fc8496964b8e8ea39abaf99434d7e1741e514f7f56906b1c9ff0 needs perl 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-4116 fixed in no fix yet
Low 1 known vulnerability in package.json@unknown (stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e) Security · 1 CVE

How to fix

No fixed version of package.json is available yet. Check whether stoplight/prism:5.15.10@sha256:586d1f0f94f8d0eaf20b26b8b41f985f2a2d494bea297bd3988c3de3eb87094e needs package.json 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-2026-3449 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 25 Jun 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.