InfraScan Cloud

Repository scan

OpenSRE

swapnildahiphale/OpenSRE · branch main · scanned 25 Jun 2026 · 76 resources

DOverall
FSecurity
–Reliability · N/A
CCost
307findings · 0 critical, 31 high
$75.00–$135estimated savings per month, from the code

High 133

High 52 known vulnerabilities in unknown@unknown (neo4j:5-community) Security · 52 CVEs

How to fix

No fixed version of unknown is available yet. Check whether neo4j:5-community 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-48962 fixed in no fix yet
  • High CVE-2026-48959 fixed in no fix yet
  • High CVE-2026-54512 fixed in no fix yet
  • High CVE-2026-54512 fixed in no fix yet
  • High CVE-2026-54513 fixed in no fix yet
  • High CVE-2026-54513 fixed in no fix yet
  • High CVE-2026-49268 fixed in no fix yet
  • High CVE-2026-12087 fixed in no fix yet
  • Medium CVE-2025-45582 fixed in no fix yet
  • Medium CVE-2026-43895 fixed in no fix yet
  • Medium CVE-2026-54514 fixed in no fix yet
  • Medium CVE-2026-54514 fixed in no fix yet
  • Medium CVE-2026-54515 fixed in no fix yet
  • Medium CVE-2026-54515 fixed in no fix yet
  • Medium CVE-2026-54516 fixed in no fix yet
  • Medium CVE-2026-54516 fixed in no fix yet
  • Medium CVE-2026-54517 fixed in no fix yet
  • Medium CVE-2026-54517 fixed in no fix yet
  • Medium CVE-2025-15649 fixed in no fix yet
  • Medium CVE-2026-43894 fixed in no fix yet
  • and 32 more
High 37 known vulnerabilities in unknown@unknown (python:3.11-slim) Security · 37 CVEs

How to fix

No fixed version of unknown is available yet. Check whether python:3.11-slim 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-24049 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-48959 fixed in no fix yet
  • High CVE-2026-12087 fixed in no fix yet
  • Medium CVE-2025-45582 fixed in no fix yet
  • Medium CVE-2026-3219 fixed in no fix yet
  • Medium CVE-2026-6357 fixed in no fix yet
  • Medium CVE-2025-15649 fixed in no fix yet
  • Medium CVE-2026-8643 fixed in no fix yet
  • Medium CVE-2025-8869 fixed in no fix yet
  • Medium CVE-2026-7010 fixed in no fix yet
  • Low CVE-2005-2541 fixed in no fix yet
  • Low CVE-2007-5686 fixed in no fix yet
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2011-3374 fixed in no fix yet
  • Low CVE-2011-4116 fixed in no fix yet
  • Low CVE-2013-4392 fixed in no fix yet
  • Low CVE-2017-18018 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • and 17 more
High 31 known vulnerabilities in unknown@unknown (postgres:15-alpine) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:15-alpine 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-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-68121 fixed in no fix yet
  • Medium CVE-2025-58183 fixed in no fix yet
  • Medium CVE-2025-47912 fixed in no fix yet
  • Medium CVE-2025-58186 fixed in no fix yet
  • Medium CVE-2025-58189 fixed in no fix yet
  • Medium CVE-2025-61724 fixed in no fix yet
  • Medium CVE-2025-61730 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • and 11 more
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 6 known vulnerabilities in stdlib@1.24.6 (postgres:15-alpine) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:15-alpine. 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

Medium 170

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 8 places
Medium 6 known vulnerabilities in unknown@unknown (envoyproxy/envoy:v1.28-latest) Security · 6 CVEs

How to fix

No fixed version of unknown is available yet. Check whether envoyproxy/envoy:v1.28-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

  • Medium CVE-2024-12133 fixed in no fix yet
  • Medium CVE-2024-12243 fixed in no fix yet
  • Medium CVE-2025-4802 fixed in no fix yet
  • Medium CVE-2025-30258 fixed in no fix yet
  • Low CVE-2024-13176 fixed in no fix yet
  • Low CVE-2024-9143 fixed in no fix yet
Medium Use read-only filesystem for containers where possible Security · 6 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 6 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 6 places
Medium Containers should run as a high UID to avoid host conflict Security · 6 places
Medium Image should use digest Security · 6 places
Medium Image Tag should be fixed - not latest or blank Security · 5 places
Medium Containers should not run with allowPrivilegeEscalation Security · 5 places
Medium Minimize the admission of root containers Security · 5 places
Medium Minimize the admission of containers with the NET_RAW capability Security · 5 places
Medium Apply security context to your pods and containers Security · 5 places
Medium Apply security context to your containers Security · 5 places
Medium Minimize the admission of containers with capabilities assigned Security · 5 places
Medium Ensure every security group and rule has a description Security · 4 places
Medium Missing Cost and Usage Report Cost · 4 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 Minimize the admission of pods which lack an associated NetworkPolicy Security · 3 places

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 3 places
Medium Ensure that EC2 is EBS optimized Security · 3 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 3 places

Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted

Documentation

Where

Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 3 places

Ensure that HEALTHCHECK instructions have been added to container images

Documentation

Where

Medium Prefer using secrets as files over secrets as environment variables Security · 3 places
Medium Missing Spot Instance Usage Cost · 3 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 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 Ensure that ALB redirects HTTP requests into HTTPS ones Security · 2 places

Ensure that ALB redirects HTTP requests into HTTPS ones

Documentation

Where

Medium Ensure that Security Groups are attached to another resource Security · 2 places

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure that load balancer is using at least TLS 1.2 Security · 2 places
Medium Ensure that ALB drops HTTP headers Security · 2 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 2 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 2 places

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 2 places
Medium Ensure ALB protocol is HTTPS Security · 2 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 2 places

Ensure CloudWatch log groups retains logs for at least 1 year

Documentation

Where

Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 2 places
Medium Ensure ECR Image Tags are immutable Security · 2 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 2 places

Ensure the ELBv2 (Application/Network) has access logging enabled

Documentation

Where

Medium CPU requests should be set Reliability · 2 places
Medium CPU limits should be set Reliability · 2 places
Medium Memory requests should be set Reliability · 2 places
Medium Memory limits should be set Reliability · 2 places

and 23 more groups with 28 findings

Low 4

Low Missing AWS Budget Cost · 4 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

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.