Repository scan
kani-k8s
starci-lab/kani-k8s · branch main · scanned 25 Jun 2026 · 63 resources
High 118
High 98 known vulnerabilities in unknown@unknown (portainer/portainer-ce:2.33.6)
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)
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)
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)
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
Base64 High Entropy String
Where
- ../../terraform/do/modules/kubernetes/yamls/reference/argo-cd.yaml:4100
- ../../terraform/do/modules/kubernetes/yamls/reference/kafka.yaml:358
- ../../terraform/do/modules/kubernetes/yamls/reference/kafka.yaml:361
- ../../terraform/do/modules/kubernetes/yamls/reference/kafka.yaml:2323
- ../../terraform/do/modules/kubernetes/yamls/reference/loki-monolithic.yaml:4030
Medium 2 known vulnerabilities in kubernetes@1.36.2 (bitnami/kubectl:latest)
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
Minimize the admission of containers with the NET_RAW capability
Where
Medium Image should use digest
Medium 1 known vulnerability in net@0.49.0 (bitnami/kubectl:latest)
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)
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
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
CPU limits should be set
Where
Medium Memory limits should be set
Memory limits should be set
Where
Medium Image Tag should be fixed - not latest or blank
Image Tag should be fixed - not latest or blank
Where
Medium Containers should not run with allowPrivilegeEscalation
Containers should not run with allowPrivilegeEscalation
Where
Medium Use read-only filesystem for containers where possible
Use read-only filesystem for containers where possible
Where
Medium Minimize the admission of root containers
Minimize the admission of root containers
Where
Medium Apply security context to your pods and containers
Apply security context to your pods and containers
Where
Medium Apply security context to your pods, deployments and daemon_sets
Apply security context to your pods, deployments and daemon_sets
Where
Medium Apply security context to your containers
Apply security context to your containers
Where
Medium Apply security context to your pods and containers
Apply security context to your pods and containers
Where
Medium Ensure that the seccomp profile is set to docker/default or runtime/default
Ensure that the seccomp profile is set to docker/default or runtime/default
Where
Medium Minimize the admission of containers with capabilities assigned
Minimize the admission of containers with capabilities assigned
Where
Medium Ensure that Service Account Tokens are only mounted where necessary
Ensure that Service Account Tokens are only mounted where necessary
Where
Medium Containers should run as a high UID to avoid host conflict
Containers should run as a high UID to avoid host conflict
Where
Medium Liveness Probe Should be Configured
Liveness Probe Should be Configured
Where
Medium Readiness Probe Should be Configured
Readiness Probe Should be Configured
Where
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.