InfraScan Cloud

Repository scan

zentinelle

calliopeai/zentinelle · branch main · scanned 25 Jun 2026 · 230 resources

DOverall
FSecurity
–Reliability · N/A
BCost
241findings · 0 critical, 32 high
—no cost findings with a savings estimate

High 70

High 31 known vulnerabilities in unknown@unknown (postgres:16-alpine) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:16-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 22 known vulnerabilities in openssl@3.3.2-r0 (clickhouse/clickhouse-server:24-alpine) Security · 22 CVEs

How to fix

Update openssl from 3.3.2-r0 to 3.3.6-r0 or later in clickhouse/clickhouse-server:24-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 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 8 known vulnerabilities in curl@8.19.0-r0 (nginx:alpine) Security · 8 CVEs

How to fix

No fixed version of curl is available yet. Check whether nginx:alpine needs curl 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-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • 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-2026-5545 fixed in no fix yet
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:16-alpine) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:16-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
High 3 known vulnerabilities in musl@1.2.5-r0 (clickhouse/clickhouse-server:24-alpine) Security · 3 CVEs

How to fix

Update musl from 1.2.5-r0 to 1.2.5-r1 or later in clickhouse/clickhouse-server:24-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.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

Medium 168

Medium Ensure every security group and rule has a description Security · 12 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 12 places
Medium Ensure that key vault secrets have "content_type" set Security · 5 places
Medium Ensure that the expiration date is set on all secrets Security · 5 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 4 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 4 places
Medium Ensure IAM policies does not allow write access without constraints Security · 4 places
Medium Ensure ECS containers are limited to read-only access to root filesystems Security · 4 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 4 places
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (clickhouse/clickhouse-server:24-alpine) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether clickhouse/clickhouse-server:24-alpine 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 Ensure S3 buckets should have event notifications enabled Security · 3 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 3 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 3 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 3 places
Medium Ensure the S3 bucket has access logging enabled Security · 3 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 3 places
Medium Ensure RDS Performance Insights are encrypted using KMS CMKs Security · 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 zlib@1.3.1-r1 (clickhouse/clickhouse-server:24-alpine) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r1 to 1.3.2-r0 or later in clickhouse/clickhouse-server:24-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.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 public facing ALB are protected by WAF Security · 2 places
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 2 places

Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones

Documentation

Where

Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 2 places

Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones

Documentation

Where

Medium Ensure that Security Groups are attached to another resource Security · 2 places
Medium Ensure that ALB drops HTTP headers Security · 2 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 2 places
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 2 places

Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure ECS Cluster logging is enabled and client to container communication uses CMK Security · 2 places

Ensure ECS Cluster logging is enabled and client to container communication uses CMK

Documentation

Where

Medium Ensure all data stored in the SNS topic is encrypted Security · 2 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 2 places
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token Security · 2 places

Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token

Documentation

Where

Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 2 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 2 places
Medium Ensure container insights are enabled on ECS cluster Security · 2 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 2 places
Medium Ensure Terraform module sources use a commit hash Security · 2 places
Medium Load Balancer for Single Instance Cost · 2 places

Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.

How to fix

Consider if load balancer is necessary for single-instance deployments or low-traffic applications.

Where

Medium 1 known vulnerability in busybox@1.37.0-r30 (nginx:alpine) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether nginx:alpine 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
Medium 1 known vulnerability in freetype@2.14.1-r0 (nginx:alpine) Security · 1 CVE

How to fix

No fixed version of freetype is available yet. Check whether nginx:alpine needs freetype 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-2026-23865 fixed in no fix yet
Medium 1 known vulnerability in busybox@1.37.0-r14 (redis:7-alpine) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether redis:7-alpine 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
Medium 1 known vulnerability in util-linux@2.40.4-r1 (redis:7-alpine) Security · 1 CVE

How to fix

No fixed version of util-linux is available yet. Check whether redis:7-alpine needs util-linux 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-2026-27456 fixed in no fix yet

and 47 more groups with 47 findings

Low 3

Low 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

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.