InfraScan Cloud

Repository scan

votemonitor

commitglobal/votemonitor · branch main · scanned 25 Jun 2026 · 82 resources

COverall
DSecurity
–Reliability · N/A
BCost
148findings · 0 critical, 22 high
$30.90–$97.25estimated savings per month, from the code

High 87

High 79 known vulnerabilities in unknown@unknown (postgres:16) Security · 79 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:16 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-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-2026-48959 fixed in no fix yet
  • High CVE-2026-12087 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-45582 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
  • and 59 more
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:16) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:16. 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 1 known vulnerability in unknown@unknown (axllent/mailpit) Security · 1 CVE

How to fix

No fixed version of unknown is available yet. Check whether axllent/mailpit 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-2023-42821 fixed in no fix yet
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 59

Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 6 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 6 places
Medium Ensure every security group and rule has a description Security · 4 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 3 places

Ensure no security groups allow egress from 0.0.0.0:0 to port -1

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 2 places
Medium Ensure ECS services do not have public IP addresses assigned to them automatically Security · 2 places

Ensure ECS services do not have public IP addresses assigned to them automatically

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 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 public facing ALB are protected by WAF Security · 1 place

Ensure public facing ALB are protected by WAF

Documentation

Where

Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled Security · 1 place

Ensure Postgres RDS as aws_db_instance has Query Logging enabled

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 1 place

Ensure an IAM role is attached to EC2 instance

Documentation

Where

Medium Ensure S3 buckets should have event notifications enabled Security · 1 place

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure access control lists for S3 buckets are disabled Security · 1 place

Ensure access control lists for S3 buckets are disabled

Documentation

Where

Medium Ensure AWS Load Balancers use strong ciphers Security · 1 place

Ensure AWS Load Balancers use strong ciphers

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 enhanced monitoring is enabled for Amazon RDS instances Security · 1 place

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 1 place

Ensure that detailed monitoring is enabled for EC2 instances

Documentation

Where

Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 1 place

Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled

Documentation

Where

Medium Ensure VPC subnets do not assign public IP by default Security · 1 place

Ensure VPC subnets do not assign public IP by default

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 1 place

Ensure that ALB drops HTTP headers

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 1 place

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 1 place

Ensure that S3 buckets are encrypted with KMS by default

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 the S3 bucket has access logging enabled Security · 1 place

Ensure the S3 bucket has access logging enabled

Documentation

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 1 place

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

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

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

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 access is controlled through SSO and not AWS IAM defined users Security · 1 place

Ensure access is controlled through SSO and not AWS IAM defined users

Documentation

Where

Medium Ensure that RDS instances have performance insights enabled Security · 1 place

Ensure that RDS instances have performance insights enabled

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 container insights are enabled on ECS cluster Security · 1 place

Ensure container insights are enabled on ECS cluster

Documentation

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 1 place

Ensure Instance Metadata Service Version 1 is not enabled

Documentation

Where

Medium EC2 instance should not have public IP. Security · 1 place

EC2 instance should not have public IP.

Documentation

Where

Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 1 place

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

Documentation

Where

Medium Missing Spot Instance Usage Cost · 1 place

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 Missing Cost and Usage Report Cost · 1 place

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 Load Balancer for Single Instance Cost · 1 place

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 ECS Task Definition Without CPU/Memory Limits Cost · 1 place

aws_ecs_task_definition without explicit cpu and memory limits. This leads to unpredictable cluster over-provisioning as the scheduler cannot bin-pack tasks efficiently.

How to fix

Set cpu and memory at the task level. Start with the minimum viable values and scale up based on CloudWatch Container Insights metrics.

Where

Low 2

Low Unassociated Elastic IP Cost · 1 place

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

Where

Low Missing AWS Budget Cost · 1 place

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.