InfraScan Cloud

Repository scan

finding-a-bed-tonight

ccradle/finding-a-bed-tonight · branch main · scanned 25 Jun 2026 · 46 resources

DOverall
FSecurity
–Reliability · N/A
CCost
748findings · 0 critical, 286 high
$0.00–$46.35estimated savings per month, from the code

High 692

High 173 known vulnerabilities in unknown@unknown (quay.io/keycloak/keycloak:24.0.1) Security · 173 CVEs

How to fix

No fixed version of unknown is available yet. Check whether quay.io/keycloak/keycloak:24.0.1 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-2024-2700 fixed in no fix yet
  • High CVE-2024-10039 fixed in no fix yet
  • High CVE-2024-10270 fixed in no fix yet
  • High CVE-2024-2419 fixed in no fix yet
  • High CVE-2024-7341 fixed in no fix yet
  • High CVE-2026-7571 fixed in no fix yet
  • High GHSA-5rxp-2rhr-qwqv fixed in no fix yet
  • High GHSA-j76j-rqwj-jmvv fixed in no fix yet
  • High CVE-2026-3872 fixed in no fix yet
  • High CVE-2026-42584 fixed in no fix yet
  • High CVE-2024-12397 fixed in no fix yet
  • High CVE-2024-1249 fixed in no fix yet
  • High CVE-2026-4282 fixed in no fix yet
  • High CVE-2024-29857 fixed in no fix yet
  • High CVE-2024-4540 fixed in no fix yet
  • High CVE-2025-24970 fixed in no fix yet
  • High CVE-2026-33870 fixed in no fix yet
  • High CVE-2026-42198 fixed in no fix yet
  • High CVE-2026-42579 fixed in no fix yet
  • High CVE-2026-42583 fixed in no fix yet
  • and 153 more
High 138 known vulnerabilities in unknown@unknown (otel/opentelemetry-collector-contrib:0.96.0) Security · 138 CVEs

How to fix

No fixed version of unknown is available yet. Check whether otel/opentelemetry-collector-contrib:0.96.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-24051 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 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-2025-52881 fixed in no fix yet
  • High CVE-2026-39883 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22868 fixed in no fix yet
  • High CVE-2025-22869 fixed in no fix yet
  • High CVE-2025-29786 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
  • and 118 more
High 90 known vulnerabilities in unknown@unknown (prom/prometheus:v2.51.0) Security · 90 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/prometheus:v2.51.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-24051 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-39883 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22868 fixed in no fix yet
  • High CVE-2025-22869 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
  • and 70 more
High 89 known vulnerabilities in unknown@unknown (jaegertracing/all-in-one:1.55) Security · 89 CVEs

How to fix

No fixed version of unknown is available yet. Check whether jaegertracing/all-in-one:1.55 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-2022-30635 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22869 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-39829 fixed in no fix yet
  • and 69 more
High 83 known vulnerabilities in unknown@unknown (prom/alertmanager:v0.27.0) Security · 83 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/alertmanager:v0.27.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-2022-30635 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22868 fixed in no fix yet
  • High CVE-2025-22869 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-39829 fixed in no fix yet
  • and 63 more
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 16 known vulnerabilities in LC_ADDRESS@unknown (quay.io/keycloak/keycloak:24.0.1) Security · 16 CVEs

How to fix

No fixed version of LC_ADDRESS is available yet. Check whether quay.io/keycloak/keycloak:24.0.1 needs LC_ADDRESS 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-4046 fixed in no fix yet
  • High CVE-2024-33599 fixed in no fix yet
  • High CVE-2023-4911 fixed in no fix yet
  • High CVE-2024-2961 fixed in no fix yet
  • High CVE-2026-0861 fixed in no fix yet
  • Medium CVE-2025-8058 fixed in no fix yet
  • Medium CVE-2024-33600 fixed in no fix yet
  • Medium CVE-2026-0915 fixed in no fix yet
  • Medium CVE-2025-0395 fixed in no fix yet
  • Medium CVE-2025-5702 fixed in no fix yet
  • Medium CVE-2023-4806 fixed in no fix yet
  • Medium CVE-2023-4813 fixed in no fix yet
  • Medium CVE-2025-4802 fixed in no fix yet
  • Low CVE-2024-33601 fixed in no fix yet
  • Low CVE-2024-33602 fixed in no fix yet
  • Low CVE-2025-15281 fixed in no fix yet
High 9 known vulnerabilities in stdlib@1.22.0 (jaegertracing/all-in-one:1.55) Security · 9 CVEs

How to fix

Update stdlib from 1.22.0 to 1.22.7 or later in jaegertracing/all-in-one:1.55. 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.22.7); 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-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-2024-24788 fixed in 1.22.3
  • Medium CVE-2025-4673 fixed in 1.23.10
High 9 known vulnerabilities in stdlib@1.22.1 (prom/prometheus:v2.51.0) Security · 9 CVEs

How to fix

Update stdlib from 1.22.1 to 1.22.7 or later in prom/prometheus:v2.51.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.22.7); 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-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-2024-24788 fixed in 1.22.3
  • Medium CVE-2025-4673 fixed in 1.23.10
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 8 known vulnerabilities in stdlib@1.21.7 (otel/opentelemetry-collector-contrib:0.96.0) Security · 8 CVEs

How to fix

Update stdlib from 1.21.7 to 1.22.7 or later in otel/opentelemetry-collector-contrib:0.96.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.22.7); 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-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 8 known vulnerabilities in stdlib@1.21.7 (prom/alertmanager:v0.27.0) Security · 8 CVEs

How to fix

Update stdlib from 1.21.7 to 1.22.7 or later in prom/alertmanager:v0.27.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.22.7); 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-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 (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 4 known vulnerabilities in crypto@0.19.0 (jaegertracing/all-in-one:1.55) Security · 4 CVEs

How to fix

Update crypto from 0.19.0 to 0.43.0 or later in jaegertracing/all-in-one:1.55. 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 4 known vulnerabilities in crypto@0.20.0 (otel/opentelemetry-collector-contrib:0.96.0) Security · 4 CVEs

How to fix

Update crypto from 0.20.0 to 0.43.0 or later in otel/opentelemetry-collector-contrib:0.96.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.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 4 known vulnerabilities in crypto@0.18.0 (prom/alertmanager:v0.27.0) Security · 4 CVEs

How to fix

Update crypto from 0.18.0 to 0.43.0 or later in prom/alertmanager:v0.27.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.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 4 known vulnerabilities in crypto@0.21.0 (prom/prometheus:v2.51.0) Security · 4 CVEs

How to fix

Update crypto from 0.21.0 to 0.43.0 or later in prom/prometheus:v2.51.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.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 3 known vulnerabilities in net@0.22.0 (prom/prometheus:v2.51.0) Security · 3 CVEs

How to fix

Update net from 0.22.0 to 0.53.0 or later in prom/prometheus:v2.51.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-2025-22870 fixed in 0.36.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 2 known vulnerabilities in net@0.21.0 (jaegertracing/all-in-one:1.55) Security · 2 CVEs

How to fix

Update net from 0.21.0 to 0.53.0 or later in jaegertracing/all-in-one:1.55. 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 musl@1.2.3-r3 (jaegertracing/all-in-one:1.55) Security · 1 CVE

How to fix

Update musl from 1.2.3-r3 to 1.2.3-r4 or later in jaegertracing/all-in-one:1.55. 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.3-r4); 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.3-r4
High 1 known vulnerability in v4@4.18.1 (otel/opentelemetry-collector-contrib:0.96.0) Security · 1 CVE

How to fix

Update v4 from 4.18.1 to 4.18.2 or later in otel/opentelemetry-collector-contrib:0.96.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 4.18.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

  • High CVE-2024-27304 fixed in 4.18.2
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 51

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 5 places
Medium Missing Cost and Usage Report Cost · 4 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 Ensure that CloudWatch Log Group is encrypted by KMS Security · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 2 places
Medium 1 known vulnerability in busybox@1.35.0-r17 (jaegertracing/all-in-one:1.55) Security · 1 CVE

How to fix

Update busybox from 1.35.0-r17 to 1.35.0-r18 or later in jaegertracing/all-in-one:1.55. 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.35.0-r18); 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-2023-42366 fixed in 1.35.0-r18
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 net@0.21.0 (otel/opentelemetry-collector-contrib:0.96.0) Security · 1 CVE

How to fix

Update net from 0.21.0 to 0.55.0 or later in otel/opentelemetry-collector-contrib:0.96.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.55.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

  • Medium CVE-2026-25680 fixed in 0.55.0
Medium 1 known vulnerability in net@0.20.0 (prom/alertmanager:v0.27.0) Security · 1 CVE

How to fix

Update net from 0.20.0 to 0.55.0 or later in prom/alertmanager:v0.27.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.55.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

  • Medium CVE-2026-25680 fixed in 0.55.0
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
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 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 RDS instance with copy tags to snapshots is enabled Security · 1 place

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure that an S3 bucket has a lifecycle configuration Security · 1 place

Ensure that an S3 bucket has a lifecycle configuration

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 AWS RDS database instance configured with encryption in transit Security · 1 place

Ensure AWS RDS database instance configured with encryption in transit

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 DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 1 place

Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 1 place

Ensure that ALB drops HTTP headers

Documentation

Where

Medium Ensure that Amazon ElastiCache Redis clusters have automatic backup turned on Reliability · 1 place

Ensure that Amazon ElastiCache Redis clusters have automatic backup turned on

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 RDS database has IAM authentication enabled Security · 1 place

Ensure RDS database has IAM authentication 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 ALB protocol is HTTPS Security · 1 place
Medium Ensure DB instance gets all minor upgrades automatically Security · 1 place

Ensure DB instance gets all minor upgrades automatically

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 that RDS instances have performance insights enabled Security · 1 place

Ensure that RDS instances have performance insights enabled

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 MSK Cluster encryption in rest and transit is enabled Security · 1 place

Ensure MSK Cluster encryption in rest and transit is enabled

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 S3 Lifecycle Policy Cost · 1 place

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 · 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

Low 5

Low Missing AWS Budget Cost · 4 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 v9@9.4.0 (otel/opentelemetry-collector-contrib:0.96.0) Security · 1 CVE

How to fix

Update v9 from 9.4.0 to 9.6.3 or later in otel/opentelemetry-collector-contrib:0.96.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 9.6.3); 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-2025-29923 fixed in 9.6.3

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.