InfraScan Cloud

Repository scan

warden

stephnangue/warden · branch main · scanned 25 Jun 2026 · 1,225 resources

FOverall
FSecurity
–Reliability · N/A
FCost
2,307findings · 0 critical, 386 high
$811–$833estimated savings per month, from the code

High 779

High 104 known vulnerabilities in unknown@unknown (hashicorp/vault:1.18) Security · 104 CVEs

How to fix

No fixed version of unknown is available yet. Check whether hashicorp/vault:1.18 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-44503 fixed in no fix yet
  • High CVE-2025-5999 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-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-2025-6203 fixed in no fix yet
  • High CVE-2025-63811 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-32286 fixed in no fix yet
  • and 84 more
High 97 known vulnerabilities in unknown@unknown (oryd/hydra:v2.2) Security · 97 CVEs

How to fix

No fixed version of unknown is available yet. Check whether oryd/hydra:v2.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-24051 fixed in no fix yet
  • High CVE-2026-33504 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-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-32286 fixed in no fix yet
  • and 77 more
High 63 known vulnerabilities in unknown@unknown (mysql:8.0) Security · 63 CVEs

How to fix

No fixed version of unknown is available yet. Check whether mysql:8.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-27459 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 GHSA-537c-gmf6-5ccf fixed in no fix yet
  • High CVE-2026-44431 fixed in no fix yet
  • High CVE-2026-44432 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-4877 fixed in no fix yet
  • Medium CVE-2025-4877 fixed in no fix yet
  • Medium CVE-2025-4878 fixed in no fix yet
  • Medium CVE-2025-4878 fixed in no fix yet
  • and 43 more
High Old Generation Instance Cost · 61 places

Usage of old generation EC2 instances (e.g., t2, m3, c4, r3). Newer generations are often cheaper and faster.

How to fix

Upgrade to current generation instances (e.g., t3, m5, c5, r5).

Where

High 44 known vulnerabilities in unknown@unknown (code.forgejo.org/forgejo/runner:12.8.0) Security · 44 CVEs

How to fix

No fixed version of unknown is available yet. Check whether code.forgejo.org/forgejo/runner:12.8.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-15558 fixed in no fix yet
  • High CVE-2026-45022 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-29181 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
  • High CVE-2026-44973 fixed in no fix yet
  • High CVE-2026-34040 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
  • and 24 more
High 40 known vulnerabilities in unknown@unknown (openbao/openbao:2.5.3) Security · 40 CVEs

How to fix

No fixed version of unknown is available yet. Check whether openbao/openbao:2.5.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-2026-45808 fixed in no fix yet
  • High CVE-2024-7594 fixed in no fix yet
  • High CVE-2025-59043 fixed in no fix yet
  • High CVE-2025-64761 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-2024-9180 fixed in no fix yet
  • High CVE-2024-8185 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-32952 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-39835 fixed in no fix yet
  • and 20 more
High 37 known vulnerabilities in unknown@unknown (python:3.11-slim) Security · 37 CVEs

How to fix

No fixed version of unknown is available yet. Check whether python:3.11-slim 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-24049 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-48959 fixed in no fix yet
  • High CVE-2026-12087 fixed in no fix yet
  • Medium CVE-2025-45582 fixed in no fix yet
  • Medium CVE-2026-3219 fixed in no fix yet
  • Medium CVE-2026-6357 fixed in no fix yet
  • Medium CVE-2025-15649 fixed in no fix yet
  • Medium CVE-2026-8643 fixed in no fix yet
  • Medium CVE-2025-8869 fixed in no fix yet
  • Medium CVE-2026-7010 fixed in no fix yet
  • Low CVE-2005-2541 fixed in no fix yet
  • Low CVE-2007-5686 fixed in no fix yet
  • Low CVE-2010-0928 fixed in no fix yet
  • Low CVE-2010-4756 fixed in no fix yet
  • Low CVE-2011-3374 fixed in no fix yet
  • Low CVE-2011-4116 fixed in no fix yet
  • Low CVE-2013-4392 fixed in no fix yet
  • Low CVE-2017-18018 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • and 17 more
High 35 known vulnerabilities in unknown@unknown (ghcr.io/stephnangue/warden:v0.16.0) Security · 35 CVEs

How to fix

No fixed version of unknown is available yet. Check whether ghcr.io/stephnangue/warden:v0.16.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-27137 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-39829 fixed in no fix yet
  • High CVE-2026-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-2020-8911 fixed in no fix yet
  • and 15 more
High 31 known vulnerabilities in unknown@unknown (postgres:15-alpine) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:15-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 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 24 known vulnerabilities in unknown@unknown (ghostunnel/ghostunnel:v1.10.0-distroless) Security · 24 CVEs

How to fix

No fixed version of unknown is available yet. Check whether ghostunnel/ghostunnel:v1.10.0-distroless 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-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-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-25681 fixed in no fix yet
  • Medium CVE-2026-27136 fixed in no fix yet
  • Medium CVE-2026-39823 fixed in no fix yet
  • Medium CVE-2026-39826 fixed in no fix yet
  • Medium CVE-2026-42502 fixed in no fix yet
  • Medium CVE-2026-42506 fixed in no fix yet
  • and 4 more
High 22 known vulnerabilities in openssl@3.5.5-r0 (code.forgejo.org/forgejo/runner:12.8.0) Security · 22 CVEs

How to fix

Update openssl from 3.5.5-r0 to 3.5.7-r0 or later in code.forgejo.org/forgejo/runner:12.8.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 3.5.7-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-2026-34181 fixed in 3.5.7-r0
  • High CVE-2026-28388 fixed in 3.5.6-r0
  • High CVE-2026-28389 fixed in 3.5.6-r0
  • High CVE-2026-28390 fixed in 3.5.6-r0
  • High CVE-2026-31790 fixed in 3.5.6-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-28387 fixed in 3.5.6-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • High CVE-2026-31789 fixed in 3.5.6-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Medium CVE-2026-2673 fixed in 3.5.6-r0
  • and 2 more
High 19 known vulnerabilities in openssl@3.3.3-r0 (hashicorp/vault:1.18) Security · 19 CVEs

How to fix

Update openssl from 3.3.3-r0 to 3.3.6-r0 or later in hashicorp/vault:1.18. 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.3.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-2025-69419 fixed in 3.3.6-r0
  • High CVE-2025-69420 fixed in 3.3.6-r0
  • High CVE-2025-69421 fixed in 3.3.6-r0
  • High CVE-2025-9230 fixed in 3.3.5-r0
  • High CVE-2026-28388 fixed in 3.3.7-r0
  • High CVE-2026-28389 fixed in 3.3.7-r0
  • High CVE-2026-28390 fixed in 3.3.7-r0
  • High CVE-2026-31790 fixed in 3.3.7-r0
  • High CVE-2026-28387 fixed in 3.3.7-r0
  • High CVE-2025-15467 fixed in 3.3.6-r0
  • High CVE-2026-31789 fixed in 3.3.7-r0
  • Medium CVE-2025-69418 fixed in 3.3.6-r0
  • Medium CVE-2025-68160 fixed in 3.3.6-r0
  • Medium CVE-2026-22796 fixed in 3.3.6-r0
  • Medium CVE-2026-22795 fixed in 3.3.6-r0
  • Medium CVE-2025-15468 fixed in 3.3.6-r0
  • Medium CVE-2025-66199 fixed in 3.3.6-r0
  • Medium CVE-2025-9232 fixed in 3.3.5-r0
  • Medium CVE-2025-9231 fixed in 3.3.5-r0
High 15 known vulnerabilities in curl@8.17.0-r1 (code.forgejo.org/forgejo/runner:12.8.0) Security · 15 CVEs

How to fix

Update curl from 8.17.0-r1 to 8.19.0-r0 or later in code.forgejo.org/forgejo/runner:12.8.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 8.19.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-2026-3805 fixed in 8.19.0-r0
  • High CVE-2026-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • Medium CVE-2025-14524 fixed in 8.19.0-r0
  • Medium CVE-2025-14819 fixed in 8.19.0-r0
  • Medium CVE-2026-3783 fixed in 8.19.0-r0
  • 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-2025-14017 fixed in 8.19.0-r0
  • Medium CVE-2026-1965 fixed in 8.19.0-r0
  • Medium CVE-2026-3784 fixed in 8.19.0-r0
  • Medium CVE-2026-5545 fixed in no fix yet
High 15 known vulnerabilities in openssl@3.5.6-r0 (codeberg.org/forgejo/forgejo:15) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in codeberg.org/forgejo/forgejo:15. 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.5.7-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-2026-34181 fixed in 3.5.7-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 15 known vulnerabilities in openssl@3.5.6-r0 (openbao/openbao:2.5.3) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in openbao/openbao:2.5.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.5.7-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-2026-34181 fixed in 3.5.7-r0
  • High CVE-2026-34180 fixed in 3.5.7-r0
  • High CVE-2026-34183 fixed in 3.5.7-r0
  • High CVE-2026-42764 fixed in 3.5.7-r0
  • High CVE-2026-45445 fixed in 3.5.7-r0
  • High CVE-2026-9076 fixed in 3.5.7-r0
  • High CVE-2026-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 8 known vulnerabilities in curl@8.19.0-r0 (codeberg.org/forgejo/forgejo:15) Security · 8 CVEs

How to fix

No fixed version of curl is available yet. Check whether codeberg.org/forgejo/forgejo:15 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 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.5 (oryd/hydra:v2.2) Security · 8 CVEs

How to fix

Update stdlib from 1.21.5 to 1.22.7 or later in oryd/hydra:v2.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 7 known vulnerabilities in unknown@unknown (ghcr.io/spiffe/spire-agent:1.15.1) Security · 7 CVEs

How to fix

No fixed version of unknown is available yet. Check whether ghcr.io/spiffe/spire-agent:1.15.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-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-34040 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • Medium CVE-2026-41568 fixed in no fix yet
  • Medium CVE-2026-27145 fixed in no fix yet
  • Medium CVE-2026-33997 fixed in no fix yet
High 7 known vulnerabilities in stdlib@1.23.6 (hashicorp/vault:1.18) Security · 7 CVEs

How to fix

Update stdlib from 1.23.6 to 1.25.8 or later in hashicorp/vault:1.18. 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
  • Medium CVE-2025-4673 fixed in 1.23.10
High 7 known vulnerabilities in openssl@3.1.4-r5 (oryd/hydra:v2.2) Security · 7 CVEs

How to fix

Update openssl from 3.1.4-r5 to 3.1.6-r0 or later in oryd/hydra:v2.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.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-2511 fixed in 3.1.4-r6
High 6 known vulnerabilities in stdlib@1.24.6 (mysql:8.0) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in mysql:8.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.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 6 known vulnerabilities in stdlib@1.24.6 (postgres:15-alpine) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:15-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 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 5 known vulnerabilities in openssh@10.2_p1-r0 (codeberg.org/forgejo/forgejo:15) Security · 5 CVEs

How to fix

No fixed version of openssh is available yet. Check whether codeberg.org/forgejo/forgejo:15 needs openssh 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-35385 fixed in no fix yet
  • Medium CVE-2026-35414 fixed in no fix yet
  • Low CVE-2026-35388 fixed in no fix yet
  • Low CVE-2026-35387 fixed in no fix yet
  • Low CVE-2026-35386 fixed in no fix yet
High 5 known vulnerabilities in stdlib@1.26.0 (ghcr.io/stephnangue/warden:v0.16.0) Security · 5 CVEs

How to fix

Update stdlib from 1.26.0 to 1.26.1 or later in ghcr.io/stephnangue/warden:v0.16.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.26.1); 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.26.1
  • 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 stdlib@1.25.8 (code.forgejo.org/forgejo/runner:12.8.0) Security · 4 CVEs

How to fix

Update stdlib from 1.25.8 to 1.25.10 or later in code.forgejo.org/forgejo/runner:12.8.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.25.10); 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.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
High 4 known vulnerabilities in stdlib@1.26.2 (ghostunnel/ghostunnel:v1.10.0-distroless) Security · 4 CVEs

How to fix

Update stdlib from 1.26.2 to 1.26.3 or later in ghostunnel/ghostunnel:v1.10.0-distroless. 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.32.0 (hashicorp/vault:1.18) Security · 4 CVEs

How to fix

Update crypto from 0.32.0 to 0.43.0 or later in hashicorp/vault:1.18. 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.25.9 (openbao/openbao:2.5.3) Security · 4 CVEs

How to fix

Update stdlib from 1.25.9 to 1.25.10 or later in openbao/openbao:2.5.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.25.10); 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.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
High 4 known vulnerabilities in crypto@0.17.0 (oryd/hydra:v2.2) Security · 4 CVEs

How to fix

Update crypto from 0.17.0 to 0.43.0 or later in oryd/hydra:v2.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 3 known vulnerabilities in crypto@0.45.0 (code.forgejo.org/forgejo/runner:12.8.0) Security · 3 CVEs

How to fix

Update crypto from 0.45.0 to 0.52.0 or later in code.forgejo.org/forgejo/runner:12.8.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.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 3 known vulnerabilities in crypto@0.51.0 (ghcr.io/stephnangue/warden:v0.16.0) Security · 3 CVEs

How to fix

Update crypto from 0.51.0 to 0.52.0 or later in ghcr.io/stephnangue/warden:v0.16.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.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 3 known vulnerabilities in crypto@0.49.0 (ghostunnel/ghostunnel:v1.10.0-distroless) Security · 3 CVEs

How to fix

Update crypto from 0.49.0 to 0.52.0 or later in ghostunnel/ghostunnel:v1.10.0-distroless. 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 3 known vulnerabilities in net@0.34.0 (hashicorp/vault:1.18) Security · 3 CVEs

How to fix

Update net from 0.34.0 to 0.53.0 or later in hashicorp/vault:1.18. 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.47.0 (openbao/openbao:2.5.3) Security · 3 CVEs

How to fix

Update crypto from 0.47.0 to 0.52.0 or later in openbao/openbao:2.5.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.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 EBS Provisioned IOPS (io1/io2) Cost · 3 places

EBS volume using Provisioned IOPS (io1/io2) type. These are very expensive — io2 costs 56× more than gp3 per GB plus per-IOPS charges.

How to fix

Verify if gp3 can meet performance requirements at a lower cost.

Where

High 2 known vulnerabilities in musl@1.2.5-r21 (code.forgejo.org/forgejo/runner:12.8.0) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r21 to 1.2.5-r23 or later in code.forgejo.org/forgejo/runner:12.8.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.2.5-r23); 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-40200 fixed in 1.2.5-r23
  • Medium CVE-2026-6042 fixed in 1.2.5-r22
High 2 known vulnerabilities in sqlite@3.51.2-r0 (codeberg.org/forgejo/forgejo:15) Security · 2 CVEs

How to fix

No fixed version of sqlite is available yet. Check whether codeberg.org/forgejo/forgejo:15 needs sqlite 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-11822 fixed in no fix yet
  • High CVE-2026-11824 fixed in no fix yet

and 10 more groups with 11 findings

Medium 1,504

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 67 places
Medium Ensure that S3 bucket has a Public Access block Security · 66 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 65 places
Medium Ensure the S3 bucket has access logging enabled Security · 65 places
Medium Ensure S3 buckets should have event notifications enabled Security · 62 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 59 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 58 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 57 places
Medium Base64 High Entropy String Security · 55 places
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 53 places

Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK

Documentation

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 52 places
Medium Ensure that EC2 is EBS optimized Security · 52 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 51 places

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 51 places

Ensure DynamoDB point in time recovery (backup) is enabled

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 50 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 47 places

Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted

Documentation

Where

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 43 places

Ensure that AWS Lambda function is configured for function-level concurrent execution limit

Documentation

Where

Medium Ensure AWS Lambda function is configured to validate code-signing Security · 43 places

Ensure AWS Lambda function is configured to validate code-signing

Documentation

Where

Medium Ensure all data stored in the SNS topic is encrypted Security · 42 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 41 places

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that AWS Lambda function is configured inside a VPC Security · 41 places

Ensure that AWS Lambda function is configured inside a VPC

Documentation

Where

Medium X-Ray tracing is enabled for Lambda Security · 41 places

X-Ray tracing is enabled for Lambda

Documentation

Where

Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 24 places

Ensure Secrets Manager secrets should have automatic rotation enabled

Documentation

Where

Medium AWS SSM Parameter should be Encrypted Security · 23 places

AWS SSM Parameter should be Encrypted

Documentation

Where

Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 23 places

Ensure that Secrets Manager secret is encrypted using KMS CMK

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 18 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 18 places
Medium Ensure that CloudWatch Log Group specifies retention days Security · 12 places
Medium CloudWatch Logs Without Retention Cost · 12 places
Medium Missing Cost and Usage Report Cost · 12 places
Medium Basic Auth Credentials Security · 11 places
Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 10 places
Medium Ensure that Security Groups are attached to another resource Security · 7 places
Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 7 places
Medium Ensure SSM parameters are using KMS CMK Security · 6 places
Medium Ensure IAM policies does not allow data exfiltration Security · 5 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 5 places
Medium DynamoDB Provisioned Mode Cost · 5 places
Medium 4 known vulnerabilities in libssh-config@0.10.4-17.el9_7 (mysql:8.0) Security · 4 CVEs

How to fix

Update libssh-config from 0.10.4-17.el9_7 to 0:0.10.4-18.el9 or later in mysql:8.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:0.10.4-18.el9); 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-8114 fixed in 0:0.10.4-18.el9
  • Medium CVE-2026-0966 fixed in 0:0.10.4-18.el9
  • Medium CVE-2026-0967 fixed in 0:0.10.4-18.el9
  • Medium CVE-2026-0968 fixed in 0:0.10.4-18.el9
Medium 4 known vulnerabilities in busybox@1.36.1-r5 (oryd/hydra:v2.2) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r5 to 1.36.1-r7 or later in oryd/hydra:v2.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

and 87 more groups with 137 findings

Low 24

Low Missing AWS Budget Cost · 12 places
Low Large Root Volume Cost · 3 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

Low 2 known vulnerabilities in expat@2.7.5-r0 (code.forgejo.org/forgejo/runner:12.8.0) Security · 2 CVEs

How to fix

Update expat from 2.7.5-r0 to 2.8.1-r0 or later in code.forgejo.org/forgejo/runner:12.8.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 2.8.1-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

  • Low CVE-2026-41080 fixed in 2.8.1-r0
  • Low CVE-2026-45186 fixed in 2.8.1-r0
Low 2 known vulnerabilities in expat@2.7.5-r0 (codeberg.org/forgejo/forgejo:15) Security · 2 CVEs

How to fix

Update expat from 2.7.5-r0 to 2.8.1-r0 or later in codeberg.org/forgejo/forgejo:15. 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 2.8.1-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

  • Low CVE-2026-41080 fixed in 2.8.1-r0
  • Low CVE-2026-45186 fixed in 2.8.1-r0
Low SQS Max Message Retention Cost · 2 places

SQS queue configured with the maximum 14-day (1209600 s) message retention. On high-volume queues this inflates storage costs and may indicate unprocessed message buildup.

How to fix

Set retention to the minimum business requirement (e.g., 1–4 days for most queues) and alert on queue depth to catch processing failures early.

Where

Low 1 known vulnerability in gnupg@2.4.9-r0 (codeberg.org/forgejo/forgejo:15) Security · 1 CVE

How to fix

No fixed version of gnupg is available yet. Check whether codeberg.org/forgejo/forgejo:15 needs gnupg 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-30258 fixed in no fix yet
Low Unassociated Elastic IP Cost · 1 place

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

How to fix

Release unattached Elastic IPs.

Where

Low EC2 Detailed Monitoring Cost · 1 place

Detailed monitoring for EC2 instances incurs extra costs.

How to fix

Disable detailed monitoring if standard 5-minute metrics are sufficient.

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.