InfraScan Cloud

Repository scan

devmind

lentrekin1/devmind · branch main · scanned 25 Jun 2026 · 103 resources

COverall
CSecurity
–Reliability · N/A
BCost
176findings · 0 critical, 53 high
—no cost findings with a savings estimate

High 109

High 96 known vulnerabilities in unknown@unknown (jaegertracing/all-in-one:1.50) Security · 96 CVEs

How to fix

No fixed version of unknown is available yet. Check whether jaegertracing/all-in-one:1.50 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-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-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-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
  • and 76 more
High 8 known vulnerabilities in stdlib@1.21.1 (jaegertracing/all-in-one:1.50) Security · 8 CVEs

How to fix

Update stdlib from 1.21.1 to 1.22.7 or later in jaegertracing/all-in-one:1.50. 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.13.0 (jaegertracing/all-in-one:1.50) Security · 4 CVEs

How to fix

Update crypto from 0.13.0 to 0.43.0 or later in jaegertracing/all-in-one:1.50. 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 1 known vulnerability in musl@1.2.3-r3 (jaegertracing/all-in-one:1.50) Security · 1 CVE

How to fix

Update musl from 1.2.3-r3 to 1.2.3-r4 or later in jaegertracing/all-in-one:1.50. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.3-r4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-26519 fixed in 1.2.3-r4

Medium 64

Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 11 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 8 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 8 places
Medium Containers should run as a high UID to avoid host conflict Security · 8 places
Medium Minimize the admission of root containers Security · 7 places
Medium Apply security context to your pods and containers Security · 7 places
Medium 3 known vulnerabilities in net@0.15.0 (jaegertracing/all-in-one:1.50) Security · 3 CVEs

How to fix

Update net from 0.15.0 to 0.36.0 or later in jaegertracing/all-in-one:1.50. 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 CVE-2023-44487 fixed in 0.17.0
Medium 1 known vulnerability in busybox@1.35.0-r17 (jaegertracing/all-in-one:1.50) 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.50. 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 openssl@1.1.1v-r0 (jaegertracing/all-in-one:1.50) Security · 1 CVE

How to fix

Update openssl from 1.1.1v-r0 to 1.1.1w-r1 or later in jaegertracing/all-in-one:1.50. 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.1.1w-r1); 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-5678 fixed in 1.1.1w-r1
Medium Ensure top-level permissions are not set to write-all Security · 1 place

Ensure top-level permissions are not set to write-all

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 1 place

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Containers should not run with allowPrivilegeEscalation Security · 1 place

Containers should not run with allowPrivilegeEscalation

Documentation

Where

Medium Use read-only filesystem for containers where possible Security · 1 place

Use read-only filesystem for containers where possible

Documentation

Where

Medium Minimize the admission of containers with the NET_RAW capability Security · 1 place

Minimize the admission of containers with the NET_RAW capability

Documentation

Where

Medium Apply security context to your containers Security · 1 place

Apply security context to your containers

Documentation

Where

Medium Prefer using secrets as files over secrets as environment variables Security · 1 place

Prefer using secrets as files over secrets as environment variables

Documentation

Where

Medium Minimize the admission of containers with capabilities assigned Security · 1 place

Minimize the admission of containers with capabilities assigned

Documentation

Where

Medium Image should use digest Security · 1 place

Image should use digest

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

Low 3

Low Large Root Volume Cost · 2 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 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.