Repository scan
Chronote
Chronote-gg/Chronote · branch main · scanned 25 Jun 2026 · 189 resources
High 431
High 242 known vulnerabilities in unknown@unknown (amazon/dynamodb-local:latest)
How to fix
No fixed version of unknown is available yet. Check whether amazon/dynamodb-local: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-2025-11468 fixed in no fix yet
- High CVE-2025-11468 fixed in no fix yet
- High CVE-2025-15282 fixed in no fix yet
- High CVE-2025-15282 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15467 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-15468 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-66199 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68160 fixed in no fix yet
- High CVE-2025-68973 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- High CVE-2025-69418 fixed in no fix yet
- and 222 more
High 100 known vulnerabilities in unknown@unknown (quay.io/minio/minio:latest)
How to fix
No fixed version of unknown is available yet. Check whether quay.io/minio/minio: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-34204 fixed in no fix yet
- High CVE-2026-39414 fixed in no fix yet
- High CVE-2026-39883 fixed in no fix yet
- High CVE-2018-1000538 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-33814 fixed in no fix yet
- High CVE-2026-33814 fixed in no fix yet
- High CVE-2026-34986 fixed in no fix yet
- High CVE-2026-39820 fixed in no fix yet
- and 80 more
High 60 known vulnerabilities in unknown@unknown (quay.io/minio/mc:latest)
How to fix
No fixed version of unknown is available yet. Check whether quay.io/minio/mc: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-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-39829 fixed in no fix yet
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2026-42151 fixed in no fix yet
- High CVE-2026-42154 fixed in no fix yet
- High CVE-2026-0861 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
- and 40 more
High 8 known vulnerabilities in crypto@0.40.0 (quay.io/minio/minio:latest)
How to fix
Update crypto from 0.40.0 to 0.43.0 or later in quay.io/minio/minio: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.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-2025-47913 fixed in 0.43.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
High 6 known vulnerabilities in stdlib@1.24.6 (quay.io/minio/mc:latest)
How to fix
Update stdlib from 1.24.6 to 1.25.8 or later in quay.io/minio/mc: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
- Medium CVE-2025-58185 fixed in 1.24.8
High 6 known vulnerabilities in stdlib@1.24.6 (quay.io/minio/minio:latest)
How to fix
Update stdlib from 1.24.6 to 1.25.8 or later in quay.io/minio/minio: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
- Medium CVE-2025-58185 fixed in 1.24.8
High 4 known vulnerabilities in crypto@0.40.0 (quay.io/minio/mc:latest)
How to fix
Update crypto from 0.40.0 to 0.43.0 or later in quay.io/minio/mc: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.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 2 known vulnerabilities in gnupg2-minimal@2.3.7-1.amzn2023.0.5 (amazon/dynamodb-local:latest)
How to fix
Update gnupg2-minimal from 2.3.7-1.amzn2023.0.5 to 2.3.7-1.amzn2023.0.6 or later in amazon/dynamodb-local: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 2.3.7-1.amzn2023.0.6); 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-68973 fixed in 2.3.7-1.amzn2023.0.6
- High CVE-2026-24882 fixed in 2.3.7-1.amzn2023.0.7
High 1 known vulnerability in gnupg2@2.3.7-1.amzn2023.0.5 (amazon/dynamodb-local:latest)
How to fix
Update gnupg2 from 2.3.7-1.amzn2023.0.5 to 2.3.7-1.amzn2023.0.7 or later in amazon/dynamodb-local: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 2.3.7-1.amzn2023.0.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-2026-24882 fixed in 2.3.7-1.amzn2023.0.7
High 1 known vulnerability in graphite2@1.3.14-7.amzn2023.0.2 (amazon/dynamodb-local:latest)
How to fix
Update graphite2 from 1.3.14-7.amzn2023.0.2 to 1.3.14-7.amzn2023.0.3 or later in amazon/dynamodb-local: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.14-7.amzn2023.0.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-50593 fixed in 1.3.14-7.amzn2023.0.3
High 1 known vulnerability in libtasn1@4.19.0-1.amzn2023.0.5 (amazon/dynamodb-local:latest)
How to fix
Update libtasn1 from 4.19.0-1.amzn2023.0.5 to 4.19.0-1.amzn2023.0.6 or later in amazon/dynamodb-local: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 4.19.0-1.amzn2023.0.6); 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-13151 fixed in 4.19.0-1.amzn2023.0.6
Medium 19
Medium 2 known vulnerabilities in net@0.42.0 (quay.io/minio/minio:latest)
How to fix
Update net from 0.42.0 to 0.55.0 or later in quay.io/minio/minio: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 CVE-2026-25680 fixed in 0.55.0
Medium Missing Cost and Usage Report
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 1 known vulnerability in curl@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local:latest)
How to fix
Update curl from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local: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 8.17.0-1.amzn2023.0.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
- Medium CVE-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in curl-minimal@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local:latest)
How to fix
Update curl-minimal from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local: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 8.17.0-1.amzn2023.0.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
- Medium CVE-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in expat@2.6.3-1.amzn2023.0.3 (amazon/dynamodb-local:latest)
How to fix
Update expat from 2.6.3-1.amzn2023.0.3 to 2.6.3-1.amzn2023.0.4 or later in amazon/dynamodb-local: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 2.6.3-1.amzn2023.0.4); 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-25210 fixed in 2.6.3-1.amzn2023.0.4
Medium 1 known vulnerability in libcurl-minimal@8.15.0-4.amzn2023.0.1 (amazon/dynamodb-local:latest)
How to fix
Update libcurl-minimal from 8.15.0-4.amzn2023.0.1 to 8.17.0-1.amzn2023.0.3 or later in amazon/dynamodb-local: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 8.17.0-1.amzn2023.0.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
- Medium CVE-2026-3805 fixed in 8.17.0-1.amzn2023.0.3
Medium 1 known vulnerability in libgcrypt@1.10.2-1.amzn2023.0.2 (amazon/dynamodb-local:latest)
How to fix
Update libgcrypt from 1.10.2-1.amzn2023.0.2 to 1.10.2-1.amzn2023.0.3 or later in amazon/dynamodb-local: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.10.2-1.amzn2023.0.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
- Medium CVE-2026-41989 fixed in 1.10.2-1.amzn2023.0.3
Medium 1 known vulnerability in net@0.42.0 (quay.io/minio/mc:latest)
How to fix
Update net from 0.42.0 to 0.55.0 or later in quay.io/minio/mc: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 Ensure that an S3 bucket has a lifecycle configuration
Ensure that an S3 bucket has a lifecycle configuration
Where
Medium Ensure S3 buckets should have event notifications enabled
Ensure S3 buckets should have event notifications enabled
Where
Medium Ensure KMS key Policy is defined
Medium Ensure access control lists for S3 buckets are disabled
Ensure access control lists for S3 buckets are disabled
Where
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK
Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK
Where
Medium Ensure that S3 bucket has cross-region replication enabled
Ensure that S3 bucket has cross-region replication enabled
Where
Medium Ensure the S3 bucket has access logging enabled
Ensure the S3 bucket has access logging enabled
Where
Medium Ensure DynamoDB point in time recovery (backup) is enabled
Ensure DynamoDB point in time recovery (backup) is enabled
Where
Medium Load Balancer for Single Instance
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 2
Low Missing AWS Budget
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.