InfraScan Cloud

Repository scan

Fixops

DevOpsMadDog/Fixops · branch main · scanned 25 Jun 2026 · 320 resources

DOverall
FSecurity
–Reliability · N/A
BCost
507findings · 0 critical, 57 high
$3.65–$82.85estimated savings per month, from the code

High 149

High 49 known vulnerabilities in unknown@unknown (dependencytrack/frontend:4.12.3) Security · 49 CVEs

How to fix

No fixed version of unknown is available yet. Check whether dependencytrack/frontend:4.12.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-44495 fixed in no fix yet
  • High CVE-2026-42043 fixed in no fix yet
  • High CVE-2026-42033 fixed in no fix yet
  • High CVE-2026-42035 fixed in no fix yet
  • High CVE-2026-42264 fixed in no fix yet
  • High CVE-2025-58754 fixed in no fix yet
  • High CVE-2026-25639 fixed in no fix yet
  • High CVE-2026-44486 fixed in no fix yet
  • High CVE-2026-44488 fixed in no fix yet
  • High CVE-2026-44496 fixed in no fix yet
  • High CVE-2025-27152 fixed in no fix yet
  • High CVE-2026-4800 fixed in no fix yet
  • High CVE-2026-44487 fixed in no fix yet
  • High CVE-2026-44492 fixed in no fix yet
  • High CVE-2026-44494 fixed in no fix yet
  • Medium CVE-2025-26791 fixed in no fix yet
  • Medium CVE-2025-64758 fixed in no fix yet
  • Medium CVE-2026-40175 fixed in no fix yet
  • Medium CVE-2026-42041 fixed in no fix yet
  • Medium CVE-2026-44490 fixed in no fix yet
  • and 29 more
High 26 known vulnerabilities in curl@8.11.1-r0 (dependencytrack/frontend:4.12.3) Security · 26 CVEs

How to fix

Update curl from 8.11.1-r0 to 8.12.0-r0 or later in dependencytrack/frontend:4.12.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 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-2025-5399 fixed in 8.14.1-r0
  • High CVE-2025-9086 fixed in 8.14.1-r2
  • High CVE-2026-3805 fixed in no fix yet
  • High CVE-2026-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • Medium CVE-2025-10966 fixed in no fix yet
  • Medium CVE-2025-5025 fixed in 8.14.0-r0
  • Medium CVE-2025-10148 fixed in 8.14.1-r2
  • Medium CVE-2025-14524 fixed in no fix yet
  • Medium CVE-2025-14819 fixed in no fix yet
  • Medium CVE-2025-15079 fixed in no fix yet
  • Medium CVE-2026-3783 fixed in no fix yet
  • Medium CVE-2026-6429 fixed in no fix yet
  • Medium CVE-2026-7168 fixed in no fix yet
  • Medium CVE-2025-13034 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 no fix yet
  • and 6 more
High 21 known vulnerabilities in openssl@3.3.2-r1 (dependencytrack/frontend:4.12.3) Security · 21 CVEs

How to fix

Update openssl from 3.3.2-r1 to 3.3.6-r0 or later in dependencytrack/frontend:4.12.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.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-2024-13176 fixed in 3.3.2-r2
  • 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-2024-12797 fixed in 3.3.3-r0
  • and 1 more
High 14 known vulnerabilities in jq@1.7.1-r0 (dependencytrack/frontend:4.12.3) Security · 14 CVEs

How to fix

No fixed version of jq is available yet. Check whether dependencytrack/frontend:4.12.3 needs jq 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-48060 fixed in no fix yet
  • High CVE-2024-53427 fixed in no fix yet
  • High CVE-2026-32316 fixed in no fix yet
  • Medium CVE-2024-23337 fixed in no fix yet
  • Medium CVE-2026-43895 fixed in no fix yet
  • Medium CVE-2026-40612 fixed in no fix yet
  • Medium CVE-2026-44777 fixed in no fix yet
  • Medium CVE-2026-41256 fixed in no fix yet
  • Medium CVE-2026-33947 fixed in no fix yet
  • Medium CVE-2026-43894 fixed in no fix yet
  • Medium CVE-2026-43896 fixed in no fix yet
  • Medium CVE-2026-41257 fixed in no fix yet
  • Medium CVE-2026-39979 fixed in no fix yet
  • Low CVE-2026-33948 fixed in no fix yet
High 11 known vulnerabilities in libpng@1.6.44-r0 (dependencytrack/frontend:4.12.3) Security · 11 CVEs

How to fix

Update libpng from 1.6.44-r0 to 1.6.53-r0 or later in dependencytrack/frontend:4.12.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.6.53-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-64720 fixed in 1.6.53-r0
  • High CVE-2025-65018 fixed in 1.6.53-r0
  • High CVE-2025-66293 fixed in 1.6.53-r0
  • High CVE-2026-33416 fixed in 1.6.56-r0
  • High CVE-2026-33636 fixed in 1.6.56-r0
  • High CVE-2026-25646 fixed in 1.6.55-r0
  • Medium CVE-2026-34757 fixed in 1.6.57-r0
  • Medium CVE-2025-64505 fixed in 1.6.53-r0
  • Medium CVE-2025-64506 fixed in 1.6.53-r0
  • Medium CVE-2026-22695 fixed in 1.6.54-r0
  • Medium CVE-2026-22801 fixed in 1.6.54-r0
High 10 known vulnerabilities in expat@2.6.4-r0 (dependencytrack/frontend:4.12.3) Security · 10 CVEs

How to fix

Update expat from 2.6.4-r0 to 2.7.0-r0 or later in dependencytrack/frontend:4.12.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 2.7.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-2024-8176 fixed in 2.7.0-r0
  • High CVE-2025-59375 fixed in 2.7.2-r0
  • High CVE-2026-32767 fixed in 2.7.5-r0
  • Medium CVE-2026-32776 fixed in 2.7.5-r0
  • Medium CVE-2026-32777 fixed in 2.7.5-r0
  • Medium CVE-2026-25210 fixed in 2.7.4-r0
  • Low CVE-2026-24515 fixed in 2.7.4-r0
  • Low CVE-2026-32778 fixed in 2.7.5-r0
  • Low CVE-2026-41080 fixed in 2.8.1-r0
  • Low CVE-2026-45186 fixed in 2.8.1-r0
High 6 known vulnerabilities in libxml2@2.12.7-r0 (dependencytrack/frontend:4.12.3) Security · 6 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether dependencytrack/frontend:4.12.3 needs libxml2 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-6021 fixed in no fix yet
  • High CVE-2024-56171 fixed in 2.12.7-r1
  • High CVE-2025-24928 fixed in 2.12.7-r1
  • Medium CVE-2025-32414 fixed in 2.12.10-r0
  • Low CVE-2025-27113 fixed in 2.12.7-r2
  • Low CVE-2025-32415 fixed in 2.12.10-r0
High 3 known vulnerabilities in musl@1.2.5-r0 (dependencytrack/frontend:4.12.3) Security · 3 CVEs

How to fix

Update musl from 1.2.5-r0 to 1.2.5-r1 or later in dependencytrack/frontend:4.12.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.2.5-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

  • High CVE-2025-26519 fixed in 1.2.5-r1
  • High CVE-2026-40200 fixed in 1.2.5-r3
  • Medium CVE-2026-6042 fixed in 1.2.5-r2
High 2 known vulnerabilities in c-ares@1.33.1-r0 (dependencytrack/frontend:4.12.3) Security · 2 CVEs

How to fix

No fixed version of c-ares is available yet. Check whether dependencytrack/frontend:4.12.3 needs c-ares 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-31498 fixed in no fix yet
  • Medium CVE-2025-62408 fixed in no fix yet
High 2 known vulnerabilities in libxslt@1.1.39-r1 (dependencytrack/frontend:4.12.3) Security · 2 CVEs

How to fix

Update libxslt from 1.1.39-r1 to 1.1.39-r2 or later in dependencytrack/frontend:4.12.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.1.39-r2); 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-55549 fixed in 1.1.39-r2
  • High CVE-2025-24855 fixed in 1.1.39-r2
High 2 known vulnerabilities in xz@5.6.2-r0 (dependencytrack/frontend:4.12.3) Security · 2 CVEs

How to fix

Update xz from 5.6.2-r0 to 5.6.2-r1 or later in dependencytrack/frontend:4.12.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 5.6.2-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

  • High CVE-2025-31115 fixed in 5.6.2-r1
  • Low CVE-2026-34743 fixed in 5.8.3-r0
High Expensive NAT Gateway Cost · 2 places

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

High 1 known vulnerability in nghttp2@1.62.1-r0 (dependencytrack/frontend:4.12.3) Security · 1 CVE

How to fix

No fixed version of nghttp2 is available yet. Check whether dependencytrack/frontend:4.12.3 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

  • High CVE-2026-27135 fixed in no fix yet

Medium 356

Medium Image should use digest Security · 15 places
Medium Minimize the admission of containers with the NET_RAW capability Security · 12 places
Medium Image Tag should be fixed - not latest or blank Security · 11 places
Medium Base64 High Entropy String Security · 11 places
Medium Containers should run as a high UID to avoid host conflict Security · 10 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 7 places
Medium Ensure that a user for the container has been created Security · 7 places
Medium Containers should not run with allowPrivilegeEscalation Security · 7 places
Medium Use read-only filesystem for containers where possible Security · 7 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 7 places
Medium Prefer using secrets as files over secrets as environment variables Security · 7 places
Medium Minimize the admission of containers with capabilities assigned Security · 7 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 7 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 6 places
Medium Ensure S3 buckets should have event notifications enabled Security · 5 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 5 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 5 places
Medium Ensure the S3 bucket has access logging enabled Security · 5 places
Medium Image Pull Policy should be Always Security · 5 places
Medium Minimize the admission of root containers Security · 5 places
Medium Apply security context to your pods and containers Security · 5 places
Medium Apply security context to your pods, deployments and daemon_sets Security · 5 places
Medium Apply security context to your containers Security · 5 places
Medium Apply security context to your pods and containers Security · 5 places
Medium Missing Cost and Usage Report Cost · 5 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 The default namespace should not be used Security · 4 places
Medium Ensure that arrays have a maximum number of items Security · 4 places
Medium Ensure that the global security field has rules defined Security · 4 places
Medium Ensure that security operations is not empty. Security · 4 places
Medium AWS Access Key Security · 4 places
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (dependencytrack/frontend:4.12.3) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether dependencytrack/frontend:4.12.3 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.36.1-r31
  • Low CVE-2025-46394 fixed in 1.36.1-r31
Medium Ensure that S3 bucket has a Public Access block Security · 3 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 3 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 3 places
Medium Ensure that Storage Accounts use replication Security · 3 places
Medium Ensure default network access rule for Storage Accounts is set to deny Security · 3 places
Medium Ensure Storage Accounts adhere to the naming rules Security · 3 places
Medium Ensure the base image uses a non latest version tag Security · 3 places

and 92 more groups with 130 findings

Low 2

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 SQS Max Message Retention Cost · 1 place

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

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.