InfraScan Cloud

Repository scan

Starguard

scheitelpunk/Starguard · branch main · scanned 25 Jun 2026 · 50 resources

DOverall
FSecurity
–Reliability · N/A
BCost
1,403findings · 0 critical, 568 high
—no cost findings with a savings estimate

High 1,339

High 244 known vulnerabilities in unknown@unknown (grafana/promtail:2.9.3) Security · 244 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/promtail:2.9.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-2023-47038 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-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 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-2026-48962 fixed in no fix yet
  • High CVE-2024-33602 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-30635 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2023-50387 fixed in no fix yet
  • High CVE-2023-50868 fixed in no fix yet
  • High CVE-2024-0553 fixed in no fix yet
  • High CVE-2024-0567 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • and 224 more
High 125 known vulnerabilities in unknown@unknown (grafana/grafana:10.2.2) Security · 125 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/grafana:10.2.2 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 GHSA-9763-4f94-gfch fixed in no fix yet
  • High CVE-2026-45022 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-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2023-47108 fixed in no fix yet
  • High CVE-2023-49568 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-21614 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-30153 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
  • and 105 more
High 119 known vulnerabilities in unknown@unknown (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 119 CVEs

How to fix

No fixed version of unknown is available yet. Check whether gcr.io/cadvisor/cadvisor:v0.47.2 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-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-2022-30635 fixed in no fix yet
  • High CVE-2023-2253 fixed in no fix yet
  • High CVE-2023-28840 fixed in no fix yet
  • High CVE-2023-39325 fixed in no fix yet
  • High CVE-2023-39325 fixed in no fix yet
  • High CVE-2023-44487 fixed in no fix yet
  • High CVE-2023-44487 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45287 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
  • and 99 more
High 106 known vulnerabilities in unknown@unknown (grafana/tempo:2.3.1) Security · 106 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/tempo:2.3.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-2026-39883 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2023-47108 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-21728 fixed in no fix yet
  • High CVE-2026-28377 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • and 86 more
High 100 known vulnerabilities in unknown@unknown (prom/prometheus:v2.48.0) Security · 100 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/prometheus:v2.48.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-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-45283 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
  • and 80 more
High 94 known vulnerabilities in unknown@unknown (grafana/loki:2.9.3) Security · 94 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/loki:2.9.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-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 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-32285 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • and 74 more
High 93 known vulnerabilities in unknown@unknown (prom/alertmanager:v0.26.0) Security · 93 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/alertmanager:v0.26.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-39325 fixed in no fix yet
  • High CVE-2023-39325 fixed in no fix yet
  • High CVE-2023-44487 fixed in no fix yet
  • High CVE-2023-45283 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
  • and 73 more
High 90 known vulnerabilities in unknown@unknown (jaegertracing/all-in-one:1.52) Security · 90 CVEs

How to fix

No fixed version of unknown is available yet. Check whether jaegertracing/all-in-one:1.52 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-45283 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
  • and 70 more
High 83 known vulnerabilities in unknown@unknown (prom/node-exporter:v1.7.0) Security · 83 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/node-exporter:v1.7.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-2025-52881 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 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
  • and 63 more
High 54 known vulnerabilities in unknown@unknown (oliver006/redis_exporter:v1.55.0) Security · 54 CVEs

How to fix

No fixed version of unknown is available yet. Check whether oliver006/redis_exporter:v1.55.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-45283 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-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-22871 fixed in no fix yet
  • High CVE-2024-24790 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • and 34 more
High 31 known vulnerabilities in unknown@unknown (prom/node-exporter:latest) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether prom/node-exporter: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

  • 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
  • High CVE-2026-33810 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-2026-46595 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-39835 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • Medium CVE-2026-32288 fixed in no fix yet
  • Medium CVE-2026-25681 fixed in no fix yet
  • and 11 more
High 16 known vulnerabilities in curl@8.4.0-r0 (grafana/grafana:10.2.2) Security · 16 CVEs

How to fix

Update curl from 8.4.0-r0 to 8.12.0-r0 or later in grafana/grafana:10.2.2. 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 8.12.0-r0); 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-0665 fixed in 8.12.0-r0
  • High CVE-2025-0725 fixed in 8.12.0-r0
  • High CVE-2024-6197 fixed in 8.9.0-r0
  • High CVE-2024-2398 fixed in 8.7.1-r0
  • Medium CVE-2024-6874 fixed in 8.9.0-r0
  • Medium CVE-2023-46219 fixed in 8.5.0-r0
  • Medium CVE-2024-0853 fixed in no fix yet
  • Medium CVE-2024-2379 fixed in 8.7.1-r0
  • Medium CVE-2023-46218 fixed in 8.5.0-r0
  • Medium CVE-2024-2466 fixed in 8.7.1-r0
  • Medium CVE-2024-7264 fixed in 8.9.1-r0
  • Medium CVE-2024-8096 fixed in 8.10.0-r0
  • Medium CVE-2024-9681 fixed in 8.11.0-r0
  • Low CVE-2024-11053 fixed in 8.11.1-r0
  • Low CVE-2025-0167 fixed in 8.12.0-r0
  • Low CVE-2024-2004 fixed in 8.7.1-r0
High 12 known vulnerabilities in openssl@3.1.3-r0 (grafana/grafana:10.2.2) Security · 12 CVEs

How to fix

Update openssl from 3.1.3-r0 to 3.1.4-r0 or later in grafana/grafana:10.2.2. 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.1.4-r0); 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-2023-5363 fixed in 3.1.4-r0
  • High CVE-2024-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2023-5678 fixed in 3.1.4-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 12 known vulnerabilities in openssl@3.1.3-r0 (grafana/tempo:2.3.1) Security · 12 CVEs

How to fix

Update openssl from 3.1.3-r0 to 3.1.4-r0 or later in grafana/tempo:2.3.1. 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.1.4-r0); 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-2023-5363 fixed in 3.1.4-r0
  • High CVE-2024-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2023-5678 fixed in 3.1.4-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 10 known vulnerabilities in openssl@3.1.4-r1 (grafana/loki:2.9.3) Security · 10 CVEs

How to fix

Update openssl from 3.1.4-r1 to 3.1.6-r0 or later in grafana/loki:2.9.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 3.1.6-r0); 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-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 9 known vulnerabilities in stdlib@1.20.10 (oliver006/redis_exporter:v1.55.0) Security · 9 CVEs

How to fix

Update stdlib from 1.20.10 to 1.22.7 or later in oliver006/redis_exporter:v1.55.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-2024-34155 fixed in 1.22.7
  • 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.19.9 (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 8 CVEs

How to fix

Update stdlib from 1.19.9 to 1.22.7 or later in gcr.io/cadvisor/cadvisor:v0.47.2. 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.3 (grafana/grafana:10.2.2) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/grafana:10.2.2. 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.3 (grafana/loki:2.9.3) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/loki:2.9.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.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.3 (grafana/promtail:2.9.3) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/promtail:2.9.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.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.3 (grafana/tempo:2.3.1) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/tempo:2.3.1. 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.4 (jaegertracing/all-in-one:1.52) Security · 8 CVEs

How to fix

Update stdlib from 1.21.4 to 1.22.7 or later in jaegertracing/all-in-one:1.52. 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.20.7 (prom/alertmanager:v0.26.0) Security · 8 CVEs

How to fix

Update stdlib from 1.20.7 to 1.22.7 or later in prom/alertmanager:v0.26.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.4 (prom/node-exporter:v1.7.0) Security · 8 CVEs

How to fix

Update stdlib from 1.21.4 to 1.22.7 or later in prom/node-exporter:v1.7.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.4 (prom/prometheus:v2.48.0) Security · 8 CVEs

How to fix

Update stdlib from 1.21.4 to 1.22.7 or later in prom/prometheus:v2.48.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 4 known vulnerabilities in crypto@0.1.0 (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 4 CVEs

How to fix

Update crypto from 0.1.0 to 0.43.0 or later in gcr.io/cadvisor/cadvisor:v0.47.2. 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 net@0.8.0 (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 4 CVEs

How to fix

Update net from 0.8.0 to 0.53.0 or later in gcr.io/cadvisor/cadvisor:v0.47.2. 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
  • Medium CVE-2023-44487 fixed in 0.17.0
High 4 known vulnerabilities in crypto@0.14.0 (grafana/grafana:10.2.2) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in grafana/grafana:10.2.2. 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.14.0 (grafana/loki:2.9.3) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in grafana/loki:2.9.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 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.14.0 (grafana/promtail:2.9.3) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in grafana/promtail:2.9.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 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.14.0 (grafana/tempo:2.3.1) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in grafana/tempo:2.3.1. 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.16.0 (jaegertracing/all-in-one:1.52) Security · 4 CVEs

How to fix

Update crypto from 0.16.0 to 0.43.0 or later in jaegertracing/all-in-one:1.52. 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.8.0 (prom/alertmanager:v0.26.0) Security · 4 CVEs

How to fix

Update crypto from 0.8.0 to 0.43.0 or later in prom/alertmanager:v0.26.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 stdlib@1.26.1 (prom/node-exporter:latest) Security · 4 CVEs

How to fix

Update stdlib from 1.26.1 to 1.26.3 or later in prom/node-exporter: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.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

  • High CVE-2026-33811 fixed in 1.26.3
  • High CVE-2026-39836 fixed in 1.26.3
  • High CVE-2026-42499 fixed in 1.26.3
  • High CVE-2026-42504 fixed in 1.26.4
High 4 known vulnerabilities in crypto@0.14.0 (prom/node-exporter:v1.7.0) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in prom/node-exporter:v1.7.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.14.0 (prom/prometheus:v2.48.0) Security · 4 CVEs

How to fix

Update crypto from 0.14.0 to 0.43.0 or later in prom/prometheus:v2.48.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.17.0 (grafana/loki:2.9.3) Security · 3 CVEs

How to fix

Update net from 0.17.0 to 0.53.0 or later in grafana/loki:2.9.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 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 3 known vulnerabilities in crypto@0.49.0 (prom/node-exporter:latest) Security · 3 CVEs

How to fix

Update crypto from 0.49.0 to 0.52.0 or later in prom/node-exporter: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 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 2 known vulnerabilities in musl@1.2.4-r2 (grafana/grafana:10.2.2) Security · 2 CVEs

How to fix

Update musl from 1.2.4-r2 to 1.2.4-r3 or later in grafana/grafana:10.2.2. 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.4-r3); 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.4-r3
  • High CVE-2025-26519 fixed in 1.2.4-r3
High 2 known vulnerabilities in net@0.17.0 (grafana/grafana:10.2.2) Security · 2 CVEs

How to fix

Update net from 0.17.0 to 0.53.0 or later in grafana/grafana:10.2.2. 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

and 12 more groups with 15 findings

Medium 60

Medium 4 known vulnerabilities in busybox@1.36.1-r2 (grafana/grafana:10.2.2) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r2 to 1.36.1-r7 or later in grafana/grafana:10.2.2. 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.36.1-r7); 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-42363 fixed in 1.36.1-r7
  • Medium CVE-2023-42364 fixed in 1.36.1-r7
  • Medium CVE-2023-42365 fixed in 1.36.1-r7
  • Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium 4 known vulnerabilities in busybox@1.36.1-r5 (grafana/loki:2.9.3) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r5 to 1.36.1-r7 or later in grafana/loki:2.9.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.36.1-r7); 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-42363 fixed in 1.36.1-r7
  • Medium CVE-2023-42364 fixed in 1.36.1-r7
  • Medium CVE-2023-42365 fixed in 1.36.1-r7
  • Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium 4 known vulnerabilities in busybox@1.36.1-r2 (grafana/tempo:2.3.1) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r2 to 1.36.1-r7 or later in grafana/tempo:2.3.1. 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.36.1-r7); 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-42363 fixed in 1.36.1-r7
  • Medium CVE-2023-42364 fixed in 1.36.1-r7
  • Medium CVE-2023-42365 fixed in 1.36.1-r7
  • Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 4 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 4 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 3 places
Medium 2 known vulnerabilities in net@0.17.0 (grafana/promtail:2.9.3) Security · 2 CVEs

How to fix

Update net from 0.17.0 to 0.36.0 or later in grafana/promtail:2.9.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 0.36.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-2025-22870 fixed in 0.36.0
  • Medium CVE-2026-25680 fixed in 0.55.0
Medium Ensure KMS key Policy is defined Security · 2 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 2 places
Medium 1 known vulnerability in busybox@1.35.0-r17 (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 1 CVE

How to fix

Update busybox from 1.35.0-r17 to 1.35.0-r18 or later in gcr.io/cadvisor/cadvisor:v0.47.2. 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 xz@5.2.5-r1 (gcr.io/cadvisor/cadvisor:v0.47.2) Security · 1 CVE

How to fix

No fixed version of xz is available yet. Check whether gcr.io/cadvisor/cadvisor:v0.47.2 needs xz 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-2020-22916 fixed in no fix yet
Medium 1 known vulnerability in gcc@12.2.1_git20220924-r10 (grafana/grafana:10.2.2) Security · 1 CVE

How to fix

No fixed version of gcc is available yet. Check whether grafana/grafana:10.2.2 needs gcc 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-2023-4039 fixed in no fix yet
Medium 1 known vulnerability in nghttp2@1.57.0-r0 (grafana/grafana:10.2.2) Security · 1 CVE

How to fix

No fixed version of nghttp2 is available yet. Check whether grafana/grafana:10.2.2 needs nghttp2 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-2024-28182 fixed in no fix yet
Medium 1 known vulnerability in net@0.17.0 (grafana/tempo:2.3.1) Security · 1 CVE

How to fix

Update net from 0.17.0 to 0.55.0 or later in grafana/tempo:2.3.1. 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.35.0-r17 (jaegertracing/all-in-one:1.52) 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.52. 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 net@0.52.0 (prom/node-exporter:latest) Security · 1 CVE

How to fix

Update net from 0.52.0 to 0.55.0 or later in prom/node-exporter: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 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.17.0 (prom/node-exporter:v1.7.0) Security · 1 CVE

How to fix

Update net from 0.17.0 to 0.55.0 or later in prom/node-exporter:v1.7.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 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 AWS ElastiCache Redis cluster with Multi-AZ Automatic Failover feature set to enabled Reliability · 1 place

Ensure AWS ElastiCache Redis cluster with Multi-AZ Automatic Failover feature set to enabled

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 S3 buckets should have event notifications enabled Security · 1 place

Ensure S3 buckets should have event notifications 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 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 that RDS instances have Multi-AZ enabled Reliability · 1 place

Ensure that RDS instances have Multi-AZ 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 ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure ECS Cluster logging is enabled and client to container communication uses CMK Security · 1 place

Ensure ECS Cluster logging is enabled and client to container communication uses CMK

Documentation

Where

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 AWS database instances have deletion protection enabled Reliability · 1 place

Ensure that AWS database instances have deletion protection enabled

Documentation

Where

Medium Ensure S3 lifecycle configuration sets period for aborting failed uploads Security · 1 place

Ensure S3 lifecycle configuration sets period for aborting failed uploads

Documentation

Where

Medium Ensure RDS Performance Insights are encrypted using KMS CMKs Security · 1 place

Ensure RDS Performance Insights are encrypted using KMS CMKs

Documentation

Where

Medium Ensure Terraform module sources use a commit hash Security · 1 place

Ensure Terraform module sources use a commit hash

Documentation

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

Low 4

Low 1 known vulnerability in v9@9.0.2 (grafana/grafana:10.2.2) Security · 1 CVE

How to fix

Update v9 from 9.0.2 to 9.6.3 or later in grafana/grafana:10.2.2. 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
Low 1 known vulnerability in pcre3@2%3A8.39-13 (grafana/promtail:2.9.3) Security · 1 CVE

How to fix

No fixed version of pcre3 is available yet. Check whether grafana/promtail:2.9.3 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 (grafana/promtail:2.9.3) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether grafana/promtail:2.9.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 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.