InfraScan Cloud

Repository scan

dev-ops

conservify/dev-ops · branch main · scanned 25 Jun 2026 · 59 resources

DOverall
DSecurity
–Reliability · N/A
DCost
361findings · 0 critical, 82 high
$971–$1,077estimated savings per month, from the code

High 271

High 140 known vulnerabilities in unknown@unknown (influxdb:1.8) Security · 140 CVEs

How to fix

No fixed version of unknown is available yet. Check whether influxdb:1.8 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-24528 fixed in no fix yet
  • High CVE-2026-42010 fixed in no fix yet
  • High CVE-2026-42012 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2025-69419 fixed in no fix yet
  • High CVE-2026-42011 fixed in no fix yet
  • High CVE-2024-4741 fixed in no fix yet
  • High CVE-2025-15281 fixed in no fix yet
  • High CVE-2025-69420 fixed in no fix yet
  • High CVE-2025-69421 fixed in no fix yet
  • High CVE-2025-9230 fixed in no fix yet
  • High CVE-2026-0915 fixed in no fix yet
  • High CVE-2026-27135 fixed in no fix yet
  • High CVE-2026-28388 fixed in no fix yet
  • High CVE-2026-28389 fixed in no fix yet
  • High CVE-2026-28390 fixed in no fix yet
  • High CVE-2026-33845 fixed in no fix yet
  • High CVE-2026-33846 fixed in no fix yet
  • High CVE-2026-34180 fixed in no fix yet
  • High CVE-2026-4046 fixed in no fix yet
  • and 120 more
High 103 known vulnerabilities in unknown@unknown (mongo:6.0) Security · 103 CVEs

How to fix

No fixed version of unknown is available yet. Check whether mongo:6.0 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-45447 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-2026-39820 fixed in no fix yet
  • High CVE-2026-39829 fixed in no fix yet
  • High CVE-2026-39830 fixed in no fix yet
  • High CVE-2026-39831 fixed in no fix yet
  • High CVE-2026-39832 fixed in no fix yet
  • High CVE-2026-39833 fixed in no fix yet
  • High CVE-2026-39834 fixed in no fix yet
  • and 83 more
High 10 known vulnerabilities in stdlib@1.24.6 (mongo:6.0) Security · 10 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in mongo:6.0. 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-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
  • Medium CVE-2025-58185 fixed in 1.24.8
High 8 known vulnerabilities in curl@8.19.0-r0 (caddy:latest) Security · 8 CVEs

How to fix

No fixed version of curl is available yet. Check whether caddy:latest 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 3 known vulnerabilities in crypto@0.45.0 (mongo:6.0) Security · 3 CVEs

How to fix

Update crypto from 0.45.0 to 0.52.0 or later in mongo:6.0. 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
High EBS Provisioned IOPS (io1/io2) Cost · 3 places

EBS volume using Provisioned IOPS (io1/io2) type. These are very expensive — io2 costs 56× more than gp3 per GB plus per-IOPS charges.

How to fix

Verify if gp3 can meet performance requirements at a lower cost.

Where

High 2 known vulnerabilities in net@0.47.0 (mongo:6.0) Security · 2 CVEs

How to fix

Update net from 0.47.0 to 0.53.0 or later in mongo:6.0. 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-2026-25680 fixed in 0.55.0
High 1 known vulnerability in stdlib@1.26.3 (caddy:latest) Security · 1 CVE

How to fix

Update stdlib from 1.26.3 to 1.26.4 or later in caddy: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 1.26.4); 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-42504 fixed in 1.26.4
High Expensive NAT Gateway Cost · 1 place

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

Medium 77

Medium Ensure every security group and rule has a description Security · 5 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 5 places
Medium Ensure that EC2 is EBS optimized Security · 3 places
Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 3 places

Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 3 places
Medium Old Generation Storage (gp2) Cost · 3 places

Using gp2 EBS volumes when gp3 provides better performance at lower cost.

How to fix

Migrate from gp2 to gp3 volumes. gp3 offers 20% cost savings and better baseline performance.

Where

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 unknown@unknown (caddy:latest) Security · 2 CVEs

How to fix

No fixed version of unknown is available yet. Check whether caddy: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-2026-42507 fixed in no fix yet
  • Medium CVE-2026-27145 fixed in no fix yet
Medium 2 known vulnerabilities in gnutls28@3.7.3-4ubuntu1.8 (mongo:6.0) Security · 2 CVEs

How to fix

Update gnutls28 from 3.7.3-4ubuntu1.8 to 3.7.3-4ubuntu1.9 or later in mongo:6.0. 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.7.3-4ubuntu1.9); 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-42014 fixed in 3.7.3-4ubuntu1.9
  • Medium CVE-2026-5260 fixed in 3.7.3-4ubuntu1.9
Medium 2 known vulnerabilities in libgcrypt20@1.9.4-3ubuntu3 (mongo:6.0) Security · 2 CVEs

How to fix

Update libgcrypt20 from 1.9.4-3ubuntu3 to 1.9.4-3ubuntu3.2 or later in mongo:6.0. 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.9.4-3ubuntu3.2); 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-41989 fixed in 1.9.4-3ubuntu3.2
  • Low CVE-2024-2236 fixed in no fix yet
Medium Route53 A Record has Attached Resource Security · 2 places
Medium Ensure AWS route table with VPC peering does not contain routes overly permissive to all traffic Security · 2 places

Ensure AWS route table with VPC peering does not contain routes overly permissive to all traffic

Documentation

Where

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 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 all data stored in the S3 bucket have versioning enabled Reliability · 2 places

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

Medium Missing Cost and Usage Report Cost · 2 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 1 known vulnerability in busybox@1.37.0-r30 (caddy:latest) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether caddy:latest 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 glibc@2.35-0ubuntu3.13 (mongo:6.0) Security · 1 CVE

How to fix

No fixed version of glibc is available yet. Check whether mongo:6.0 needs glibc 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-5435 fixed in no fix yet
Medium 1 known vulnerability in systemd@249.11-0ubuntu3.20 (mongo:6.0) Security · 1 CVE

How to fix

Update systemd from 249.11-0ubuntu3.20 to 249.11-0ubuntu3.21 or later in mongo:6.0. 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 249.11-0ubuntu3.21); 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-40226 fixed in 249.11-0ubuntu3.21
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 Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 1 place

Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances

Documentation

Where

Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 1 place

Ensure that ALB redirects HTTP requests into HTTPS ones

Documentation

Where

Medium Ensure public facing ALB are protected by WAF Security · 1 place

Ensure public facing ALB are protected by WAF

Documentation

Where

Medium Ensure that load balancer is using at least TLS 1.2 Security · 1 place

Ensure that load balancer is using at least TLS 1.2

Documentation

Where

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 1 place

Ensure that AWS Lambda function is configured for function-level concurrent execution limit

Documentation

Where

Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 1 place

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that AWS Lambda function is configured inside a VPC Security · 1 place

Ensure that AWS Lambda function is configured inside a VPC

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 1 place

Ensure that ALB drops HTTP headers

Documentation

Where

Medium Ensure that Load Balancer has deletion protection enabled Reliability · 1 place

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Ensure ALB protocol is HTTPS Security · 1 place

Ensure ALB protocol is HTTPS

Documentation

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 1 place

Ensure no security groups allow ingress from 0.0.0.0:0 to port 80

Documentation

Where

Medium Ensure AWS Lambda function is configured to validate code-signing Security · 1 place

Ensure AWS Lambda function is configured to validate code-signing

Documentation

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 1 place

Ensure IAM policies does not allow write access without constraints

Documentation

Where

Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 1 place

Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions

Documentation

Where

Medium Ensure Lambda Runtime is not deprecated Security · 1 place

Ensure Lambda Runtime is not deprecated

Documentation

Where

and 6 more groups with 6 findings

Low 13

Low EC2 Detailed Monitoring Cost · 3 places

Detailed monitoring for EC2 instances incurs extra costs.

How to fix

Disable detailed monitoring if standard 5-minute metrics are sufficient.

Where

Low Large Root Volume Cost · 3 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

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

Low 1 known vulnerability in pcre3@2%3A8.39-13 (influxdb:1.8) Security · 1 CVE

How to fix

No fixed version of pcre3 is available yet. Check whether influxdb:1.8 needs pcre3 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

  • Low CVE-2017-11164 fixed in no fix yet
Low 1 known vulnerability in perl@5.32.1-4%2Bdeb11u3 (influxdb:1.8) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether influxdb:1.8 needs perl 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

  • Low CVE-2011-4116 fixed in no fix yet
Low 1 known vulnerability in sqlite3@3.34.1-3%2Bdeb11u1 (influxdb:1.8) Security · 1 CVE

How to fix

No fixed version of sqlite3 is available yet. Check whether influxdb:1.8 needs sqlite3 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

  • Low CVE-2025-52099 fixed in no fix yet
Low 1 known vulnerability in gcc-12@12.3.0-1ubuntu1~22.04.3 (mongo:6.0) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether mongo:6.0 needs gcc-12 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

  • Low CVE-2022-27943 fixed in no fix yet
Low 1 known vulnerability in ncurses@6.3-2ubuntu0.1 (mongo:6.0) Security · 1 CVE

How to fix

No fixed version of ncurses is available yet. Check whether mongo:6.0 needs ncurses 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

  • Low CVE-2023-50495 fixed in no fix yet

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.