InfraScan Cloud

Repository scan

openmrs-contrib-cluster

olszewskiigor/openmrs-contrib-cluster · branch main · scanned 3 Jun 2026 · 98 resources

DOverall
FSecurity
–Reliability · N/A
CCost
392findings · 0 critical, 114 high
—no cost findings with a savings estimate

High 265

High 52 known vulnerabilities in unknown@unknown (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 52 CVEs

How to fix

No fixed version of unknown is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 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-2025-31133 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • High CVE-2025-52881 fixed in no fix yet
  • High CVE-2025-22868 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-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2025-22871 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-22866 fixed in no fix yet
  • and 32 more
High 48 known vulnerabilities in unknown@unknown (rancher/local-path-provisioner:v0.0.31) Security · 48 CVEs

How to fix

No fixed version of unknown is available yet. Check whether rancher/local-path-provisioner:v0.0.31 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-2025-22868 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-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2025-65637 fixed in no fix yet
  • High CVE-2026-44543 fixed in no fix yet
  • High CVE-2025-22871 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • High CVE-2025-62878 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-22866 fixed in no fix yet
  • and 28 more
High 47 known vulnerabilities in unknown@unknown (registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f) Security · 47 CVEs

How to fix

No fixed version of unknown is available yet. Check whether registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f 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-2025-22868 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-39820 fixed in no fix yet
  • High CVE-2025-22871 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-22866 fixed in no fix yet
  • Medium CVE-2025-58183 fixed in no fix yet
  • Medium CVE-2025-22870 fixed in no fix yet
  • Medium CVE-2024-45338 fixed in no fix yet
  • Medium CVE-2025-22872 fixed in no fix yet
  • and 27 more
High 28 known vulnerabilities in curl@8.10.1-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 28 CVEs

How to fix

Update curl from 8.10.1-r0 to 8.12.0-r0 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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.12.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-2025-0665 fixed in 8.12.0-r0
  • High CVE-2025-0725 fixed in 8.12.0-r0
  • High CVE-2025-5399 fixed in 8.14.1-r0
  • High CVE-2025-9086 fixed in 8.14.1-r2
  • High CVE-2026-3805 fixed in no fix yet
  • High CVE-2026-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • Medium CVE-2025-10966 fixed in no fix yet
  • Medium CVE-2025-5025 fixed in 8.14.0-r0
  • Medium CVE-2025-10148 fixed in 8.14.1-r2
  • 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-2026-6429 fixed in no fix yet
  • Medium CVE-2026-7168 fixed in no fix yet
  • Medium CVE-2025-13034 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 no fix yet
  • and 8 more
High 22 known vulnerabilities in openssl@3.3.2-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 22 CVEs

How to fix

Update openssl from 3.3.2-r0 to 3.3.6-r0 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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.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-2025-69419 fixed in 3.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2026-28387 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • High CVE-2026-31789 fixed in 3.3.7-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2024-13176 fixed in 3.3.2-r2
  • Medium CVE-2024-9143 fixed in 3.3.2-r1
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • and 2 more
High 21 known vulnerabilities in openssl@3.3.2-r4 (rancher/local-path-provisioner:v0.0.31) Security · 21 CVEs

How to fix

Update openssl from 3.3.2-r4 to 3.3.6-r0 or later in rancher/local-path-provisioner:v0.0.31. If the 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.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-2025-69419 fixed in 3.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2026-28387 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • High CVE-2026-31789 fixed in 3.3.7-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2024-13176 fixed in 3.3.2-r5
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • Medium CVE-2024-12797 fixed in 3.3.3-r0
  • and 1 more
High 6 known vulnerabilities in stdlib@1.23.5 (rancher/local-path-provisioner:v0.0.31) Security · 6 CVEs

How to fix

Update stdlib from 1.23.5 to 1.25.8 or later in rancher/local-path-provisioner:v0.0.31. If the 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
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 6 known vulnerabilities in libxml2@2.12.7-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 6 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 needs libxml2 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-6021 fixed in no fix yet
  • High CVE-2024-56171 fixed in 2.12.7-r1
  • High CVE-2025-24928 fixed in 2.12.7-r1
  • Medium CVE-2025-32414 fixed in 2.12.10-r0
  • Low CVE-2025-27113 fixed in 2.12.7-r2
  • Low CVE-2025-32415 fixed in 2.12.10-r0
High 6 known vulnerabilities in stdlib@1.22.8 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 6 CVEs

How to fix

Update stdlib from 1.22.8 to 1.25.8 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 6 known vulnerabilities in stdlib@1.22.8 (registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f) Security · 6 CVEs

How to fix

Update stdlib from 1.22.8 to 1.25.8 or later in registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f. If the 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
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 3 known vulnerabilities in musl@1.2.5-r8 (rancher/local-path-provisioner:v0.0.31) Security · 3 CVEs

How to fix

Update musl from 1.2.5-r8 to 1.2.5-r9 or later in rancher/local-path-provisioner:v0.0.31. If the 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-r9); if 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.5-r9
  • High CVE-2026-40200 fixed in 1.2.5-r11
  • Medium CVE-2026-6042 fixed in 1.2.5-r10
High 3 known vulnerabilities in musl@1.2.5-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 3 CVEs

How to fix

Update musl from 1.2.5-r0 to 1.2.5-r1 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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-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-2025-26519 fixed in 1.2.5-r1
  • High CVE-2026-40200 fixed in 1.2.5-r3
  • Medium CVE-2026-6042 fixed in 1.2.5-r2
High 3 known vulnerabilities in net@0.28.0 (registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f) Security · 3 CVEs

How to fix

Update net from 0.28.0 to 0.53.0 or later in registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.4@sha256:a9f03b34a3cbfbb26d103a14046ab2c5130a80c3d69d526ff8063d2b37b9fd3f. If the 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.53.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-33814 fixed in 0.53.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High Missing AWS Budget Cost · 3 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

High 2 known vulnerabilities in c-ares@1.33.1-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 2 CVEs

How to fix

No fixed version of c-ares is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 needs c-ares 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-31498 fixed in no fix yet
  • Medium CVE-2025-62408 fixed in no fix yet
High 2 known vulnerabilities in protobuf@24.4-r1 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 2 CVEs

How to fix

No fixed version of protobuf is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 needs protobuf 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-0994 fixed in no fix yet
  • High CVE-2024-7254 fixed in no fix yet
High 2 known vulnerabilities in xz@5.6.2-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 2 CVEs

How to fix

Update xz from 5.6.2-r0 to 5.6.2-r1 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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.6.2-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-2025-31115 fixed in 5.6.2-r1
  • Low CVE-2026-34743 fixed in 5.8.3-r0
High Expensive NAT Gateway Cost · 2 places

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

High 1 known vulnerability in icu@74.2-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 1 CVE

How to fix

Update icu from 74.2-r0 to 74.2-r1 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 74.2-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-2025-5222 fixed in 74.2-r1
High 1 known vulnerability in nghttp2@1.62.1-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 1 CVE

How to fix

No fixed version of nghttp2 is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 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 Old Generation Instance Cost · 1 place

Usage of old generation EC2 instances (e.g., t2, m3, c4, r3). Newer generations are often cheaper and faster.

How to fix

Upgrade to current generation instances (e.g., t3, m5, c5, r5).

Where

Medium 127

Medium Base64 High Entropy String Security · 10 places
Medium Ensure SSM parameters are using KMS CMK Security · 5 places
Medium Ensure top-level permissions are not set to write-all Security · 4 places

Ensure top-level permissions are not set to write-all

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 4 places

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium CPU limits should be set Reliability · 4 places
Medium Memory limits should be set Reliability · 4 places
Medium Apply security context to your pods and containers Security · 4 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 4 places
Medium 3 known vulnerabilities in busybox@1.37.0-r12 (rancher/local-path-provisioner:v0.0.31) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether rancher/local-path-provisioner:v0.0.31 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
  • Low CVE-2024-58251 fixed in 1.37.0-r14
  • Low CVE-2025-46394 fixed in 1.37.0-r14
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 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
  • Low CVE-2024-58251 fixed in 1.36.1-r31
  • Low CVE-2025-46394 fixed in 1.36.1-r31
Medium CPU requests should be set Reliability · 3 places
Medium Memory requests should be set Reliability · 3 places
Medium Missing Cost and Usage Report Cost · 3 places

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Medium 2 known vulnerabilities in net@0.34.0 (rancher/local-path-provisioner:v0.0.31) Security · 2 CVEs

How to fix

Update net from 0.34.0 to 0.36.0 or later in rancher/local-path-provisioner:v0.0.31. If the 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.36.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-22870 fixed in 0.36.0
  • Medium CVE-2026-25680 fixed in 0.55.0
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (rancher/local-path-provisioner:v0.0.31) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in rancher/local-path-provisioner:v0.0.31. If the 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 zlib@1.3.1-r1 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r1 to 1.3.2-r0 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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 Ensure that S3 bucket has a Public Access block Security · 2 places

Ensure that S3 bucket has a Public Access block

Documentation

Where

Medium Ensure that an S3 bucket has a lifecycle configuration Security · 2 places

Ensure that an S3 bucket has a lifecycle configuration

Documentation

Where

Medium Ensure S3 buckets should have event notifications enabled Security · 2 places

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 2 places

Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK

Documentation

Where

Medium Ensure VPC subnets do not assign public IP by default Security · 2 places

Ensure VPC subnets do not assign public IP by default

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 2 places

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 2 places

Ensure that S3 buckets are encrypted with KMS by default

Documentation

Where

Medium Ensure the S3 bucket has access logging enabled Security · 2 places

Ensure the S3 bucket has access logging enabled

Documentation

Where

Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 2 places

Ensure DynamoDB point in time recovery (backup) is enabled

Documentation

Where

Medium Use read-only filesystem for containers where possible Security · 2 places

Use read-only filesystem for containers where possible

Documentation

Where

Medium Containers should run as a high UID to avoid host conflict Security · 2 places

Containers should run as a high UID to avoid host conflict

Documentation

Where

Medium Missing Spot Instance Usage Cost · 2 places

No spot instances detected. Spot instances can save 50-90% on compute costs for interruptible workloads.

How to fix

Use spot instances for batch jobs, data analysis, and optional tasks. Consider aws_spot_instance_request or spot_price in launch templates.

Where

Medium 1 known vulnerability in grpc@1.62.1-r0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 1 CVE

How to fix

No fixed version of grpc is available yet. Check whether registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5 needs grpc 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-2024-7246 fixed in no fix yet
Medium 1 known vulnerability in net@0.29.0 (registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5) Security · 1 CVE

How to fix

Update net from 0.29.0 to 0.55.0 or later in registry.k8s.io/ingress-nginx/controller:v1.12.1@sha256:9724476b928967173d501040631b23ba07f47073999e80e34b120e8db5f234d5. If the 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.55.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-25680 fixed in 0.55.0
Medium Ensure VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium AWS SSM Parameter should be Encrypted Security · 1 place

AWS SSM Parameter should be Encrypted

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 1 place

Ensure an IAM role is attached to EC2 instance

Documentation

Where

Medium Ensure that Security Groups are attached to another resource Security · 1 place

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 1 place

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure AWS RDS database instance configured with encryption in transit Security · 1 place

Ensure AWS RDS database instance configured with encryption in transit

Documentation

Where

Medium No ServiceAccount/Node should be able to read all secrets Security · 1 place

No ServiceAccount/Node should be able to read all secrets

Documentation

Where

Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 1 place

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 1 place

Ensure that detailed monitoring is enabled for EC2 instances

Documentation

Where

and 31 more groups with 31 findings

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 3 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.