InfraScan Cloud

Repository scan

starguide

serverpod/starguide · branch main · scanned 25 Jun 2026 · 69 resources

COverall
DSecurity
–Reliability · N/A
BCost
754findings · 0 critical, 262 high
—no cost findings with a savings estimate

High 633

High 275 known vulnerabilities in unknown@unknown (redis:6.2.6) Security · 275 CVEs

How to fix

No fixed version of unknown is available yet. Check whether redis:6.2.6 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-0286 fixed in no fix yet
  • High CVE-2023-27561 fixed in no fix yet
  • High CVE-2023-47038 fixed in no fix yet
  • High CVE-2022-29458 fixed in no fix yet
  • 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-2022-1292 fixed in no fix yet
  • High CVE-2022-2068 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2024-2961 fixed in no fix yet
  • High CVE-2024-33601 fixed in no fix yet
  • High CVE-2025-31133 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • High CVE-2025-52881 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2023-0361 fixed in no fix yet
  • High CVE-2024-33602 fixed in no fix yet
  • High CVE-2025-69419 fixed in no fix yet
  • and 255 more
High 246 known vulnerabilities in unknown@unknown (postgres:16.3) Security · 246 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:16.3 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-5222 fixed in no fix yet
  • 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-2025-6965 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 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-2022-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • High CVE-2022-41722 fixed in no fix yet
  • and 226 more
High 73 known vulnerabilities in unknown@unknown (pgvector/pgvector:pg16) Security · 73 CVEs

How to fix

No fixed version of unknown is available yet. Check whether pgvector/pgvector:pg16 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 53 more
High 17 known vulnerabilities in stdlib@1.16.7 (redis:6.2.6) Security · 17 CVEs

How to fix

Update stdlib from 1.16.7 to 1.16.12 or later in redis:6.2.6. 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.16.12); 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-2021-44716 fixed in 1.16.12
  • High CVE-2022-23772 fixed in 1.16.14
  • High CVE-2022-24675 fixed in 1.17.9
  • High CVE-2022-28131 fixed in 1.17.12
  • High CVE-2022-30630 fixed in 1.17.12
  • High CVE-2022-30632 fixed in 1.17.12
  • High CVE-2022-30634 fixed in 1.17.11
  • High CVE-2022-30635 fixed in 1.17.12
  • High CVE-2022-32189 fixed in 1.17.13
  • High CVE-2024-34158 fixed in 1.22.7
  • 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 CVE-2025-4673 fixed in 1.23.10
High 14 known vulnerabilities in stdlib@1.18.2 (postgres:16.3) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in postgres:16.3. 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.18.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-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • High CVE-2024-34158 fixed in 1.22.7
  • 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 CVE-2025-4673 fixed in 1.23.10
High 6 known vulnerabilities in stdlib@1.24.6 (pgvector/pgvector:pg16) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in pgvector/pgvector:pg16. 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 e2scrub@.service (redis:6.2.6) Security · 1 CVE

How to fix

No fixed version of e2scrub is available yet. Check whether redis:6.2.6 needs e2scrub 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-2022-1304 fixed in no fix yet
High 1 known vulnerability in krb5@1.18.3-6%2Bdeb11u1 (redis:6.2.6) Security · 1 CVE

How to fix

Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u5 or later in redis:6.2.6. 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.18.3-6+deb11u5); 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-2024-37371 fixed in 1.18.3-6+deb11u5

Medium 105

Medium Ensure that auto Scaling groups that are associated with a load balancer are using Elastic Load Balancing health checks. Reliability · 6 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 4 places
Medium Ensure every security group and rule has a description Security · 4 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 4 places
Medium Ensure CloudFront distribution has a response headers policy attached Security · 3 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 3 places
Medium Ensure that S3 bucket has a Public Access block Security · 3 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 3 places
Medium Ensure S3 buckets should have event notifications enabled Security · 3 places
Medium Ensure access control lists for S3 buckets are disabled 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 all data stored in the S3 bucket have versioning enabled Reliability · 3 places
Medium Ensure HTTP HTTPS Target group defines Healthcheck Security · 3 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 3 places
Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 2 places
Medium Ensure public facing ALB are protected by WAF Security · 2 places
Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled Security · 2 places
Medium Ensure AWS CloudFront distribution is using secure SSL protocols for HTTPS communication Security · 2 places

Ensure AWS CloudFront distribution is using secure SSL protocols for HTTPS communication

Documentation

Where

Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 2 places
Medium Ensure AWS Load Balancers use strong ciphers Security · 2 places
Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher Security · 2 places
Medium Ensure CloudFront distribution has a default root object configured Security · 2 places
Medium Ensure CloudFront distributions should have origin failover configured Security · 2 places
Medium Ensure AWS CloudFront web distribution has geo restriction enabled Security · 2 places
Medium CloudFront Distribution should have WAF enabled Security · 2 places
Medium Ensure CloudFront distribution has Access Logging enabled Security · 2 places
Medium Ensure Terraform module sources use a commit hash Security · 2 places
Medium Missing S3 Lifecycle Policy Cost · 2 places

S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.

How to fix

Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.

Where

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 Ensure AWS CloudFront Distribution with S3 have Origin Access set to enabled Security · 1 place

Ensure AWS CloudFront Distribution with S3 have Origin Access set to enabled

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 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 that ALB drops HTTP headers Security · 1 place
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 1 place

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 1 place

Ensure that RDS instances have Multi-AZ enabled

Documentation

Where

Medium Ensure all data stored in the RDS is securely encrypted at rest Security · 1 place

Ensure all data stored in the RDS is securely encrypted at rest

Documentation

Where

Medium Ensure RDS database has IAM authentication enabled Security · 1 place

Ensure RDS database has IAM authentication enabled

Documentation

Where

Medium Ensure all data stored in RDS is not publicly accessible Security · 1 place

Ensure all data stored in RDS is not publicly accessible

Documentation

Where

and 12 more groups with 12 findings

Low 16

Low 7 known vulnerabilities in aa_ER@saaho (pgvector/pgvector:pg16) Security · 7 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether pgvector/pgvector:pg16 needs aa_ER 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-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • Low CVE-2019-1010024 fixed in no fix yet
  • Low CVE-2019-1010025 fixed in no fix yet
  • Low CVE-2019-9192 fixed in no fix yet
Low 1 known vulnerability in gcc-12@12.2.0-14%2Bdeb12u1 (pgvector/pgvector:pg16) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether pgvector/pgvector:pg16 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 perl@5.36.0-7%2Bdeb12u3 (pgvector/pgvector:pg16) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether pgvector/pgvector:pg16 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.40.1-2%2Bdeb12u2 (pgvector/pgvector:pg16) Security · 1 CVE

How to fix

No fixed version of sqlite3 is available yet. Check whether pgvector/pgvector:pg16 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.2.0-14 (postgres:16.3) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether postgres:16.3 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 perl@5.36.0-7%2Bdeb12u1 (postgres:16.3) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether postgres:16.3 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 pcre3@2%3A8.39-13 (redis:6.2.6) Security · 1 CVE

How to fix

No fixed version of pcre3 is available yet. Check whether redis:6.2.6 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%2Bdeb11u2 (redis:6.2.6) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether redis:6.2.6 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 sys@0.0.0-20210817142637-7d9622a276b7 (redis:6.2.6) Security · 1 CVE

How to fix

Update sys from 0.0.0-20210817142637-7d9622a276b7 to 0.44.0 or later in redis:6.2.6. 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.44.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

  • Low CVE-2026-39824 fixed in 0.44.0
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.