InfraScan Cloud

Repository scan

gigadb-website

gigascience/gigadb-website · branch main · scanned 25 Jun 2026 · 210 resources

DOverall
FSecurity
–Reliability · N/A
BCost
1,510findings · 0 critical, 305 high
$50.00–$90.00estimated savings per month, from the code

High 1,330

High 559 known vulnerabilities in unknown@unknown (selenium/standalone-chrome:3.141.59-oxygen) Security · 559 CVEs

How to fix

No fixed version of unknown is available yet. Check whether selenium/standalone-chrome:3.141.59-oxygen 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-2021-33910 fixed in no fix yet
  • High CVE-2020-1971 fixed in no fix yet
  • High CVE-2021-3449 fixed in no fix yet
  • High CVE-2020-27216 fixed in no fix yet
  • High CVE-2020-27216 fixed in no fix yet
  • High CVE-2020-27216 fixed in no fix yet
  • High CVE-2024-13009 fixed in no fix yet
  • High CVE-2023-0286 fixed in no fix yet
  • High CVE-2026-2332 fixed in no fix yet
  • High CVE-2017-18640 fixed in no fix yet
  • High CVE-2018-12545 fixed in no fix yet
  • High CVE-2021-0341 fixed in no fix yet
  • High CVE-2021-28165 fixed in no fix yet
  • High CVE-2021-28165 fixed in no fix yet
  • High CVE-2021-28165 fixed in no fix yet
  • High CVE-2021-28165 fixed in no fix yet
  • High CVE-2022-0778 fixed in no fix yet
  • High CVE-2022-25857 fixed in no fix yet
  • High CVE-2018-16864 fixed in no fix yet
  • High CVE-2018-16865 fixed in no fix yet
  • and 539 more
High 413 known vulnerabilities in unknown@unknown (seleniarm/standalone-firefox:latest) Security · 413 CVEs

How to fix

No fixed version of unknown is available yet. Check whether seleniarm/standalone-firefox:latest needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-5222 fixed in no fix yet
  • High CVE-2025-24528 fixed in no fix yet
  • High CVE-2026-32741 fixed in no fix yet
  • High CVE-2026-32882 fixed in no fix yet
  • High CVE-2025-6965 fixed in no fix yet
  • High CVE-2025-9951 fixed in no fix yet
  • High CVE-2025-49176 fixed in no fix yet
  • High CVE-2025-49179 fixed in no fix yet
  • High CVE-2025-62229 fixed in no fix yet
  • High CVE-2025-62230 fixed in no fix yet
  • High CVE-2025-62231 fixed in no fix yet
  • High CVE-2025-70103 fixed in no fix yet
  • High CVE-2026-42584 fixed in no fix yet
  • High CVE-2026-42584 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2026-32775 fixed in no fix yet
  • High CVE-2026-35535 fixed in no fix yet
  • High CVE-2023-24329 fixed in no fix yet
  • High CVE-2023-35790 fixed in no fix yet
  • High CVE-2023-52356 fixed in no fix yet
  • and 393 more
High 157 known vulnerabilities in unknown@unknown (gitlab/gitlab-runner:latest) Security · 157 CVEs

How to fix

No fixed version of unknown is available yet. Check whether gitlab/gitlab-runner:latest needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-45447 fixed in no fix yet
  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2026-45022 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 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-32283 fixed in no fix yet
  • and 137 more
High 21 known vulnerabilities in curl@7.83.1-r3 (composer/composer:2.4.3) Security · 21 CVEs

How to fix

Update curl from 7.83.1-r3 to 7.83.1-r4 or later in composer/composer:2.4.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.83.1-r4); 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-42916 fixed in 7.83.1-r4
  • High CVE-2022-43551 fixed in 7.83.1-r5
  • High CVE-2023-28319 fixed in 8.1.0-r0
  • High CVE-2023-38039 fixed in 8.3.0-r0
  • High CVE-2022-42915 fixed in 7.83.1-r4
  • High CVE-2023-27533 fixed in 8.0.1-r0
  • High CVE-2023-27534 fixed in 8.0.1-r0
  • High CVE-2022-32221 fixed in 7.83.1-r4
  • High CVE-2023-38545 fixed in 8.4.0-r0
  • Medium CVE-2023-46219 fixed in 8.5.0-r0
  • Medium CVE-2024-0853 fixed in no fix yet
  • Medium CVE-2023-27538 fixed in 8.0.1-r0
  • Medium CVE-2022-43552 fixed in 7.83.1-r5
  • Medium CVE-2023-27535 fixed in 8.0.1-r0
  • Medium CVE-2023-27536 fixed in 8.0.1-r0
  • Medium CVE-2023-27537 fixed in 8.0.1-r0
  • Medium CVE-2023-28320 fixed in 8.1.0-r0
  • Medium CVE-2023-28321 fixed in 8.1.0-r0
  • Medium CVE-2023-46218 fixed in 8.5.0-r0
  • Low CVE-2023-28322 fixed in 8.1.0-r0
  • and 1 more
High 20 known vulnerabilities in aa_ER@saaho (seleniarm/standalone-firefox:latest) Security · 20 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether seleniarm/standalone-firefox:latest needs aa_ER at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2024-33601 fixed in no fix yet
  • High CVE-2024-33602 fixed in no fix yet
  • High CVE-2025-15281 fixed in no fix yet
  • High CVE-2026-0915 fixed in no fix yet
  • High CVE-2026-4046 fixed in no fix yet
  • High CVE-2025-4802 fixed in no fix yet
  • High CVE-2024-33599 fixed in no fix yet
  • High CVE-2026-0861 fixed in no fix yet
  • Medium CVE-2024-33600 fixed in no fix yet
  • Medium CVE-2025-8058 fixed in no fix yet
  • Medium CVE-2025-0395 fixed in no fix yet
  • 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 CVE-2026-4437 fixed in no fix yet
  • Low CVE-2026-4438 fixed in no fix yet
High 18 known vulnerabilities in unknown@unknown (portainer/portainer-ce:latest) Security · 18 CVEs

How to fix

No fixed version of unknown is available yet. Check whether portainer/portainer-ce:latest needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2025-15558 fixed in no fix yet
  • High CVE-2026-53489 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2026-33748 fixed in no fix yet
  • High CVE-2026-33747 fixed in no fix yet
  • High CVE-2026-53492 fixed in no fix yet
  • High CVE-2024-33662 fixed in no fix yet
  • High CVE-2026-53488 fixed in no fix yet
  • High CVE-2026-53488 fixed in no fix yet
  • High CVE-2026-34040 fixed in no fix yet
  • Medium CVE-2025-47909 fixed in no fix yet
  • Medium CVE-2026-50195 fixed in no fix yet
  • Medium CVE-2026-41568 fixed in no fix yet
  • Medium CVE-2026-33997 fixed in no fix yet
  • Medium CVE-2026-47262 fixed in no fix yet
  • Medium CVE-2026-47262 fixed in no fix yet
High 16 known vulnerabilities in unknown@unknown (certbot/certbot) Security · 16 CVEs

How to fix

No fixed version of unknown is available yet. Check whether certbot/certbot 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 GHSA-4w2j-m93h-cj5j fixed in no fix yet
  • High GHSA-537c-gmf6-5ccf fixed in no fix yet
  • High GHSA-82j2-j2ch-gfr8 fixed in no fix yet
  • High CVE-2026-44431 fixed in no fix yet
  • High CVE-2026-44432 fixed in no fix yet
  • Medium GHSA-3pv8-6f4r-ffg2 fixed in no fix yet
  • Medium GHSA-4gg8-gxpx-9rph fixed in no fix yet
  • Medium GHSA-4gg8-gxpx-9rph fixed in no fix yet
  • Medium CVE-2026-8643 fixed in no fix yet
  • Medium CVE-2023-49092 fixed in no fix yet
  • Medium GHSA-fp55-jw48-c537 fixed in no fix yet
  • Medium CVE-2026-45409 fixed in no fix yet
  • Medium GHSA-3cv2-h65g-fgmm fixed in no fix yet
  • Medium GHSA-vfvv-c25p-m7mm fixed in no fix yet
  • Low GHSA-cq8v-f236-94qc fixed in no fix yet
  • Low GHSA-xx64-wwv2-hcqq fixed in no fix yet
High 15 known vulnerabilities in openssl@3.5.6-r0 (certbot/certbot) Security · 15 CVEs

How to fix

Update openssl from 3.5.6-r0 to 3.5.7-r0 or later in certbot/certbot. 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 14 known vulnerabilities in stdlib@1.22.2 (gitlab/gitlab-runner:latest) Security · 14 CVEs

How to fix

Update stdlib from 1.22.2 to 1.22.7 or later in gitlab/gitlab-runner: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.22.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-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-33811 fixed in 1.25.10
  • High CVE-2026-39836 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-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • High CVE-2026-42504 fixed in 1.26.4
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2024-24788 fixed in 1.22.3
  • Medium CVE-2025-4673 fixed in 1.23.10
High 10 known vulnerabilities in git@2.36.2-r0 (composer/composer:2.4.3) Security · 10 CVEs

How to fix

Update git from 2.36.2-r0 to 2.36.6-r0 or later in composer/composer:2.4.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.36.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-2023-29007 fixed in 2.36.6-r0
  • High CVE-2023-25652 fixed in 2.36.6-r0
  • High CVE-2022-31012 fixed in no fix yet
  • High CVE-2022-39260 fixed in 2.36.3-r0
  • High CVE-2022-23521 fixed in 2.36.4-r0
  • High CVE-2022-41903 fixed in 2.36.4-r0
  • Medium CVE-2022-39253 fixed in 2.36.3-r0
  • Medium CVE-2023-22490 fixed in 2.36.5-r0
  • Medium CVE-2023-23946 fixed in 2.36.5-r0
  • Low CVE-2023-25815 fixed in 2.36.6-r0
High 8 known vulnerabilities in binutils@2.45.1-r0 (certbot/certbot) Security · 8 CVEs

How to fix

No fixed version of binutils is available yet. Check whether certbot/certbot needs binutils 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-69649 fixed in no fix yet
  • High CVE-2025-69650 fixed in no fix yet
  • High CVE-2026-6846 fixed in no fix yet
  • Medium CVE-2025-69644 fixed in no fix yet
  • Medium CVE-2025-69651 fixed in no fix yet
  • Medium CVE-2025-69647 fixed in no fix yet
  • Medium CVE-2025-69648 fixed in no fix yet
  • Medium CVE-2025-69652 fixed in no fix yet
High 8 known vulnerabilities in curl@7.61.1-r0 (rija/docker-alpine-shell-tools:1.0.1) Security · 8 CVEs

How to fix

Update curl from 7.61.1-r0 to 7.61.1-r2 or later in rija/docker-alpine-shell-tools:1.0.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.61.1-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-2018-16890 fixed in 7.61.1-r2
  • High CVE-2018-16840 fixed in 7.61.1-r1
  • High CVE-2019-3822 fixed in 7.61.1-r2
  • High CVE-2019-5481 fixed in 7.61.1-r3
  • High CVE-2019-5482 fixed in 7.61.1-r3
  • Medium CVE-2018-16839 fixed in 7.61.1-r1
  • Medium CVE-2019-3823 fixed in 7.61.1-r2
  • Medium CVE-2018-16842 fixed in 7.61.1-r1
High 7 known vulnerabilities in unknown@unknown (composer/composer:2.4.3) Security · 7 CVEs

How to fix

No fixed version of unknown is available yet. Check whether composer/composer:2.4.3 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-0286 fixed in no fix yet
  • Medium CVE-2022-4304 fixed in no fix yet
  • Medium CVE-2022-4450 fixed in no fix yet
  • Medium CVE-2023-0215 fixed in no fix yet
  • Medium CVE-2023-23916 fixed in no fix yet
  • Low CVE-2023-23914 fixed in no fix yet
  • Low CVE-2023-23915 fixed in no fix yet
High 6 known vulnerabilities in openssl@1.1.1q-r0 (composer/composer:2.4.3) Security · 6 CVEs

How to fix

Update openssl from 1.1.1q-r0 to 1.1.1t-r1 or later in composer/composer:2.4.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.1t-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-2023-0464 fixed in 1.1.1t-r1
  • Medium CVE-2023-0465 fixed in 1.1.1t-r2
  • Medium CVE-2023-3446 fixed in 1.1.1u-r2
  • Medium CVE-2023-3817 fixed in 1.1.1v-r0
  • Medium CVE-2023-5678 fixed in 1.1.1w-r1
  • Medium CVE-2023-2650 fixed in 1.1.1u-r0
High 6 known vulnerabilities in python3@3.10.5-r0 (composer/composer:2.4.3) Security · 6 CVEs

How to fix

Update python3 from 3.10.5-r0 to 3.10.9-r0 or later in composer/composer:2.4.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.10.9-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-2022-45061 fixed in 3.10.9-r0
  • High CVE-2022-42919 fixed in 3.10.9-r0
  • High CVE-2023-6597 fixed in 3.10.14-r0
  • High CVE-2022-37454 fixed in 3.10.9-r0
  • Medium CVE-2023-40217 fixed in 3.10.13-r0
  • Medium CVE-2024-0450 fixed in 3.10.14-r0
High 6 known vulnerabilities in crypto@0.50.0 (gitlab/gitlab-runner:latest) Security · 6 CVEs

How to fix

Update crypto from 0.50.0 to 0.52.0 or later in gitlab/gitlab-runner: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.52.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-46597 fixed in 0.52.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
High 5 known vulnerabilities in openssh@9.0_p1-r2 (composer/composer:2.4.3) Security · 5 CVEs

How to fix

Update openssh from 9.0_p1-r2 to 9.0_p1-r3 or later in composer/composer:2.4.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.0_p1-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-2023-28531 fixed in 9.0_p1-r3
  • High CVE-2023-38408 fixed in 9.0_p1-r4
  • Medium CVE-2023-51384 fixed in 9.0_p1-r5
  • Medium CVE-2023-48795 fixed in 9.0_p1-r5
  • Medium CVE-2023-51385 fixed in 9.0_p1-r5
High 4 known vulnerabilities in expat@2.4.9-r0 (composer/composer:2.4.3) Security · 4 CVEs

How to fix

Update expat from 2.4.9-r0 to 2.5.0-r0 or later in composer/composer:2.4.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.5.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-2022-43680 fixed in 2.5.0-r0
  • High CVE-2023-52425 fixed in 2.6.0-r0
  • High CVE-2024-28757 fixed in 2.6.2-r0
  • Medium CVE-2023-52426 fixed in 2.6.0-r0
High 4 known vulnerabilities in libxml2@2.9.8-r0 (rija/docker-alpine-shell-tools:1.0.1) Security · 4 CVEs

How to fix

Update libxml2 from 2.9.8-r0 to 2.9.8-r2 or later in rija/docker-alpine-shell-tools:1.0.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.9.8-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-2019-19956 fixed in 2.9.8-r2
  • Medium CVE-2018-9251 fixed in 2.9.8-r1
  • Medium CVE-2018-14404 fixed in 2.9.8-r1
  • Medium CVE-2018-14567 fixed in 2.9.8-r1
High 4 known vulnerabilities in gdk-pixbuf.mo@unknown (seleniarm/standalone-firefox:latest) Security · 4 CVEs

How to fix

No fixed version of gdk-pixbuf.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs gdk-pixbuf.mo 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-7345 fixed in no fix yet
  • High CVE-2026-5201 fixed in no fix yet
  • High CVE-2022-48622 fixed in no fix yet
  • Low CVE-2025-6199 fixed in no fix yet
High 3 known vulnerabilities in apr@1.7.0-r2 (composer/composer:2.4.3) Security · 3 CVEs

How to fix

Update apr from 1.7.0-r2 to 1.7.1-r0 or later in composer/composer:2.4.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.7.1-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-2022-24963 fixed in 1.7.1-r0
  • High CVE-2022-28331 fixed in 1.7.1-r0
  • Medium CVE-2022-25147 fixed in 1.7.1-r0
High 3 known vulnerabilities in net@0.47.0 (gitlab/gitlab-runner:latest) Security · 3 CVEs

How to fix

Update net from 0.47.0 to 0.53.0 or later in gitlab/gitlab-runner: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.53.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-33814 fixed in 0.53.0
  • Medium CVE-2026-25680 fixed in 0.55.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 3 known vulnerabilities in Linux-PAM.mo@unknown (seleniarm/standalone-firefox:latest) Security · 3 CVEs

How to fix

No fixed version of Linux-PAM.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs Linux-PAM.mo 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-6020 fixed in no fix yet
  • Medium CVE-2024-22365 fixed in no fix yet
  • Medium CVE-2026-54411 fixed in no fix yet
High 3 known vulnerabilities in ffmpeg@7%3A5.1.4-0%2Bdeb12u1 (seleniarm/standalone-firefox:latest) Security · 3 CVEs

How to fix

Update ffmpeg from 7%3A5.1.4-0%2Bdeb12u1 to 7:5.1.5-0+deb12u1 or later in seleniarm/standalone-firefox: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.1.5-0+deb12u1); 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-32230 fixed in 7:5.1.5-0+deb12u1
  • High CVE-2024-35367 fixed in 7:5.1.7-0+deb12u1
  • High CVE-2024-35368 fixed in 7:5.1.7-0+deb12u1
High 2 known vulnerabilities in sqlite@3.51.2-r0 (certbot/certbot) Security · 2 CVEs

How to fix

No fixed version of sqlite is available yet. Check whether certbot/certbot needs sqlite 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-11822 fixed in no fix yet
  • High CVE-2026-11824 fixed in no fix yet
High 2 known vulnerabilities in nghttp2@1.47.0-r0 (composer/composer:2.4.3) Security · 2 CVEs

How to fix

Update nghttp2 from 1.47.0-r0 to 1.47.0-r1 or later in composer/composer:2.4.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.47.0-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-2023-35945 fixed in 1.47.0-r1
  • High CVE-2023-44487 fixed in 1.47.0-r2
High 2 known vulnerabilities in nghttp2@1.32.0-r0 (rija/docker-alpine-shell-tools:1.0.1) Security · 2 CVEs

How to fix

Update nghttp2 from 1.32.0-r0 to 1.39.2-r0 or later in rija/docker-alpine-shell-tools:1.0.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.39.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

  • High CVE-2019-9511 fixed in 1.39.2-r0
  • High CVE-2019-9513 fixed in 1.39.2-r0
High 2 known vulnerabilities in ghostscript@10.0.0~dfsg-11%2Bdeb12u3 (seleniarm/standalone-firefox:latest) Security · 2 CVEs

How to fix

Update ghostscript from 10.0.0~dfsg-11%2Bdeb12u3 to 10.0.0~dfsg-11+deb12u7 or later in seleniarm/standalone-firefox: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 10.0.0~dfsg-11+deb12u7); 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-27835 fixed in 10.0.0~dfsg-11+deb12u7
  • High CVE-2025-27836 fixed in 10.0.0~dfsg-11+deb12u7
High 2 known vulnerabilities in gnupg2.mo@unknown (seleniarm/standalone-firefox:latest) Security · 2 CVEs

How to fix

No fixed version of gnupg2.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs gnupg2.mo 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-68973 fixed in no fix yet
  • Low CVE-2022-3219 fixed in no fix yet
High 1 known vulnerability in musl@1.2.3-r0 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update musl from 1.2.3-r0 to 1.2.3-r4 or later in composer/composer:2.4.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.3-r4); 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.3-r4
High 1 known vulnerability in ncurses@6.3_p20220521-r0 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update ncurses from 6.3_p20220521-r0 to 6.3_p20220521-r1 or later in composer/composer:2.4.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 6.3_p20220521-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-2023-29491 fixed in 6.3_p20220521-r1
High 1 known vulnerability in pcre2@10.40-r0 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update pcre2 from 10.40-r0 to 10.42-r0 or later in composer/composer:2.4.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 10.42-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-2022-41409 fixed in 10.42-r0
High 1 known vulnerability in musl@1.1.19-r10 (rija/docker-alpine-shell-tools:1.0.1) Security · 1 CVE

How to fix

Update musl from 1.1.19-r10 to 1.1.19-r11 or later in rija/docker-alpine-shell-tools:1.0.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.1.19-r11); 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-2019-14697 fixed in 1.1.19-r11
High 1 known vulnerability in krb5@1.20.1-2%2Bdeb12u1 (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

Update krb5 from 1.20.1-2%2Bdeb12u1 to 1.20.1-2+deb12u2 or later in seleniarm/standalone-firefox: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.1-2+deb12u2); 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-37371 fixed in 1.20.1-2+deb12u2
High 1 known vulnerability in cyrus-sasl2@2.1.27~101-g0780600%2Bdfsg-3ubuntu2 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update cyrus-sasl2 from 2.1.27~101-g0780600%2Bdfsg-3ubuntu2 to 2.1.27~101-g0780600+dfsg-3ubuntu2.4 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.1.27~101-g0780600+dfsg-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

  • High CVE-2022-24407 fixed in 2.1.27~101-g0780600+dfsg-3ubuntu2.4
High Unencrypted EBS Volume Cost · 1 place

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

How to fix

Enable encryption for EBS volumes.

Where

Medium 154

Medium Ensure that HTTPS url is used with uri Security · 25 places
Medium 18 known vulnerabilities in aa_ER@saaho (selenium/standalone-chrome:3.141.59-oxygen) Security · 18 CVEs

How to fix

No fixed version of aa_ER is available yet. Check whether selenium/standalone-chrome:3.141.59-oxygen needs aa_ER 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-1751 fixed in no fix yet
  • Medium CVE-2018-19591 fixed in no fix yet
  • Medium CVE-2018-11237 fixed in no fix yet
  • Medium CVE-2021-3999 fixed in no fix yet
  • Medium CVE-2018-11236 fixed in no fix yet
  • Low CVE-2019-19126 fixed in no fix yet
  • Low CVE-2020-29562 fixed in no fix yet
  • Low CVE-2020-10029 fixed in no fix yet
  • Low CVE-2020-27618 fixed in no fix yet
  • Low CVE-2016-10228 fixed in no fix yet
  • Low CVE-2019-25013 fixed in no fix yet
  • Low CVE-2020-1752 fixed in no fix yet
  • Low CVE-2021-3326 fixed in no fix yet
  • Low CVE-2020-6096 fixed in no fix yet
  • Low CVE-2021-35942 fixed in no fix yet
  • Low CVE-2019-9169 fixed in no fix yet
  • Low CVE-2022-23218 fixed in no fix yet
  • Low CVE-2022-23219 fixed in no fix yet
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 15 places
Medium Ensure that a user for the container has been created Security · 14 places
Medium 5 known vulnerabilities in avahi.mo@unknown (seleniarm/standalone-firefox:latest) Security · 5 CVEs

How to fix

No fixed version of avahi.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs avahi.mo 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-2023-38469 fixed in no fix yet
  • Medium CVE-2023-38470 fixed in no fix yet
  • Medium CVE-2023-38471 fixed in no fix yet
  • Medium CVE-2023-38472 fixed in no fix yet
  • Medium CVE-2023-38473 fixed in no fix yet
Medium 5 known vulnerabilities in libxml2@2.9.4%2Bdfsg1-6.1ubuntu1.2 (selenium/standalone-chrome:3.141.59-oxygen) Security · 5 CVEs

How to fix

Update libxml2 from 2.9.4%2Bdfsg1-6.1ubuntu1.2 to 2.9.4+dfsg1-6.1ubuntu1.7 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.9.4+dfsg1-6.1ubuntu1.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-2016-3709 fixed in 2.9.4+dfsg1-6.1ubuntu1.7
  • Medium CVE-2022-23308 fixed in 2.9.4+dfsg1-6.1ubuntu1.5
  • Low CVE-2019-19956 fixed in 2.9.4+dfsg1-6.1ubuntu1.3
  • Low CVE-2019-20388 fixed in 2.9.4+dfsg1-6.1ubuntu1.4
  • Low CVE-2020-7595 fixed in 2.9.4+dfsg1-6.1ubuntu1.3
Medium Ensure Terraform module sources use a commit hash Security · 5 places
Medium Ensure block is handling task errors properly Security · 4 places
Medium 3 known vulnerabilities in gnutls28@3.8.3-1.1ubuntu3.5 (gitlab/gitlab-runner:latest) Security · 3 CVEs

How to fix

Update gnutls28 from 3.8.3-1.1ubuntu3.5 to 3.8.3-1.1ubuntu3.6 or later in gitlab/gitlab-runner: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.8.3-1.1ubuntu3.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

  • Medium CVE-2026-42014 fixed in 3.8.3-1.1ubuntu3.6
  • Medium CVE-2026-5260 fixed in 3.8.3-1.1ubuntu3.6
  • Medium CVE-2026-5419 fixed in 3.8.3-1.1ubuntu3.6
Medium 3 known vulnerabilities in libjpeg-turbo@1.5.2-0ubuntu5.18.04.1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 3 CVEs

How to fix

Update libjpeg-turbo from 1.5.2-0ubuntu5.18.04.1 to 1.5.2-0ubuntu5.18.04.6 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.5.2-0ubuntu5.18.04.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

  • Medium CVE-2020-35538 fixed in 1.5.2-0ubuntu5.18.04.6
  • Medium CVE-2020-13790 fixed in 1.5.2-0ubuntu5.18.04.4
  • Low CVE-2018-11813 fixed in 1.5.2-0ubuntu5.18.04.6
Medium 3 known vulnerabilities in openldap@2.4.45%2Bdfsg-1ubuntu1.2 (selenium/standalone-chrome:3.141.59-oxygen) Security · 3 CVEs

How to fix

Update openldap from 2.4.45%2Bdfsg-1ubuntu1.2 to 2.4.45+dfsg-1ubuntu1.5 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.45+dfsg-1ubuntu1.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-2020-12243 fixed in 2.4.45+dfsg-1ubuntu1.5
  • Medium CVE-2020-36222 fixed in 2.4.45+dfsg-1ubuntu1.9
  • Medium CVE-2020-36225 fixed in 2.4.45+dfsg-1ubuntu1.9
Medium 3 known vulnerabilities in python2.7@2.7.15~rc1-1ubuntu0.1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 3 CVEs

How to fix

Update python2.7 from 2.7.15~rc1-1ubuntu0.1 to 2.7.17-1~18.04ubuntu1.1 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.17-1~18.04ubuntu1.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-2019-20907 fixed in 2.7.17-1~18.04ubuntu1.1
  • Medium CVE-2023-24329 fixed in 2.7.17-1~18.04ubuntu1.13
  • Low CVE-2019-9674 fixed in 2.7.17-1~18.04ubuntu1.1
Medium Base64 High Entropy String Security · 3 places
Medium 2 known vulnerabilities in glibc@2.39-0ubuntu8.7 (gitlab/gitlab-runner:latest) Security · 2 CVEs

How to fix

No fixed version of glibc is available yet. Check whether gitlab/gitlab-runner:latest 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

  • Medium CVE-2026-4438 fixed in no fix yet
  • Medium CVE-2026-5435 fixed in no fix yet
Medium 2 known vulnerabilities in libgcrypt20@1.10.3-2build1 (gitlab/gitlab-runner:latest) Security · 2 CVEs

How to fix

Update libgcrypt20 from 1.10.3-2build1 to 1.10.3-2ubuntu0.1 or later in gitlab/gitlab-runner:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.10.3-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-2026-41989 fixed in 1.10.3-2ubuntu0.1
  • Low CVE-2024-2236 fixed in no fix yet
Medium 2 known vulnerabilities in curl@7.58.0-2ubuntu3.7 (selenium/standalone-chrome:3.141.59-oxygen) Security · 2 CVEs

How to fix

Update curl from 7.58.0-2ubuntu3.7 to 7.58.0-2ubuntu3.8 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.58.0-2ubuntu3.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-2019-5481 fixed in 7.58.0-2ubuntu3.8
  • Medium CVE-2019-5482 fixed in 7.58.0-2ubuntu3.8
Medium 2 known vulnerabilities in perl@5.26.1-6ubuntu0.3 (selenium/standalone-chrome:3.141.59-oxygen) Security · 2 CVEs

How to fix

Update perl from 5.26.1-6ubuntu0.3 to 5.26.1-6ubuntu0.6 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.26.1-6ubuntu0.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

  • Medium CVE-2020-16156 fixed in 5.26.1-6ubuntu0.6
  • Medium CVE-2023-31484 fixed in 5.26.1-6ubuntu0.7
Medium 2 known vulnerabilities in sudo@1.8.21p2-3ubuntu1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 2 CVEs

How to fix

Update sudo from 1.8.21p2-3ubuntu1 to 1.8.21p2-3ubuntu1.6 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.8.21p2-3ubuntu1.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

  • Medium CVE-2023-28486 fixed in 1.8.21p2-3ubuntu1.6
  • Medium CVE-2023-28487 fixed in 1.8.21p2-3ubuntu1.6
Medium Ensure that packages with untrusted or missing GPG signatures are not used by dnf Security · 2 places

Ensure that packages with untrusted or missing GPG signatures are not used by dnf

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 2 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 2 places
Medium Ensure that EC2 is EBS optimized Security · 2 places
Medium Ensure every security group and rule has a description Security · 2 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 2 places
Medium Ensure Instance Metadata Service Version 1 is not 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 busybox@1.37.0-r30 (certbot/certbot) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether certbot/certbot 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 apr-util@1.6.1-r12 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update apr-util from 1.6.1-r12 to 1.6.3-r0 or later in composer/composer:2.4.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.6.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

  • Medium CVE-2022-25147 fixed in 1.6.3-r0
Medium 1 known vulnerability in busybox@1.35.0-r17 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update busybox from 1.35.0-r17 to 1.35.0-r18 or later in composer/composer:2.4.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.35.0-r18); 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-2023-42366 fixed in 1.35.0-r18
Medium 1 known vulnerability in sqlite@3.38.5-r0 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update sqlite from 3.38.5-r0 to 3.40.1-r1 or later in composer/composer:2.4.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.40.1-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-2023-7104 fixed in 3.40.1-r1
Medium 1 known vulnerability in tar@1.34-r0 (composer/composer:2.4.3) Security · 1 CVE

How to fix

Update tar from 1.34-r0 to 1.34-r1 or later in composer/composer:2.4.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.34-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-2022-48303 fixed in 1.34-r1
Medium 1 known vulnerability in xz@5.2.5-r1 (composer/composer:2.4.3) Security · 1 CVE

How to fix

No fixed version of xz is available yet. Check whether composer/composer:2.4.3 needs xz 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-22916 fixed in no fix yet
Medium 1 known vulnerability in dpkg@1.22.6ubuntu6.5 (gitlab/gitlab-runner:latest) Security · 1 CVE

How to fix

No fixed version of dpkg is available yet. Check whether gitlab/gitlab-runner:latest needs dpkg 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-2219 fixed in no fix yet
Medium 1 known vulnerability in systemd@255.4-1ubuntu8.15 (gitlab/gitlab-runner:latest) Security · 1 CVE

How to fix

Update systemd from 255.4-1ubuntu8.15 to 255.4-1ubuntu8.16 or later in gitlab/gitlab-runner: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 255.4-1ubuntu8.16); 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-40226 fixed in 255.4-1ubuntu8.16
Medium 1 known vulnerability in db5.3@5.3.28-13.1ubuntu1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update db5.3 from 5.3.28-13.1ubuntu1 to 5.3.28-13.1ubuntu1.1 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.3.28-13.1ubuntu1.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-2019-8457 fixed in 5.3.28-13.1ubuntu1.1
Medium 1 known vulnerability in freetype@2.8.1-2ubuntu2 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update freetype from 2.8.1-2ubuntu2 to 2.8.1-2ubuntu2.2 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.8.1-2ubuntu2.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

  • Medium CVE-2022-31782 fixed in 2.8.1-2ubuntu2.2
Medium 1 known vulnerability in openjdk-8@8u212-b03-0ubuntu1.18.04.1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update openjdk-8 from 8u212-b03-0ubuntu1.18.04.1 to 8u222-b10-1ubuntu1~18.04.1 or later in selenium/standalone-chrome:3.141.59-oxygen. 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 8u222-b10-1ubuntu1~18.04.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-2019-7317 fixed in 8u222-b10-1ubuntu1~18.04.1
Medium 1 known vulnerability in sqlite3@3.22.0-1 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update sqlite3 from 3.22.0-1 to 3.22.0-1ubuntu0.4 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.22.0-1ubuntu0.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-2020-13434 fixed in 3.22.0-1ubuntu0.4
Medium 1 known vulnerability in zlib@1%3A1.2.11.dfsg-0ubuntu2 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update zlib from 1%3A1.2.11.dfsg-0ubuntu2 to 1:1.2.11.dfsg-0ubuntu2.1 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.2.11.dfsg-0ubuntu2.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-2018-25032 fixed in 1:1.2.11.dfsg-0ubuntu2.1
Medium Ensure that sudo isn't used Security · 1 place

Ensure that sudo isn't used

Documentation

Where

and 8 more groups with 8 findings

Low 26

Low 7 known vulnerabilities in elfutils.mo@unknown (seleniarm/standalone-firefox:latest) Security · 7 CVEs

How to fix

No fixed version of elfutils.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs elfutils.mo 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-2024-25260 fixed in no fix yet
  • Low CVE-2025-1352 fixed in no fix yet
  • Low CVE-2025-1365 fixed in no fix yet
  • Low CVE-2025-1371 fixed in no fix yet
  • Low CVE-2025-1372 fixed in no fix yet
  • Low CVE-2025-1376 fixed in no fix yet
  • Low CVE-2025-1377 fixed in no fix yet
Low 4 known vulnerabilities in systemd.be@latin.catalog (seleniarm/standalone-firefox:latest) Security · 4 CVEs

How to fix

No fixed version of systemd.be is available yet. Check whether seleniarm/standalone-firefox:latest needs systemd.be 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 2 known vulnerabilities in giflib@5.2.1-2.5 (seleniarm/standalone-firefox:latest) Security · 2 CVEs

How to fix

No fixed version of giflib is available yet. Check whether seleniarm/standalone-firefox: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

  • Low CVE-2022-28506 fixed in no fix yet
  • Low CVE-2023-39742 fixed in no fix yet
Low 2 known vulnerabilities in sudo@1.9.13p3-1%2Bdeb12u1 (seleniarm/standalone-firefox:latest) Security · 2 CVEs

How to fix

No fixed version of sudo is available yet. Check whether seleniarm/standalone-firefox:latest needs sudo 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-2005-1119 fixed in no fix yet
  • Low CVE-2025-32462 fixed in 1.9.13p3-1+deb12u2
Low 2 known vulnerabilities in tiff@4.5.0-6%2Bdeb12u1 (seleniarm/standalone-firefox:latest) Security · 2 CVEs

How to fix

No fixed version of tiff is available yet. Check whether seleniarm/standalone-firefox:latest needs tiff 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-10126 fixed in no fix yet
  • Low CVE-2024-6716 fixed in no fix yet
Low 1 known vulnerability in xz@5.8.2-r0 (certbot/certbot) Security · 1 CVE

How to fix

Update xz from 5.8.2-r0 to 5.8.3-r0 or later in certbot/certbot. 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 1 known vulnerability in gcc-12@12.2.0-14 (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether seleniarm/standalone-firefox:latest needs gcc-12 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-27943 fixed in no fix yet
Low 1 known vulnerability in glib20.mo@unknown (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of glib20.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs glib20.mo 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-2012-0039 fixed in no fix yet
Low 1 known vulnerability in perl@5.36.0-7%2Bdeb12u1 (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether seleniarm/standalone-firefox:latest 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 pixman@0.42.2-1 (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of pixman is available yet. Check whether seleniarm/standalone-firefox:latest needs pixman 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-37769 fixed in no fix yet
Low 1 known vulnerability in x264@2%3A0.164.3108%2Bgit31e19f9-1 (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of x264 is available yet. Check whether seleniarm/standalone-firefox:latest needs x264 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-25467 fixed in no fix yet
Low 1 known vulnerability in xdg-user-dirs.mo@unknown (seleniarm/standalone-firefox:latest) Security · 1 CVE

How to fix

No fixed version of xdg-user-dirs.mo is available yet. Check whether seleniarm/standalone-firefox:latest needs xdg-user-dirs.mo 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-15131 fixed in no fix yet
Low 1 known vulnerability in ncurses@6.1-1ubuntu1.18.04 (selenium/standalone-chrome:3.141.59-oxygen) Security · 1 CVE

How to fix

Update ncurses from 6.1-1ubuntu1.18.04 to 6.1-1ubuntu1.18.04.1 or later in selenium/standalone-chrome:3.141.59-oxygen. 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.1-1ubuntu1.18.04.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-2021-39537 fixed in 6.1-1ubuntu1.18.04.1
Low 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

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.