InfraScan Cloud

Repository scan

gfw-data-api

wri/gfw-data-api · branch main · scanned 25 Jun 2026 · 60 resources

COverall
DSecurity
–Reliability · N/A
BCost
270findings · 0 critical, 101 high
$2.50estimated savings per month, from the code

High 209

High 88 known vulnerabilities in unknown@unknown (postgis/postgis:14-3.4-alpine) Security · 88 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgis/postgis:14-3.4-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-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 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
  • High CVE-2022-41722 fixed in no fix yet
  • High CVE-2022-41723 fixed in no fix yet
  • High CVE-2022-41724 fixed in no fix yet
  • High CVE-2022-41725 fixed in no fix yet
  • High CVE-2023-24534 fixed in no fix yet
  • High CVE-2023-24536 fixed in no fix yet
  • High CVE-2023-24537 fixed in no fix yet
  • High CVE-2023-39325 fixed in no fix yet
  • High CVE-2023-44487 fixed in no fix yet
  • and 68 more
High 28 known vulnerabilities in curl@8.10.1-r0 (postgis/postgis:14-3.4-alpine) Security · 28 CVEs

How to fix

Update curl from 8.10.1-r0 to 8.12.0-r0 or later in postgis/postgis:14-3.4-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.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 8 more
High 22 known vulnerabilities in openssl@3.3.2-r0 (postgis/postgis:14-3.4-alpine) Security · 22 CVEs

How to fix

Update openssl from 3.3.2-r0 to 3.3.6-r0 or later in postgis/postgis:14-3.4-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.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-2024-9143 fixed in 3.3.2-r1
  • 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
  • and 2 more
High 14 known vulnerabilities in stdlib@1.18.2 (postgis/postgis:14-3.4-alpine) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in postgis/postgis:14-3.4-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.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 11 known vulnerabilities in expat@2.6.3-r0 (postgis/postgis:14-3.4-alpine) Security · 11 CVEs

How to fix

Update expat from 2.6.3-r0 to 2.7.0-r0 or later in postgis/postgis:14-3.4-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.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-2024-50602 fixed in 2.6.4-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 11 known vulnerabilities in libpng@1.6.44-r0 (postgis/postgis:14-3.4-alpine) Security · 11 CVEs

How to fix

Update libpng from 1.6.44-r0 to 1.6.53-r0 or later in postgis/postgis:14-3.4-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.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 8 known vulnerabilities in libarchive@3.7.6-r0 (postgis/postgis:14-3.4-alpine) Security · 8 CVEs

How to fix

No fixed version of libarchive is available yet. Check whether postgis/postgis:14-3.4-alpine needs libarchive 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-5914 fixed in no fix yet
  • Medium CVE-2024-57970 fixed in 3.7.9-r0
  • Medium CVE-2025-25724 fixed in 3.7.9-r0
  • Medium CVE-2025-1632 fixed in 3.7.9-r0
  • Medium CVE-2025-5915 fixed in no fix yet
  • Low CVE-2025-5917 fixed in no fix yet
  • Low CVE-2025-5916 fixed in no fix yet
  • Low CVE-2025-5918 fixed in no fix yet
High 6 known vulnerabilities in libxml2@2.12.7-r0 (postgis/postgis:14-3.4-alpine) Security · 6 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether postgis/postgis:14-3.4-alpine 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 6 known vulnerabilities in sqlite@3.45.3-r1 (postgis/postgis:14-3.4-alpine) Security · 6 CVEs

How to fix

Update sqlite from 3.45.3-r1 to 3.45.3-r3 or later in postgis/postgis:14-3.4-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.45.3-r3); 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 3.45.3-r3
  • High CVE-2025-70873 fixed in no fix yet
  • High CVE-2026-11822 fixed in no fix yet
  • High CVE-2026-11824 fixed in no fix yet
  • Medium CVE-2025-3277 fixed in no fix yet
  • Low CVE-2025-29087 fixed in 3.45.3-r2
High 4 known vulnerabilities in giflib@5.2.2-r0 (postgis/postgis:14-3.4-alpine) Security · 4 CVEs

How to fix

No fixed version of giflib is available yet. Check whether postgis/postgis:14-3.4-alpine needs giflib 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-31344 fixed in no fix yet
  • High CVE-2026-26740 fixed in no fix yet
  • Medium CVE-2026-23868 fixed in no fix yet
  • Medium CVE-2024-45993 fixed in no fix yet
High 3 known vulnerabilities in musl@1.2.5-r0 (postgis/postgis:14-3.4-alpine) Security · 3 CVEs

How to fix

Update musl from 1.2.5-r0 to 1.2.5-r1 or later in postgis/postgis:14-3.4-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.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 (postgis/postgis:14-3.4-alpine) Security · 2 CVEs

How to fix

No fixed version of c-ares is available yet. Check whether postgis/postgis:14-3.4-alpine 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 (postgis/postgis:14-3.4-alpine) Security · 2 CVEs

How to fix

Update libxslt from 1.1.39-r1 to 1.1.39-r2 or later in postgis/postgis:14-3.4-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.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 (postgis/postgis:14-3.4-alpine) Security · 2 CVEs

How to fix

Update xz from 5.6.2-r0 to 5.6.2-r1 or later in postgis/postgis:14-3.4-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.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 1 known vulnerability in icu@74.2-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

Update icu from 74.2-r0 to 74.2-r1 or later in postgis/postgis:14-3.4-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 74.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-5222 fixed in 74.2-r1
High 1 known vulnerability in nghttp2@1.62.1-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of nghttp2 is available yet. Check whether postgis/postgis:14-3.4-alpine 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 59

Medium Ensure AWS API gateway request is validated Security · 13 places
Medium Ensure Terraform module sources use a commit hash Security · 7 places
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (postgis/postgis:14-3.4-alpine) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether postgis/postgis:14-3.4-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
  • Low CVE-2024-58251 fixed in 1.36.1-r31
  • Low CVE-2025-46394 fixed in 1.36.1-r31
Medium 2 known vulnerabilities in libjxl@0.10.2-r0 (postgis/postgis:14-3.4-alpine) Security · 2 CVEs

How to fix

No fixed version of libjxl is available yet. Check whether postgis/postgis:14-3.4-alpine needs libjxl 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-2024-11403 fixed in no fix yet
  • Medium CVE-2024-11498 fixed in no fix yet
Medium 2 known vulnerabilities in zlib@1.3.1-r1 (postgis/postgis:14-3.4-alpine) Security · 2 CVEs

How to fix

Update zlib from 1.3.1-r1 to 1.3.2-r0 or later in postgis/postgis:14-3.4-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.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 fontconfig@2.15.0-r1 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of fontconfig is available yet. Check whether postgis/postgis:14-3.4-alpine needs fontconfig 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-2026-34085 fixed in no fix yet
Medium 1 known vulnerability in freetype@2.13.2-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of freetype is available yet. Check whether postgis/postgis:14-3.4-alpine needs freetype 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-2026-23865 fixed in no fix yet
Medium 1 known vulnerability in lcms2@2.16-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

Update lcms2 from 2.16-r0 to 2.19-r0 or later in postgis/postgis:14-3.4-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.19-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-41254 fixed in 2.19-r0
Medium 1 known vulnerability in libgcrypt@1.10.3-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of libgcrypt is available yet. Check whether postgis/postgis:14-3.4-alpine needs libgcrypt 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-2026-41989 fixed in no fix yet
Medium 1 known vulnerability in openjpeg@2.5.2-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of openjpeg is available yet. Check whether postgis/postgis:14-3.4-alpine needs openjpeg 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-54874 fixed in no fix yet
Medium 1 known vulnerability in openldap@2.6.7-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of openldap is available yet. Check whether postgis/postgis:14-3.4-alpine needs openldap 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-2026-22185 fixed in no fix yet
Medium 1 known vulnerability in util-linux@2.40.1-r1 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of util-linux is available yet. Check whether postgis/postgis:14-3.4-alpine needs util-linux 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-2026-27456 fixed in no fix yet
Medium Ensure public API gateway are protected by WAF Security · 1 place

Ensure public API gateway are protected by WAF

Documentation

Where

Medium Ensure CloudFront distribution has a response headers policy attached Security · 1 place

Ensure CloudFront distribution has a response headers policy attached

Documentation

Where

Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 1 place

Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability

Documentation

Where

Medium Ensure AWS API Gateway endpoints uses client certificate authentication Security · 1 place

Ensure AWS API Gateway endpoints uses client certificate authentication

Documentation

Where

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 1 place

Ensure that AWS Lambda function is configured for function-level concurrent execution limit

Documentation

Where

Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 1 place

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that AWS Lambda function is configured inside a VPC Security · 1 place

Ensure that AWS Lambda function is configured inside a VPC

Documentation

Where

Medium Ensure API Gateway caching is enabled Security · 1 place

Ensure API Gateway caching is enabled

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 1 place

Ensure that CloudWatch Log Group is encrypted by KMS

Documentation

Where

Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher Security · 1 place

Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher

Documentation

Where

Medium Ensure API Gateway method setting caching is enabled Security · 1 place

Ensure API Gateway method setting caching is enabled

Documentation

Where

Medium Ensure Create before destroy for API Gateway Security · 1 place

Ensure Create before destroy for API Gateway

Documentation

Where

Medium Ensure AWS Lambda function is configured to validate code-signing Security · 1 place

Ensure AWS Lambda function is configured to validate code-signing

Documentation

Where

Medium Ensure Data Trace is not enabled in API Gateway Method Settings Security · 1 place

Ensure Data Trace is not enabled in API Gateway Method Settings

Documentation

Where

Medium Ensure CloudFront distribution has a default root object configured Security · 1 place

Ensure CloudFront distribution has a default root object configured

Documentation

Where

Medium Ensure CloudFront distributions should have origin failover configured Security · 1 place

Ensure CloudFront distributions should have origin failover configured

Documentation

Where

Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 1 place

Ensure CloudWatch log groups retains logs for at least 1 year

Documentation

Where

Medium Ensure AWS CloudFront web distribution has geo restriction enabled Security · 1 place

Ensure AWS CloudFront web distribution has geo restriction enabled

Documentation

Where

Medium X-Ray tracing is enabled for Lambda Security · 1 place
Medium Ensure there is no open access to back-end resources through API Security · 1 place

Ensure there is no open access to back-end resources through API

Documentation

Where

Medium CloudFront Distribution should have WAF enabled Security · 1 place

CloudFront Distribution should have WAF enabled

Documentation

Where

Medium Ensure API Gateway has X-Ray Tracing enabled Security · 1 place

Ensure API Gateway has X-Ray Tracing enabled

Documentation

Where

Medium Ensure API Gateway has Access Logging enabled Security · 1 place

Ensure API Gateway has Access Logging enabled

Documentation

Where

Medium Ensure CloudFront distribution has Access Logging enabled Security · 1 place

Ensure CloudFront distribution has Access Logging enabled

Documentation

Where

Medium API Gateway REST Instead of HTTP API Cost · 1 place

aws_api_gateway_rest_api (REST API) costs ~3.5x more per million requests than aws_apigatewayv2_api (HTTP API). Most modern use cases are supported by the HTTP API.

How to fix

Migrate to aws_apigatewayv2_api (HTTP API v2) unless REST-specific features (usage plans, request validation, custom authorizers v1) are required.

Where

Low 2

Low 1 known vulnerability in cairo@1.18.0-r0 (postgis/postgis:14-3.4-alpine) Security · 1 CVE

How to fix

No fixed version of cairo is available yet. Check whether postgis/postgis:14-3.4-alpine needs cairo 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

  • Low CVE-2025-50422 fixed in no fix yet
Low Large Root Volume Cost · 1 place

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

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.