InfraScan Cloud

Repository scan

marble

checkmarble/marble · branch main · scanned 5 Mar 2026 · 64 resources

COverall
DSecurity
–Reliability · N/A
BCost
300findings · 0 critical, 83 high
—no cost findings with a savings estimate

High 126

High 17 known vulnerabilities in openssl@3.3.1-r3 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 17 CVEs

How to fix

Update openssl from 3.3.1-r3 to 3.3.6-r0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 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-2024-6119 fixed in 3.3.2-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-2025-15467 fixed in 3.3.6-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
  • Medium CVE-2024-12797 fixed in 3.3.3-r0
  • Medium CVE-2025-9231 fixed in 3.3.5-r0
High 16 known vulnerabilities in stdlib@1.24.6 (postgres:15) Security · 16 CVEs

How to fix

Update stdlib from 1.24.6 to 1.24.9 or later in postgres:15. 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.24.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-2025-58187 fixed in 1.24.9
  • High CVE-2025-58188 fixed in 1.24.8
  • High CVE-2025-61723 fixed in 1.24.8
  • High CVE-2025-61725 fixed in 1.24.8
  • High CVE-2025-61726 fixed in 1.24.12
  • High CVE-2025-61729 fixed in 1.24.11
  • High CVE-2025-68121 fixed in 1.24.13
  • Medium CVE-2025-58183 fixed in 1.24.8
  • Medium CVE-2025-47912 fixed in 1.24.8
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-58186 fixed in 1.24.8
  • Medium CVE-2025-58189 fixed in 1.24.8
  • Medium CVE-2025-61724 fixed in 1.24.8
  • Medium CVE-2025-61730 fixed in 1.24.12
  • Medium CVE-2025-61727 fixed in 1.24.11
  • Medium CVE-2025-61728 fixed in 1.24.12
High 12 known vulnerabilities in minimatch@9.0.5 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 12 CVEs

How to fix

Update minimatch from 9.0.5 to 9.0.7 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 9.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-27903 fixed in 9.0.7
  • High CVE-2026-27903 fixed in 6.2.2
  • High CVE-2026-27903 fixed in 5.1.8
  • High CVE-2026-27903 fixed in 3.1.3
  • High CVE-2026-27904 fixed in 5.1.8
  • High CVE-2026-27904 fixed in 9.0.7
  • High CVE-2026-27904 fixed in 3.1.4
  • High CVE-2026-27904 fixed in 6.2.2
  • High CVE-2026-26996 fixed in 10.2.1
  • High CVE-2026-26996 fixed in 10.2.1
  • High CVE-2026-26996 fixed in 10.2.1
  • High CVE-2026-26996 fixed in 10.2.1
High 12 known vulnerabilities in openjdk11@11.0.24_p8-r0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 12 CVEs

How to fix

Update openjdk11 from 11.0.24_p8-r0 to 11.0.27_p6-r0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 11.0.27_p6-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-21587 fixed in 11.0.27_p6-r0
  • High CVE-2025-30749 fixed in 11.0.28_p6-r0
  • High CVE-2025-50106 fixed in 11.0.28_p6-r0
  • High CVE-2025-50059 fixed in 11.0.28_p6-r0
  • Medium CVE-2024-21235 fixed in 11.0.25_p9-r0
  • Medium CVE-2025-21502 fixed in 11.0.26_p4-r0
  • Medium CVE-2025-30754 fixed in 11.0.28_p6-r0
  • Medium CVE-2025-30698 fixed in 11.0.27_p6-r0
  • Medium CVE-2025-30761 fixed in 11.0.28_p6-r0
  • Low CVE-2024-21208 fixed in 11.0.25_p9-r0
  • Low CVE-2024-21210 fixed in 11.0.25_p9-r0
  • Low CVE-2024-21217 fixed in 11.0.25_p9-r0
High 8 known vulnerabilities in libpng@1.6.43-r0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 8 CVEs

How to fix

Update libpng from 1.6.43-r0 to 1.6.53-r0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.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-25646 fixed in 1.6.55-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 5 known vulnerabilities in tar@6.2.1 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 5 CVEs

How to fix

Update tar from 6.2.1 to 7.5.8 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 7.5.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-26960 fixed in 7.5.8
  • High CVE-2026-23745 fixed in 7.5.3
  • High CVE-2026-24842 fixed in 7.5.7
  • High GHSA-qffp-2rhf-9h96 fixed in 7.5.10
  • High CVE-2026-23950 fixed in 7.5.4
High 5 known vulnerabilities in react-router@7.9.4 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 5 CVEs

How to fix

Update react-router from 7.9.4 to 7.12.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 7.12.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-2026-22029 fixed in 7.12.0
  • High CVE-2026-21884 fixed in 7.12.0
  • Medium CVE-2025-68470 fixed in 6.30.2
  • Medium CVE-2025-68470 fixed in 7.9.6
  • Medium CVE-2026-22030 fixed in 7.12.0
High 4 known vulnerabilities in bcpkix-jdk18on@1.76 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 4 CVEs

How to fix

Update bcpkix-jdk18on from 1.76 to 1.78 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.78); 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-29857 fixed in 1.78
  • Medium CVE-2024-30172 fixed in 1.78
  • Medium CVE-2024-30171 fixed in 1.78
  • Medium CVE-2025-8916 fixed in 1.79
High 4 known vulnerabilities in devalue@5.3.2 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 4 CVEs

How to fix

Update devalue from 5.3.2 to 5.6.2 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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); 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-22774 fixed in 5.6.2
  • High CVE-2026-22775 fixed in 5.6.2
  • Low GHSA-33hq-fvwr-56pm fixed in 5.6.3
  • Low GHSA-8qm3-746x-r74r fixed in 5.6.3
High 3 known vulnerabilities in jackson-core@2.13.4 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 3 CVEs

How to fix

Update jackson-core from 2.13.4 to 2.15.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.15.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-52999 fixed in 2.15.0
  • High GHSA-72hv-8253-57qq fixed in 2.18.6
  • High GHSA-72hv-8253-57qq fixed in 2.18.6
High 3 known vulnerabilities in path-to-regexp@1.8.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 3 CVEs

How to fix

Update path-to-regexp from 1.8.0 to 1.9.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.9.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-2024-45296 fixed in 1.9.0
  • High CVE-2024-45296 fixed in 0.1.10
  • High CVE-2024-52798 fixed in 0.1.12
High 3 known vulnerabilities in minimatch@9.0.5 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 3 CVEs

How to fix

Update minimatch from 9.0.5 to 9.0.7 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 9.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-27903 fixed in 9.0.7
  • High CVE-2026-27904 fixed in 9.0.7
  • High CVE-2026-26996 fixed in 10.2.1
High 2 known vulnerabilities in lz4-java@1.8.0 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

No fixed version of lz4-java is available yet. Check whether docker.elastic.co/elasticsearch/elasticsearch:8.14.3 needs lz4-java 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-66566 fixed in no fix yet
  • High CVE-2025-12183 fixed in 1.8.1
High 2 known vulnerabilities in nimbus-jose-jwt@9.23 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update nimbus-jose-jwt from 9.23 to 9.37.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 9.37.2); 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-2023-52428 fixed in 9.37.2
  • Medium CVE-2025-53864 fixed in 10.0.2
High 2 known vulnerabilities in tika-parser-pdf-module@2.9.1 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update tika-parser-pdf-module from 2.9.1 to 3.2.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.2.2); 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-54988 fixed in 3.2.2
  • High CVE-2025-66516 fixed in 3.2.2
High 2 known vulnerabilities in cross-spawn@6.0.5 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update cross-spawn from 6.0.5 to 6.0.6 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 6.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-2024-21538 fixed in 6.0.6
  • High CVE-2024-21538 fixed in 7.0.5
High 2 known vulnerabilities in form-data@4.0.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update form-data from 4.0.0 to 4.0.4 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.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

  • High CVE-2025-7783 fixed in 4.0.4
  • High CVE-2025-7783 fixed in 2.5.4
High 2 known vulnerabilities in giflib@5.2.2-r0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

No fixed version of giflib is available yet. Check whether europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest 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
  • Medium CVE-2024-45993 fixed in no fix yet
High 2 known vulnerabilities in glob@10.4.2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update glob from 10.4.2 to 11.1.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 11.1.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-64756 fixed in 11.1.0
  • High CVE-2025-64756 fixed in 11.1.0
High 2 known vulnerabilities in jws@3.2.2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update jws from 3.2.2 to 3.2.3 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 3.2.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-2025-65945 fixed in 3.2.3
  • High CVE-2025-65945 fixed in 4.0.1
High 2 known vulnerabilities in libtasn1@4.19.0-r2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update libtasn1 from 4.19.0-r2 to 4.21.0-r0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.21.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-13151 fixed in 4.21.0-r0
  • Medium CVE-2024-12133 fixed in 4.20.0-r0
High 2 known vulnerabilities in react@2.17.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 2 CVEs

How to fix

Update react from 2.17.0 to 2.17.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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.17.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-59057 fixed in 2.17.1
  • High CVE-2026-21884 fixed in 2.17.3
High 1 known vulnerability in json-smart@2.4.8 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update json-smart from 2.4.8 to 2.4.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.4.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-2023-1370 fixed in 2.4.9
High 1 known vulnerability in netty-codec-http2@4.1.107.Final (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update netty-codec-http2 from 4.1.107.Final to 4.1.124.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.1.124.Final); 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-55163 fixed in 4.1.124.Final
High 1 known vulnerability in netty-handler@4.1.107.Final (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update netty-handler from 4.1.107.Final to 4.1.118.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.1.118.Final); 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-24970 fixed in 4.1.118.Final
High 1 known vulnerability in protobuf-java@3.21.9 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update protobuf-java from 3.21.9 to 3.25.5 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.25.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-2024-7254 fixed in 3.25.5
High 1 known vulnerability in tika-core@2.9.1 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update tika-core from 2.9.1 to 3.2.2 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.2.2); 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-66516 fixed in 3.2.2
High 1 known vulnerability in basic-auth-connect@1.0.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update basic-auth-connect from 1.0.0 to 1.1.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.1.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-2024-47178 fixed in 1.1.0
High 1 known vulnerability in basic-ftp@5.0.5 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update basic-ftp from 5.0.5 to 5.2.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 5.2.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-2026-27699 fixed in 5.2.0
High 1 known vulnerability in body-parser@1.20.2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update body-parser from 1.20.2 to 1.20.3 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.20.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-2024-45590 fixed in 1.20.3
High 1 known vulnerability in musl@1.2.5-r0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update musl from 1.2.5-r0 to 1.2.5-r1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.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 1 known vulnerability in sdk@1.39.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0) Security · 1 CVE

How to fix

Update sdk from 1.39.0 to 1.40.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0. 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.40.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-2026-24051 fixed in 1.40.0
High 1 known vulnerability in glob@10.4.5 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update glob from 10.4.5 to 11.1.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 11.1.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-64756 fixed in 11.1.0
High 1 known vulnerability in node@2.17.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update node from 2.17.0 to 2.17.2 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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.17.2); 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-61686 fixed in 2.17.2
High 1 known vulnerability in router@1.23.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update router from 1.23.0 to 1.23.2 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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.23.2); 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-22029 fixed in 1.23.2
High Missing AWS Budget Cost · 1 place

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

Medium 121

Medium 7 known vulnerabilities in krb5@1.17-6ubuntu4.4 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 7 CVEs

How to fix

Update krb5 from 1.17-6ubuntu4.4 to 1.17-6ubuntu4.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.17-6ubuntu4.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

  • Medium CVE-2025-24528 fixed in 1.17-6ubuntu4.9
  • Medium CVE-2025-3576 fixed in 1.17-6ubuntu4.11
  • Medium CVE-2024-37370 fixed in 1.17-6ubuntu4.6
  • Medium CVE-2024-3596 fixed in 1.17-6ubuntu4.8
  • Medium CVE-2024-37371 fixed in 1.17-6ubuntu4.6
  • Low CVE-2024-26458 fixed in 1.17-6ubuntu4.9
  • Low CVE-2024-26461 fixed in 1.17-6ubuntu4.9
Medium 5 known vulnerabilities in bcprov-jdk18on@1.76 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 5 CVEs

How to fix

Update bcprov-jdk18on from 1.76 to 1.78 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.78); 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-2024-29857 fixed in 1.78
  • Medium CVE-2024-30171 fixed in 1.78
  • Medium CVE-2024-34447 fixed in 1.78
  • Medium CVE-2025-8885 fixed in 1.78
  • Medium CVE-2024-30172 fixed in 1.78
Medium 5 known vulnerabilities in elasticsearch@8.14.3 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 5 CVEs

How to fix

Update elasticsearch from 8.14.3 to 8.15.1 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.15.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

  • Medium CVE-2024-52981 fixed in 8.15.1
  • Medium CVE-2025-37727 fixed in 8.18.8
  • Medium CVE-2024-52979 fixed in 8.16.0
  • Medium CVE-2024-52980 fixed in 8.15.1
  • Medium CVE-2025-37731 fixed in 8.19.8
Medium 4 known vulnerabilities in qs@6.13.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 4 CVEs

How to fix

Update qs from 6.13.0 to 6.14.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 6.14.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

  • Medium CVE-2025-15284 fixed in 6.14.1
  • Medium CVE-2025-15284 fixed in 6.14.1
  • Low CVE-2026-2391 fixed in 6.14.2
  • Low CVE-2026-2391 fixed in 6.14.2
Medium Ensure every security group and rule has a description Security · 4 places
Medium 3 known vulnerabilities in curl@7.68.0-1ubuntu2.22 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 3 CVEs

How to fix

Update curl from 7.68.0-1ubuntu2.22 to 7.68.0-1ubuntu2.24 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 7.68.0-1ubuntu2.24); 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-2024-8096 fixed in 7.68.0-1ubuntu2.24
  • Medium CVE-2024-7264 fixed in 7.68.0-1ubuntu2.23
  • Low CVE-2024-11053 fixed in 7.68.0-1ubuntu2.25
Medium 3 known vulnerabilities in netty-codec-http@4.1.107.Final (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 3 CVEs

How to fix

Update netty-codec-http from 4.1.107.Final to 4.1.108.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.1.108.Final); 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-2024-29025 fixed in 4.1.108.Final
  • Medium CVE-2025-67735 fixed in 4.1.129.Final
  • Low CVE-2025-58056 fixed in 4.1.125.Final
Medium 3 known vulnerabilities in busybox@1.36.1-r29 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 3 CVEs

How to fix

No fixed version of busybox is available yet. Check whether europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest 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 bc-fips@1.0.2.4 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update bc-fips from 1.0.2.4 to 1.0.2.5 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.0.2.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

  • Medium CVE-2024-29857 fixed in 1.0.2.5
  • Medium CVE-2025-8885 fixed in 2.1.0
Medium 2 known vulnerabilities in commons-compress@1.24.0 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update commons-compress from 1.24.0 to 1.26.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.26.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-2024-25710 fixed in 1.26.0
  • Medium CVE-2024-26308 fixed in 1.26.0
Medium 2 known vulnerabilities in commons-lang3@3.13.0 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update commons-lang3 from 3.13.0 to 3.18.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.18.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-2025-48924 fixed in 3.18.0
  • Medium CVE-2025-48924 fixed in 3.18.0
Medium 2 known vulnerabilities in glibc@2.31-0ubuntu9.16 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update glibc from 2.31-0ubuntu9.16 to 2.31-0ubuntu9.17 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.31-0ubuntu9.17); 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-2025-0395 fixed in 2.31-0ubuntu9.17
  • Medium CVE-2025-4802 fixed in 2.31-0ubuntu9.18
Medium 2 known vulnerabilities in log4j-core@2.19.0 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update log4j-core from 2.19.0 to 2.25.3 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.25.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-2025-68161 fixed in 2.25.3
  • Medium CVE-2025-68161 fixed in 2.25.3
Medium 2 known vulnerabilities in netty-common@4.1.107.Final (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update netty-common from 4.1.107.Final to 4.1.115.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.1.115.Final); 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-2024-47535 fixed in 4.1.115.Final
  • Medium CVE-2025-25193 fixed in 4.1.118.Final
Medium 2 known vulnerabilities in sqlite3@3.31.1-4ubuntu0.6 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 2 CVEs

How to fix

Update sqlite3 from 3.31.1-4ubuntu0.6 to 3.31.1-4ubuntu0.7 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.31.1-4ubuntu0.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

  • Medium CVE-2025-52099 fixed in 3.31.1-4ubuntu0.7
  • Medium CVE-2025-29088 fixed in 3.31.1-4ubuntu0.7
Medium 2 known vulnerabilities in ajv@6.12.6 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update ajv from 6.12.6 to 8.18.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.18.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-2025-69873 fixed in 8.18.0
  • Medium CVE-2025-69873 fixed in 8.18.0
Medium 2 known vulnerabilities in qs@6.11.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update qs from 6.11.0 to 6.14.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 6.14.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

  • Medium CVE-2025-15284 fixed in 6.14.1
  • Low CVE-2026-2391 fixed in 6.14.2
Medium 2 known vulnerabilities in aws-sdk-go@1.55.7 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0) Security · 2 CVEs

How to fix

No fixed version of aws-sdk-go is available yet. Check whether europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
  • Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in tar@1.35%2Bdfsg-3.1 (postgres:15) Security · 2 CVEs

How to fix

No fixed version of tar is available yet. Check whether postgres:15 needs tar 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-45582 fixed in no fix yet
  • Low CVE-2005-2541 fixed in no fix yet
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 2 places

Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances

Documentation

Where

Medium Ensure VPC subnets do not assign public IP by default Security · 2 places

Ensure VPC subnets do not assign public IP by default

Documentation

Where

Medium Ensure that GCP Cloud Run services are not anonymously or publicly accessible Security · 2 places
Medium Bucket should log access Security · 2 places
Medium Ensure Cloud storage has versioning enabled Security · 2 places
Medium Missing Spot Instance Usage Cost · 2 places

No spot instances detected. Spot instances can save 50-90% on compute costs for interruptible workloads.

How to fix

Use spot instances for batch jobs, data analysis, and optional tasks. Consider aws_spot_instance_request or spot_price in launch templates.

Where

Medium 1 known vulnerability in gnupg2@2.2.19-3ubuntu2.2 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update gnupg2 from 2.2.19-3ubuntu2.2 to 2.2.19-3ubuntu2.4 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.2.19-3ubuntu2.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-2025-30258 fixed in 2.2.19-3ubuntu2.4
Medium 1 known vulnerability in gnutls28@3.6.13-2ubuntu1.11 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update gnutls28 from 3.6.13-2ubuntu1.11 to 3.6.13-2ubuntu1.12 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.6.13-2ubuntu1.12); 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-2024-12243 fixed in 3.6.13-2ubuntu1.12
Medium 1 known vulnerability in libtasn1-6@4.16.0-2 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update libtasn1-6 from 4.16.0-2 to 4.16.0-2ubuntu0.1 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.16.0-2ubuntu0.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

  • Medium CVE-2024-12133 fixed in 4.16.0-2ubuntu0.1
Medium 1 known vulnerability in netty-codec@4.1.107.Final (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update netty-codec from 4.1.107.Final to 4.1.125.Final or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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 4.1.125.Final); 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-2025-58057 fixed in 4.1.125.Final
Medium 1 known vulnerability in poi-ooxml@5.2.3 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update poi-ooxml from 5.2.3 to 5.4.0 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.4.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-2025-31672 fixed in 5.4.0
Medium 1 known vulnerability in reactor-netty-http@1.0.39 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update reactor-netty-http from 1.0.39 to 1.2.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.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

  • Medium CVE-2025-22227 fixed in 1.2.8
Medium 1 known vulnerability in x-pack-core@8.14.3 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update x-pack-core from 8.14.3 to 8.19.8 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.19.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

  • Medium CVE-2025-68390 fixed in 8.19.8
Medium 1 known vulnerability in x-pack-security@8.14.3 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 1 CVE

How to fix

Update x-pack-security from 8.14.3 to 8.19.9 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.19.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

  • Medium CVE-2025-68384 fixed in 8.19.9
Medium 1 known vulnerability in js-yaml@4.1.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update js-yaml from 4.1.0 to 4.1.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.1.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

  • Medium CVE-2025-64718 fixed in 4.1.1
Medium 1 known vulnerability in lodash@4.17.21 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update lodash from 4.17.21 to 4.17.23 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.17.23); 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-2025-13465 fixed in 4.17.23
Medium 1 known vulnerability in lodash@4.17.21 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update lodash from 4.17.21 to 4.17.23 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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.17.23); 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-2025-13465 fixed in 4.17.23
Medium 1 known vulnerability in mdast-util-to-hast@13.2.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update mdast-util-to-hast from 13.2.0 to 13.2.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 13.2.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

  • Medium CVE-2025-66400 fixed in 13.2.1
Medium 1 known vulnerability in server-runtime@2.17.0 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update server-runtime from 2.17.0 to 2.17.3 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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.17.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-22030 fixed in 2.17.3
Medium 1 known vulnerability in undici@6.21.3 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1) Security · 1 CVE

How to fix

Update undici from 6.21.3 to 6.23.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.61.1. 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 6.23.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-22036 fixed in 6.23.0
Medium Ensure VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

and 38 more groups with 38 findings

Low 53

Low 7 known vulnerabilities in glibc@2.41-12%2Bdeb13u1 (postgres:15) Security · 7 CVEs

How to fix

No fixed version of glibc is available yet. Check whether postgres:15 needs glibc 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-2010-4756 fixed in no fix yet
  • Low CVE-2018-20796 fixed in no fix yet
  • Low CVE-2019-1010022 fixed in no fix yet
  • Low CVE-2019-1010023 fixed in no fix yet
  • Low CVE-2019-1010024 fixed in no fix yet
  • Low CVE-2019-1010025 fixed in no fix yet
  • Low CVE-2019-9192 fixed in no fix yet
Low 5 known vulnerabilities in openssl@1.1.1f-1ubuntu2.22 (docker.elastic.co/elasticsearch/elasticsearch:8.14.3) Security · 5 CVEs

How to fix

Update openssl from 1.1.1f-1ubuntu2.22 to 1.1.1f-1ubuntu2.24 or later in docker.elastic.co/elasticsearch/elasticsearch:8.14.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.1f-1ubuntu2.24); 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-2024-13176 fixed in 1.1.1f-1ubuntu2.24
  • Low CVE-2024-2511 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-4741 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-5535 fixed in 1.1.1f-1ubuntu2.23
  • Low CVE-2024-9143 fixed in 1.1.1f-1ubuntu2.24
Low 5 known vulnerabilities in openldap@2.6.10%2Bdfsg-1 (postgres:15) Security · 5 CVEs

How to fix

No fixed version of openldap is available yet. Check whether postgres:15 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

  • Low CVE-2015-3276 fixed in no fix yet
  • Low CVE-2017-14159 fixed in no fix yet
  • Low CVE-2017-17740 fixed in no fix yet
  • Low CVE-2020-15719 fixed in no fix yet
  • Low CVE-2026-22185 fixed in no fix yet
Low 4 known vulnerabilities in systemd@257.9-1~deb13u1 (postgres:15) Security · 4 CVEs

How to fix

No fixed version of systemd is available yet. Check whether postgres:15 needs systemd 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-2013-4392 fixed in no fix yet
  • Low CVE-2023-31437 fixed in no fix yet
  • Low CVE-2023-31438 fixed in no fix yet
  • Low CVE-2023-31439 fixed in no fix yet
Low 3 known vulnerabilities in krb5@1.21.3-5 (postgres:15) Security · 3 CVEs

How to fix

No fixed version of krb5 is available yet. Check whether postgres:15 needs krb5 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-2018-5709 fixed in no fix yet
  • Low CVE-2024-26458 fixed in no fix yet
  • Low CVE-2024-26461 fixed in no fix yet
Low 3 known vulnerabilities in libxml2@2.12.7%2Bdfsg%2Breally2.9.14-2.1%2Bdeb13u2 (postgres:15) Security · 3 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether postgres:15 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

  • Low CVE-2025-12863 fixed in no fix yet
  • Low CVE-2025-8732 fixed in no fix yet
  • Low CVE-2026-1757 fixed in no fix yet
Low 2 known vulnerabilities in brace-expansion@1.1.11 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update brace-expansion from 1.1.11 to 1.1.12 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.1.12); 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-2025-5889 fixed in 1.1.12
  • Low CVE-2025-5889 fixed in 2.0.2
Low 2 known vulnerabilities in tmp@0.2.3 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 2 CVEs

How to fix

Update tmp from 0.2.3 to 0.2.4 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.2.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

  • Low CVE-2025-54798 fixed in 0.2.4
  • Low CVE-2025-54798 fixed in 0.2.4
Low 2 known vulnerabilities in coreutils@9.7-3 (postgres:15) Security · 2 CVEs

How to fix

No fixed version of coreutils is available yet. Check whether postgres:15 needs coreutils 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-2017-18018 fixed in no fix yet
  • Low CVE-2025-5278 fixed in no fix yet
Low 2 known vulnerabilities in libgcrypt20@1.11.0-7 (postgres:15) Security · 2 CVEs

How to fix

No fixed version of libgcrypt20 is available yet. Check whether postgres:15 needs libgcrypt20 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-2018-6829 fixed in no fix yet
  • Low CVE-2024-2236 fixed in no fix yet
Low 1 known vulnerability in cookie@0.6.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update cookie from 0.6.0 to 0.7.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.7.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-2024-47764 fixed in 0.7.0
Low 1 known vulnerability in diff@5.2.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update diff from 5.2.0 to 5.2.2 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 5.2.2); 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-24001 fixed in 5.2.2
Low 1 known vulnerability in express@4.19.2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update express from 4.19.2 to 4.20.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.20.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-2024-43796 fixed in 4.20.0
Low 1 known vulnerability in on-headers@1.0.2 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update on-headers from 1.0.2 to 1.1.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.1.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-2025-7339 fixed in 1.1.0
Low 1 known vulnerability in once@2.0.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update once from 2.0.0 to 3.0.1 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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 3.0.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

  • Low CVE-2026-3449 fixed in 3.0.1
Low 1 known vulnerability in send@0.18.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update send from 0.18.0 to 0.19.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.19.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-2024-43799 fixed in 0.19.0
Low 1 known vulnerability in serve-static@1.15.0 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

Update serve-static from 1.15.0 to 1.16.0 or later in europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator: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.16.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-2024-43800 fixed in 1.16.0
Low 1 known vulnerability in zlib@1.3.1-r1 (europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest) Security · 1 CVE

How to fix

No fixed version of zlib is available yet. Check whether europe-west1-docker.pkg.dev/marble-infra/marble/firebase-emulator:latest needs zlib 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-2026-27171 fixed in no fix yet
Low 1 known vulnerability in imaging@1.6.2 (europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0) Security · 1 CVE

How to fix

No fixed version of imaging is available yet. Check whether europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.61.0 needs imaging 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-2023-36308 fixed in no fix yet
Low 1 known vulnerability in apt@3.0.3 (postgres:15) Security · 1 CVE

How to fix

No fixed version of apt is available yet. Check whether postgres:15 needs apt 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-2011-3374 fixed in no fix yet
Low 1 known vulnerability in gnupg2@2.4.7-21%2Bdeb13u1 (postgres:15) Security · 1 CVE

How to fix

No fixed version of gnupg2 is available yet. Check whether postgres:15 needs gnupg2 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-2022-3219 fixed in no fix yet
Low 1 known vulnerability in libxslt@1.1.35-1.2%2Bdeb13u2 (postgres:15) Security · 1 CVE

How to fix

No fixed version of libxslt is available yet. Check whether postgres:15 needs libxslt 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-2015-9019 fixed in no fix yet
Low 1 known vulnerability in openssl@3.5.4-1~deb13u2 (postgres:15) Security · 1 CVE

How to fix

No fixed version of openssl is available yet. Check whether postgres:15 needs openssl 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-2010-0928 fixed in no fix yet
Low 1 known vulnerability in perl@5.40.1-6 (postgres:15) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether postgres:15 needs perl 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-2011-4116 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.17.4-2 (postgres:15) Security · 1 CVE

How to fix

No fixed version of shadow is available yet. Check whether postgres:15 needs shadow 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-2007-5686 fixed in no fix yet
Low 1 known vulnerability in sqlite3@3.46.1-7 (postgres:15) Security · 1 CVE

How to fix

No fixed version of sqlite3 is available yet. Check whether postgres:15 needs sqlite3 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-2021-45346 fixed in no fix yet
Low 1 known vulnerability in util-linux@2.41-5 (postgres:15) Security · 1 CVE

How to fix

No fixed version of util-linux is available yet. Check whether postgres:15 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

  • Low CVE-2022-0563 fixed in no fix yet
Low Elastic IP Usage 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

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 5 Mar 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.