InfraScan Cloud

Repository scan

pulse-data

Recidiviz/pulse-data · branch main · scanned 25 Jun 2026 · 471 resources

COverall
FSecurity
–Reliability · N/A
ACost
287findings · 0 critical, 30 high
$2.10estimated savings per month, from the code

High 68

High 31 known vulnerabilities in unknown@unknown (postgres:18.3-alpine) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:18.3-alpine 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-39820 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-58183 fixed in no fix yet
  • Medium CVE-2025-47912 fixed in no fix yet
  • Medium CVE-2025-58186 fixed in no fix yet
  • Medium CVE-2025-58189 fixed in no fix yet
  • Medium CVE-2025-61724 fixed in no fix yet
  • Medium CVE-2025-61730 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • and 11 more
High 15 known vulnerabilities in curl@8.17.0-r1 (postgres:18.3-alpine) Security · 15 CVEs

How to fix

Update curl from 8.17.0-r1 to 8.19.0-r0 or later in postgres:18.3-alpine. 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.19.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-2026-3805 fixed in 8.19.0-r0
  • High CVE-2026-5773 fixed in no fix yet
  • High CVE-2026-6276 fixed in no fix yet
  • Medium CVE-2025-14524 fixed in 8.19.0-r0
  • Medium CVE-2025-14819 fixed in 8.19.0-r0
  • Medium CVE-2026-3783 fixed in 8.19.0-r0
  • Medium CVE-2026-6429 fixed in no fix yet
  • Medium CVE-2026-7009 fixed in no fix yet
  • Medium CVE-2026-7168 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 8.19.0-r0
  • Medium CVE-2026-1965 fixed in 8.19.0-r0
  • Medium CVE-2026-3784 fixed in 8.19.0-r0
  • Medium CVE-2026-5545 fixed in no fix yet
High 15 known vulnerabilities in openssl@3.5.6-r0 (postgres:18.3-alpine) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in postgres:18.3-alpine. 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.7-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-2026-34181 fixed in 3.5.7-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-7383 fixed in 3.5.7-r0
  • High CVE-2026-45447 fixed in 3.5.7-r0
  • High CVE-2026-34182 fixed in 3.5.7-r0
  • Medium CVE-2026-45446 fixed in 3.5.7-r0
  • Medium CVE-2026-42769 fixed in 3.5.7-r0
  • Medium CVE-2026-42766 fixed in 3.5.7-r0
  • Medium CVE-2026-42767 fixed in 3.5.7-r0
  • Low CVE-2026-42768 fixed in 3.5.7-r0
  • Low CVE-2026-42770 fixed in 3.5.7-r0
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:18.3-alpine) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:18.3-alpine. 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 1 known vulnerability in nghttp2@1.68.0-r0 (postgres:18.3-alpine) Security · 1 CVE

How to fix

Update nghttp2 from 1.68.0-r0 to 1.68.1 or later in postgres:18.3-alpine. 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.68.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-2026-27135 fixed in 1.68.1

Medium 217

Medium Ensure public access prevention is enforced on Cloud Storage bucket Security · 56 places

Ensure public access prevention is enforced on Cloud Storage bucket

Documentation

Where

Medium Ensure Big Query Datasets are encrypted with Customer Supplied Encryption Keys (CSEK) Security · 15 places
Medium Ensure PubSub Topics are encrypted with Customer Supplied Encryption Keys (CSEK) Security · 12 places
Medium Ensure that Cloud Storage buckets have uniform bucket-level access enabled Security · 11 places
Medium Ensure Cloud SQL database does not have public IP Security · 11 places
Medium Ensure the GCP PostgreSQL database log levels are set to ERROR or lower Security · 10 places
Medium Ensure pgAudit is enabled for your GCP PostgreSQL database Security · 10 places
Medium Ensure PostgreSQL database 'log_checkpoints' flag is set to 'on' Security · 10 places
Medium Ensure PostgreSQL database 'log_min_duration_statement' flag is set to '-1' Security · 9 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 5 places
Medium Ensure Memorystore for Redis has AUTH enabled Security · 5 places
Medium Ensure Memorystore for Redis uses intransit encryption Security · 5 places
Medium Ensure Terraform module sources use a commit hash Security · 4 places
Medium Ensure that a user for the container has been created Security · 3 places
Medium Ensure that GCP Cloud Run services are not anonymously or publicly accessible Security · 3 places
Medium Ensure the GKE Metadata Server is Enabled Security · 3 places
Medium Ensure Big Query Tables are encrypted with Customer Supplied Encryption Keys (CSEK) Security · 3 places
Medium Ensure that Cloud Audit Logging is configured properly across all services and all users from a project Security · 2 places
Medium Ensure the base image uses a non latest version tag Security · 2 places
Medium Ensure that APT isn't used Security · 2 places
Medium Ensure basic roles are not used at project level. Security · 2 places
Medium Ensure BigQuery tables have deletion protection enabled Security · 2 places
Medium Ensure roles do not impersonate or manage Service Accounts used at project level Security · 2 places
Medium Ensure all Cloud SQL database instance requires all incoming connections to use SSL Security · 2 places
Medium Bucket should log access Security · 2 places
Medium Ensure Secure Boot for Shielded GKE Nodes is Enabled Security · 2 places
Medium Ensure Cloud Armor prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 2 places
Medium Ensure Artifact Registry Repositories are encrypted with Customer Supplied Encryption Keys (CSEK) Security · 2 places
Medium 1 known vulnerability in busybox@1.37.0-r30 (postgres:18.3-alpine) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether postgres:18.3-alpine 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
Medium 1 known vulnerability in libxml2@2.13.9-r0 (postgres:18.3-alpine) Security · 1 CVE

How to fix

Update libxml2 from 2.13.9-r0 to 2.13.9-r1 or later in postgres:18.3-alpine. 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.13.9-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-2026-6732 fixed in 2.13.9-r1
Medium Ensure PostgreSQL database flag 'log_duration' is set to 'on' Security · 1 place
Medium Ensure GCP network defines a firewall and does not use the default firewall Security · 1 place

Ensure GCP network defines a firewall and does not use the default firewall

Documentation

Where

Medium Ensure 'Automatic node upgrade' is enabled for Kubernetes Clusters Security · 1 place

Ensure 'Automatic node upgrade' is enabled for Kubernetes Clusters

Documentation

Where

Medium Ensure hostnames are logged for GCP PostgreSQL databases Security · 1 place
Medium Ensure GCP PostgreSQL logs SQL statements Security · 1 place
Medium Ensure Network Policy is enabled on Kubernetes Engine Clusters Security · 1 place

Ensure Network Policy is enabled on Kubernetes Engine Clusters

Documentation

Where

Medium Ensure that DNSSEC is enabled for Cloud DNS Security · 1 place
Medium Ensure Kubernetes Clusters are configured with Labels Security · 1 place
Medium Ensure Container-Optimized OS (cos) is used for Kubernetes Engine Clusters Node image Security · 1 place

Ensure Container-Optimized OS (cos) is used for Kubernetes Engine Clusters Node image

Documentation

Where

Medium Ensure Kubernetes Cluster is created with Private cluster enabled Security · 1 place

Ensure Kubernetes Cluster is created with Private cluster enabled

Documentation

Where

and 8 more groups with 8 findings

Low 2

Low 1 known vulnerability in xz@5.8.2-r0 (postgres:18.3-alpine) Security · 1 CVE

How to fix

Update xz from 5.8.2-r0 to 5.8.3-r0 or later in postgres:18.3-alpine. 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.8.3-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

  • Low CVE-2026-34743 fixed in 5.8.3-r0
Low EC2 Detailed Monitoring Cost · 1 place

Detailed monitoring for EC2 instances incurs extra costs.

How to fix

Disable detailed monitoring if standard 5-minute metrics are sufficient.

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.