InfraScan Cloud

Repository scan

catalogue-pipeline

wellcomecollection/catalogue-pipeline · branch main · scanned 25 Jun 2026 · 319 resources

DOverall
FSecurity
–Reliability · N/A
CCost
875findings · 0 critical, 88 high
$19.38estimated savings per month, from the code

High 170

High 132 known vulnerabilities in unknown@unknown (public.ecr.aws/docker/library/mysql:5.7) Security · 132 CVEs

How to fix

No fixed version of unknown is available yet. Check whether public.ecr.aws/docker/library/mysql:5.7 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-56171 fixed in no fix yet
  • High CVE-2024-56171 fixed in no fix yet
  • High CVE-2025-24928 fixed in no fix yet
  • High CVE-2025-24928 fixed in no fix yet
  • High CVE-2023-27561 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 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-2023-0286 fixed in no fix yet
  • High CVE-2022-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • and 112 more
High 14 known vulnerabilities in stdlib@1.18.2 (public.ecr.aws/docker/library/mysql:5.7) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in public.ecr.aws/docker/library/mysql:5.7. 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.18.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

  • High CVE-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • 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 5 known vulnerabilities in libxml2@2.9.1-6.0.3.el7_9.6 (public.ecr.aws/docker/library/mysql:5.7) Security · 5 CVEs

How to fix

Update libxml2 from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.7.el7_9.6 or later in public.ecr.aws/docker/library/mysql:5.7. 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:2.9.1-6.0.7.el7_9.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-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
  • Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 5 known vulnerabilities in libxml2-python@2.9.1-6.0.3.el7_9.6 (public.ecr.aws/docker/library/mysql:5.7) Security · 5 CVEs

How to fix

Update libxml2-python from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.7.el7_9.6 or later in public.ecr.aws/docker/library/mysql:5.7. 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:2.9.1-6.0.7.el7_9.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-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
  • Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 4 known vulnerabilities in python@2.7.5-94.0.1.el7_9 (public.ecr.aws/docker/library/mysql:5.7) Security · 4 CVEs

How to fix

Update python from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in public.ecr.aws/docker/library/mysql:5.7. 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:2.7.5-94.0.7.el7_9); 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-4519 fixed in 0:2.7.5-94.0.7.el7_9
  • Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
  • Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
  • Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 4 known vulnerabilities in python-libs@2.7.5-94.0.1.el7_9 (public.ecr.aws/docker/library/mysql:5.7) Security · 4 CVEs

How to fix

Update python-libs from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in public.ecr.aws/docker/library/mysql:5.7. 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:2.7.5-94.0.7.el7_9); 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-4519 fixed in 0:2.7.5-94.0.7.el7_9
  • Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
  • Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
  • Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 2 known vulnerabilities in krb5-libs@1.15.1-55.0.1.el7_9 (public.ecr.aws/docker/library/mysql:5.7) Security · 2 CVEs

How to fix

Update krb5-libs from 1.15.1-55.0.1.el7_9 to 0:1.15.1-55.0.7.el7_9 or later in public.ecr.aws/docker/library/mysql:5.7. 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:1.15.1-55.0.7.el7_9); 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-3596 fixed in 0:1.15.1-55.0.7.el7_9
  • Medium CVE-2025-24528 fixed in 0:1.15.1-55.0.9.el7_9
High 1 known vulnerability in gnupg2@2.0.22-5.el7_5 (public.ecr.aws/docker/library/mysql:5.7) Security · 1 CVE

How to fix

Update gnupg2 from 2.0.22-5.el7_5 to 0:2.0.22-5.0.1.el7_5 or later in public.ecr.aws/docker/library/mysql:5.7. 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:2.0.22-5.0.1.el7_5); 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 0:2.0.22-5.0.1.el7_5
High 1 known vulnerability in sqlite@3.7.17-8.el7_7.1 (public.ecr.aws/docker/library/mysql:5.7) Security · 1 CVE

How to fix

Update sqlite from 3.7.17-8.el7_7.1 to 0:3.7.17-8.0.1.el7_9.1 or later in public.ecr.aws/docker/library/mysql:5.7. 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:3.7.17-8.0.1.el7_9.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-2025-6965 fixed in 0:3.7.17-8.0.1.el7_9.1
High 1 known vulnerability in zlib@1.2.7-21.el7_9 (public.ecr.aws/docker/library/mysql:5.7) Security · 1 CVE

How to fix

Update zlib from 1.2.7-21.el7_9 to 0:1.2.7-21.0.1.el7_9 or later in public.ecr.aws/docker/library/mysql:5.7. 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:1.2.7-21.0.1.el7_9); 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-2016-9840 fixed in 0:1.2.7-21.0.1.el7_9
High Unencrypted EBS Volume Cost · 1 place

EBS volume is not encrypted. This is a security risk and often indicates unmanaged infrastructure.

How to fix

Enable encryption for EBS volumes.

Where

Medium 694

Medium Ensure Terraform module sources use a commit hash Security · 283 places
Medium Ensure that ECR repositories are encrypted using KMS Security · 30 places
Medium Ensure ECR image scanning on push is enabled Security · 30 places
Medium Ensure ECR Image Tags are immutable Security · 30 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 22 places
Medium Ensure every security group and rule has a description Security · 22 places
Medium Ensure State Machine has X-Ray tracing enabled Security · 22 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 22 places
Medium Ensure that Security Groups are attached to another resource Security · 12 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 11 places
Medium Ensure DynamoDB Tables are encrypted using a KMS Customer Managed CMK Security · 10 places
Medium Ensure all data stored in the SNS topic is encrypted Security · 10 places
Medium Missing Cost and Usage Report Cost · 10 places
Medium Ensure that S3 bucket has a Public Access block Security · 9 places
Medium Ensure S3 buckets should have event notifications enabled Security · 9 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 9 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 9 places
Medium Ensure the S3 bucket has access logging enabled Security · 9 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 9 places
Medium Ensure EventBridge Scheduler Schedule uses Customer Managed Key (CMK) Security · 9 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 9 places
Medium Ensure IAM policies does not allow write access without constraints Security · 8 places
Medium Ensure DynamoDB point in time recovery (backup) is enabled Reliability · 8 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 8 places
Medium AWS SSM Parameter should be Encrypted Security · 5 places
Medium Ensure S3 lifecycle configuration sets period for aborting failed uploads Security · 5 places
Medium Ensure container insights are enabled on ECS cluster Security · 5 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 4 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 3 places
Medium Ensure that RDS clusters has backup plan of AWS Backup Reliability · 3 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 3 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 3 places
Medium Ensure RDS cluster has IAM authentication enabled Security · 3 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 3 places
Medium Ensure RDS cluster configured to copy tags to snapshots Security · 3 places
Medium Ensure that RDS Cluster log capture is enabled Security · 3 places
Medium Ensure that RDS Cluster audit logging is enabled for MySQL engine Security · 3 places
Medium Ensure that RDS Aurora Clusters have backtracking enabled Security · 3 places
Medium Ensure RDS Clusters are encrypted using KMS CMKs Security · 3 places
Medium Ensure SSM parameters are using KMS CMK Security · 3 places

and 17 more groups with 29 findings

Low 11

Low Missing AWS Budget Cost · 10 places
Low 1 known vulnerability in sys@0.0.0-20220907062415-87db552b00fd (public.ecr.aws/docker/library/mysql:5.7) Security · 1 CVE

How to fix

Update sys from 0.0.0-20220907062415-87db552b00fd to 0.44.0 or later in public.ecr.aws/docker/library/mysql:5.7. 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.44.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

  • Low CVE-2026-39824 fixed in 0.44.0

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.