InfraScan Cloud

Repository scan

Distributed_Microservices_Backend

alimx07/Distributed_Microservices_Backend · branch main · scanned 25 Jun 2026 · 191 resources

COverall
DSecurity
–Reliability · N/A
BCost
379findings · 0 critical, 28 high
$7.44–$56.83estimated savings per month, from the code

High 52

High 40 known vulnerabilities in unknown@unknown (quay.io/coreos/etcd:v3.6.7) Security · 40 CVEs

How to fix

No fixed version of unknown is available yet. Check whether quay.io/coreos/etcd:v3.6.7 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-24051 fixed in no fix yet
  • High CVE-2026-39883 fixed in no fix yet
  • High CVE-2025-61726 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-39829 fixed in no fix yet
  • High CVE-2026-33186 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
  • High CVE-2026-39821 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • High CVE-2026-46595 fixed in no fix yet
  • Medium CVE-2025-47914 fixed in no fix yet
  • Medium CVE-2025-58181 fixed in no fix yet
  • and 20 more
High 5 known vulnerabilities in stdlib@1.24.11 (quay.io/coreos/etcd:v3.6.7) Security · 5 CVEs

How to fix

Update stdlib from 1.24.11 to 1.25.8 or later in quay.io/coreos/etcd:v3.6.7. 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
High 4 known vulnerabilities in crypto@0.42.0 (quay.io/coreos/etcd:v3.6.7) Security · 4 CVEs

How to fix

Update crypto from 0.42.0 to 0.43.0 or later in quay.io/coreos/etcd:v3.6.7. 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.43.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-2025-47913 fixed in 0.43.0
  • 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 2 known vulnerabilities in net@0.45.0 (quay.io/coreos/etcd:v3.6.7) Security · 2 CVEs

How to fix

Update net from 0.45.0 to 0.53.0 or later in quay.io/coreos/etcd:v3.6.7. 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 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 325

Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 15 places
Medium Containers should not run with allowPrivilegeEscalation Security · 15 places
Medium Use read-only filesystem for containers where possible Security · 15 places
Medium Minimize the admission of root containers Security · 15 places
Medium Minimize the admission of containers with the NET_RAW capability Security · 15 places
Medium Apply security context to your pods and containers Security · 15 places
Medium Apply security context to your containers Security · 15 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 15 places
Medium Minimize the admission of containers with capabilities assigned Security · 15 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 15 places
Medium Containers should run as a high UID to avoid host conflict Security · 15 places
Medium Image should use digest Security · 15 places
Medium CPU requests should be set Reliability · 10 places
Medium CPU limits should be set Reliability · 10 places
Medium Memory requests should be set Reliability · 10 places
Medium Memory limits should be set Reliability · 10 places
Medium Liveness Probe Should be Configured Reliability · 10 places
Medium Readiness Probe Should be Configured Reliability · 10 places
Medium Image Tag should be fixed - not latest or blank Security · 9 places
Medium Ensure top-level permissions are not set to write-all Security · 7 places
Medium Image Pull Policy should be Always Security · 6 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 5 places
Medium Prefer using secrets as files over secrets as environment variables Security · 5 places
Medium Ensure Terraform module sources use a commit hash Security · 3 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 2 places
Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 2 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 2 places
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 2 places

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 · 2 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 2 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 2 places
Medium Ensure RDS database has IAM authentication enabled 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 DB instance gets all minor upgrades automatically Security · 2 places
Medium Ensure that AWS database instances have deletion protection enabled Reliability · 2 places
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit Security · 2 places

Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit

Documentation

Where

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 that RDS instances have performance insights enabled Security · 2 places
Medium Ensure that a user for the container has been created 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

and 19 more groups with 19 findings

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.