InfraScan Cloud

Repository scan

valkyrie

deepakdinesh1123/valkyrie · branch main · scanned 25 Jun 2026 · 19 resources

DOverall
DSecurity
–Reliability · N/A
CCost
221findings · 0 critical, 91 high
$200estimated savings per month, from the code

High 180

High 63 known vulnerabilities in unknown@unknown (quay.io/cilium/tetragon:v1.4.0) Security · 63 CVEs

How to fix

No fixed version of unknown is available yet. Check whether quay.io/cilium/tetragon:v1.4.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-2024-25621 fixed in no fix yet
  • High CVE-2025-31133 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • High CVE-2025-52881 fixed in no fix yet
  • High CVE-2026-46680 fixed in no fix yet
  • High CVE-2025-22874 fixed in no fix yet
  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2026-41520 fixed in no fix yet
  • High CVE-2026-53488 fixed in no fix yet
  • and 43 more
High 42 known vulnerabilities in unknown@unknown (jaegertracing/all-in-one:latest) Security · 42 CVEs

How to fix

No fixed version of unknown is available yet. Check whether jaegertracing/all-in-one: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-24051 fixed in no fix yet
  • High CVE-2026-39883 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-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-39820 fixed in no fix yet
  • High CVE-2026-39829 fixed in no fix yet
  • High CVE-2026-41602 fixed in no fix yet
  • High CVE-2026-33186 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-2025-68121 fixed in no fix yet
  • and 22 more
High 34 known vulnerabilities in openssl@3.5.4-r0 (jaegertracing/all-in-one:latest) Security · 34 CVEs

How to fix

Update openssl from 3.5.4-r0 to 3.5.5-r0 or later in jaegertracing/all-in-one: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 3.5.5-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.5.5-r0
  • High CVE-2026-34181 fixed in 3.5.7-r0
  • High CVE-2025-69420 fixed in 3.5.5-r0
  • High CVE-2025-69421 fixed in 3.5.5-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-2025-15467 fixed in 3.5.5-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-2025-69418 fixed in 3.5.5-r0
  • and 14 more
High 19 known vulnerabilities in openssl@3.3.3-r0 (quay.io/cilium/tetragon:v1.4.0) Security · 19 CVEs

How to fix

Update openssl from 3.3.3-r0 to 3.3.6-r0 or later in quay.io/cilium/tetragon:v1.4.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.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 7 known vulnerabilities in stdlib@1.24.1 (quay.io/cilium/tetragon:v1.4.0) Security · 7 CVEs

How to fix

Update stdlib from 1.24.1 to 1.25.8 or later in quay.io/cilium/tetragon:v1.4.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
  • Medium CVE-2025-4673 fixed in 1.24.4
High 5 known vulnerabilities in stdlib@1.25.4 (jaegertracing/all-in-one:latest) Security · 5 CVEs

How to fix

Update stdlib from 1.25.4 to 1.25.8 or later in jaegertracing/all-in-one: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.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
High 3 known vulnerabilities in crypto@0.45.0 (jaegertracing/all-in-one:latest) Security · 3 CVEs

How to fix

Update crypto from 0.45.0 to 0.52.0 or later in jaegertracing/all-in-one: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.5-r10 (jaegertracing/all-in-one:latest) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r10 to 1.2.5-r12 or later in jaegertracing/all-in-one: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.2.5-r12); 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-r12
  • Medium CVE-2026-6042 fixed in 1.2.5-r11
High 2 known vulnerabilities in net@0.47.0 (jaegertracing/all-in-one:latest) Security · 2 CVEs

How to fix

Update net from 0.47.0 to 0.53.0 or later in jaegertracing/all-in-one: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.53.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33814 fixed in 0.53.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 2 known vulnerabilities in musl@1.2.5-r9 (quay.io/cilium/tetragon:v1.4.0) Security · 2 CVEs

How to fix

Update musl from 1.2.5-r9 to 1.2.5-r11 or later in quay.io/cilium/tetragon:v1.4.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-r11); 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-r11
  • Medium CVE-2026-6042 fixed in 1.2.5-r10
High EBS Provisioned IOPS (io1/io2) Cost · 1 place

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

Medium 38

Medium 3 known vulnerabilities in busybox@1.37.0-r19 (jaegertracing/all-in-one:latest) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether jaegertracing/all-in-one:latest needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
  • Low CVE-2024-58251 fixed in 1.37.0-r20
  • Low CVE-2025-46394 fixed in 1.37.0-r20
Medium 3 known vulnerabilities in busybox@1.37.0-r12 (quay.io/cilium/tetragon:v1.4.0) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether quay.io/cilium/tetragon:v1.4.0 needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
  • Low CVE-2024-58251 fixed in 1.37.0-r14
  • Low CVE-2025-46394 fixed in 1.37.0-r14
Medium Ensure VPC subnets do not assign public IP by default Security · 3 places
Medium Missing Cost and Usage Report Cost · 3 places

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Medium 2 known vulnerabilities in zlib@1.3.1-r2 (jaegertracing/all-in-one:latest) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in jaegertracing/all-in-one: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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (quay.io/cilium/tetragon:v1.4.0) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in quay.io/cilium/tetragon:v1.4.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.3.2-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

  • Medium CVE-2026-22184 fixed in 1.3.2-r0
  • Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 1 known vulnerability in libcap@2.71-r0 (quay.io/cilium/tetragon:v1.4.0) Security · 1 CVE

How to fix

Update libcap from 2.71-r0 to 2.78-r0 or later in quay.io/cilium/tetragon:v1.4.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.78-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

  • Medium CVE-2026-4878 fixed in 2.78-r0
Medium 1 known vulnerability in net@0.36.0 (quay.io/cilium/tetragon:v1.4.0) Security · 1 CVE

How to fix

Update net from 0.36.0 to 0.55.0 or later in quay.io/cilium/tetragon:v1.4.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 VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure 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 an IAM role is attached to EC2 instance Security · 1 place

Ensure an IAM role is attached to EC2 instance

Documentation

Where

Medium Ensure that Security Groups are attached to another resource Security · 1 place

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 1 place

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 1 place

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 1 place

Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled

Documentation

Where

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

Ensure that RDS instances have Multi-AZ enabled

Documentation

Where

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

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

Documentation

Where

Medium Ensure resource is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure resource is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure EBS Volume is encrypted by KMS using a customer managed Key (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 every security group and rule has a description Security · 1 place

Ensure every security group and rule has a description

Documentation

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 1 place

Ensure no security groups allow ingress from 0.0.0.0:0 to port 22

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 all data stored in the EBS is securely encrypted Security · 1 place

Ensure all data stored in the EBS is securely encrypted

Documentation

Where

Medium Ensure that RDS instances have performance insights enabled Security · 1 place

Ensure that RDS instances have performance insights enabled

Documentation

Where

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 1 place

Ensure no security groups allow egress from 0.0.0.0:0 to port -1

Documentation

Where

Medium Ensure EFS is securely encrypted Security · 1 place

Ensure EFS is securely encrypted

Documentation

Where

Low 3

Low Missing AWS Budget Cost · 3 places

No AWS budget configured. Budgets help monitor and control spending with alerts.

How to fix

Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.

Where

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.