InfraScan Cloud

Repository scan

kani-k8s

starci-lab/kani-k8s · branch main · scanned 25 Jun 2026 · 63 resources

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

High 118

High 98 known vulnerabilities in unknown@unknown (portainer/portainer-ce:2.33.6) Security · 98 CVEs

How to fix

No fixed version of unknown is available yet. Check whether portainer/portainer-ce:2.33.6 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-15558 fixed in no fix yet
  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2026-24051 fixed in no fix yet
  • High CVE-2026-45022 fixed in no fix yet
  • High CVE-2026-53489 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-39883 fixed in no fix yet
  • High CVE-2026-46680 fixed in no fix yet
  • High CVE-2026-46680 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2026-29181 fixed in no fix yet
  • High CVE-2026-32280 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-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • and 78 more
High 10 known vulnerabilities in stdlib@1.25.5 (portainer/portainer-ce:2.33.6) Security · 10 CVEs

How to fix

Update stdlib from 1.25.5 to 1.25.8 or later in portainer/portainer-ce:2.33.6. 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-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 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-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • High CVE-2026-42504 fixed in 1.25.11
High 7 known vulnerabilities in unknown@unknown (bitnami/kubectl:latest) Security · 7 CVEs

How to fix

No fixed version of unknown is available yet. Check whether bitnami/kubectl:latest 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-33814 fixed in no fix yet
  • High CVE-2026-39821 fixed in no fix yet
  • Medium CVE-2026-25681 fixed in no fix yet
  • Medium CVE-2026-27136 fixed in no fix yet
  • Medium CVE-2026-42502 fixed in no fix yet
  • Medium CVE-2026-42506 fixed in no fix yet
  • Low CVE-2026-39824 fixed in no fix yet
High 3 known vulnerabilities in crypto@0.45.0 (portainer/portainer-ce:2.33.6) Security · 3 CVEs

How to fix

Update crypto from 0.45.0 to 0.52.0 or later in portainer/portainer-ce:2.33.6. 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.52.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-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0

Medium 30

Medium Base64 High Entropy String Security · 5 places
Medium 2 known vulnerabilities in kubernetes@1.36.2 (bitnami/kubectl:latest) Security · 2 CVEs

How to fix

No fixed version of kubernetes is available yet. Check whether bitnami/kubectl:latest needs kubernetes 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-1767 fixed in no fix yet
  • Low CVE-2024-7598 fixed in no fix yet
Medium Minimize the admission of containers with the NET_RAW capability Security · 2 places
Medium Image should use digest Security · 2 places
Medium 1 known vulnerability in net@0.49.0 (bitnami/kubectl:latest) Security · 1 CVE

How to fix

Update net from 0.49.0 to 0.55.0 or later in bitnami/kubectl:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.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 1 known vulnerability in net@0.47.0 (portainer/portainer-ce:2.33.6) Security · 1 CVE

How to fix

Update net from 0.47.0 to 0.55.0 or later in portainer/portainer-ce:2.33.6. 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 Minimize the admission of pods which lack an associated NetworkPolicy Security · 1 place

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 · 1 place
Medium Memory limits should be set Reliability · 1 place
Medium Image Tag should be fixed - not latest or blank Security · 1 place

Image Tag should be fixed - not latest or blank

Documentation

Where

Medium Containers should not run with allowPrivilegeEscalation Security · 1 place

Containers should not run with allowPrivilegeEscalation

Documentation

Where

Medium Use read-only filesystem for containers where possible Security · 1 place

Use read-only filesystem for containers where possible

Documentation

Where

Medium Minimize the admission of root containers Security · 1 place
Medium Apply security context to your pods and containers Security · 1 place

Apply security context to your pods and containers

Documentation

Where

Medium Apply security context to your pods, deployments and daemon_sets Security · 1 place

Apply security context to your pods, deployments and daemon_sets

Documentation

Where

Medium Apply security context to your containers Security · 1 place
Medium Apply security context to your pods and containers Security · 1 place

Apply security context to your pods and containers

Documentation

Where

Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 1 place

Ensure that the seccomp profile is set to docker/default or runtime/default

Documentation

Where

Medium Minimize the admission of containers with capabilities assigned Security · 1 place

Minimize the admission of containers with capabilities assigned

Documentation

Where

Medium Ensure that Service Account Tokens are only mounted where necessary Security · 1 place

Ensure that Service Account Tokens are only mounted where necessary

Documentation

Where

Medium Containers should run as a high UID to avoid host conflict Security · 1 place

Containers should run as a high UID to avoid host conflict

Documentation

Where

Medium Liveness Probe Should be Configured Reliability · 1 place
Medium Readiness Probe Should be Configured Reliability · 1 place

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.