Repository scan
OasisPlatform
OasisLMF/OasisPlatform · branch main · scanned 1 Jun 2026
High 953
High 582 known vulnerabilities in stdlib@1.13 (portainer/portainer:latest)
How to fix
Update stdlib from 1.13 to 1.15.13 or later in portainer/portainer: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.15.13); 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-2021-33195 fixed in 1.15.13
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2019-16276 fixed in 1.13.1
- High CVE-2019-17596 fixed in 1.13.2
- High CVE-2020-16845 fixed in 1.13.15
- High CVE-2020-7919 fixed in 1.13.7
- High CVE-2021-27918 fixed in 1.15.9
- High CVE-2021-33196 fixed in 1.15.13
- High CVE-2021-33198 fixed in 1.15.13
- and 562 more
High 71 known vulnerabilities in docker@20.10.3-0.20220309172631-83b51522df43%2Bincompatible (portainer/portainer:latest)
How to fix
No fixed version of docker is available yet. Check whether portainer/portainer:latest needs docker 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-41567 fixed in no fix yet
- High CVE-2026-41567 fixed in no fix yet
- High CVE-2026-41567 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-42306 fixed in no fix yet
- High CVE-2026-42306 fixed in no fix yet
- High CVE-2026-42306 fixed in no fix yet
- High CVE-2019-13509 fixed in 18.09.8
- High CVE-2023-28840 fixed in 20.10.24
- High CVE-2023-28840 fixed in 20.10.24
- High CVE-2023-28840 fixed in 20.10.24
- High CVE-2023-28840 fixed in 20.10.24
- High CVE-2026-34040 fixed in 29.3.1
- High CVE-2026-34040 fixed in 29.3.1
- High CVE-2026-34040 fixed in 29.3.1
- High CVE-2026-34040 fixed in 29.3.1
- High CVE-2024-41110 fixed in 23.0.15
- High CVE-2024-41110 fixed in 23.0.15
- High CVE-2024-41110 fixed in 23.0.15
- and 51 more
High 61 known vulnerabilities in crypto@0.0.0-20220214200702-86341886e292 (portainer/portainer:latest)
How to fix
Update crypto from 0.0.0-20220214200702-86341886e292 to 0.0.0-20220314234659-1baeb1ce4c0b or later in portainer/portainer: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.0.0-20220314234659-1baeb1ce4c0b); 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-27191 fixed in 0.0.0-20220314234659-1baeb1ce4c0b
- High CVE-2022-27191 fixed in 0.0.0-20220314234659-1baeb1ce4c0b
- High CVE-2022-30636 fixed in 0.0.0-20220525230936-793ad666bf5e
- High CVE-2022-30636 fixed in 0.0.0-20220525230936-793ad666bf5e
- High CVE-2025-22869 fixed in 0.35.0
- High CVE-2025-22869 fixed in 0.35.0
- High CVE-2025-22869 fixed in 0.35.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2026-39829 fixed in 0.52.0
- High CVE-2026-39829 fixed in 0.52.0
- High CVE-2026-39829 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2024-45337 fixed in 0.31.0
- High CVE-2024-45337 fixed in 0.31.0
- High CVE-2024-45337 fixed in 0.31.0
- High CVE-2026-39830 fixed in 0.52.0
- and 41 more
High 60 known vulnerabilities in net@0.0.0-20200324143707-d3edc9973b7e (portainer/portainer:latest)
How to fix
Update net from 0.0.0-20200324143707-d3edc9973b7e to 0.0.0-20210520170846-37e1c6afe023 or later in portainer/portainer: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.0.0-20210520170846-37e1c6afe023); 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-2021-33194 fixed in 0.0.0-20210520170846-37e1c6afe023
- High CVE-2021-44716 fixed in 0.0.0-20211209124913-491a49abca63
- High CVE-2022-27664 fixed in 0.0.0-20220906165146-f3363e06e74c
- High CVE-2022-27664 fixed in 0.0.0-20220906165146-f3363e06e74c
- High CVE-2022-27664 fixed in 0.0.0-20220906165146-f3363e06e74c
- High CVE-2022-41723 fixed in 0.7.0
- High CVE-2022-41723 fixed in 0.7.0
- High CVE-2022-41723 fixed in 0.7.0
- High CVE-2023-39325 fixed in 0.17.0
- High CVE-2023-39325 fixed in 0.17.0
- High CVE-2023-39325 fixed in 0.17.0
- High CVE-2026-33814 fixed in 0.53.0
- High CVE-2026-33814 fixed in 0.53.0
- High CVE-2026-33814 fixed in 0.53.0
- High CVE-2026-39821 fixed in 0.55.0
- High CVE-2026-39821 fixed in 0.55.0
- High CVE-2026-39821 fixed in 0.55.0
- Medium CVE-2025-22870 fixed in 0.36.0
- Medium CVE-2025-22870 fixed in 0.36.0
- Medium CVE-2025-22870 fixed in 0.36.0
- and 40 more
High 33 known vulnerabilities in stdlib@1.24.6 (postgres)
How to fix
Update stdlib from 1.24.6 to 1.24.9 or later in postgres. 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-2026-25679 fixed in 1.25.8
- High CVE-2026-32280 fixed in 1.25.9
- High CVE-2026-32281 fixed in 1.25.9
- High CVE-2026-32283 fixed in 1.25.9
- High CVE-2026-33811 fixed in 1.25.10
- High CVE-2026-33814 fixed in 1.25.10
- High CVE-2026-39820 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-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
- and 13 more
High 22 known vulnerabilities in containerd@1.6.8 (portainer/portainer:latest)
How to fix
Update containerd from 1.6.8 to 1.6.18 or later in portainer/portainer: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.18); 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-2989 fixed in 1.6.18
- High CVE-2022-2989 fixed in 1.6.18
- High CVE-2022-2990 fixed in 1.6.18
- High CVE-2022-2990 fixed in 1.6.18
- High CVE-2022-2995 fixed in 1.6.18
- High CVE-2022-2995 fixed in 1.6.18
- High CVE-2024-25621 fixed in 1.7.29
- High CVE-2024-25621 fixed in 1.7.29
- Medium GHSA-7ww5-4wqc-m92c fixed in 1.6.26
- Medium GHSA-7ww5-4wqc-m92c fixed in 1.6.26
- Medium CVE-2024-40635 fixed in 1.6.38
- Medium CVE-2024-40635 fixed in 1.6.38
- Medium CVE-2022-36109 fixed in 1.6.18
- Medium CVE-2022-36109 fixed in 1.6.18
- Medium CVE-2023-25173 fixed in 1.6.18
- Medium CVE-2023-25173 fixed in 1.6.18
- Medium CVE-2023-25153 fixed in 1.6.18
- Medium CVE-2023-25153 fixed in 1.6.18
- Medium CVE-2022-23471 fixed in 1.6.12
- Medium CVE-2022-23471 fixed in 1.6.12
- and 2 more
High 20 known vulnerabilities in runc@1.1.2 (portainer/portainer:latest)
How to fix
Update runc from 1.1.2 to 1.1.5 or later in portainer/portainer: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.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-2023-27561 fixed in 1.1.5
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-31133 fixed in 1.2.8
- High CVE-2025-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2019-16884 fixed in 1.0.0-rc8.0.20190930145003-cad42f6e0932
- High CVE-2021-30465 fixed in 1.0.0-rc95
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2024-45310 fixed in 1.1.14
- Medium CVE-2019-19921 fixed in 1.0.0-rc9.0.20200122160610-2fc03cc11c77
- Medium CVE-2022-29162 fixed in 1.1.2
- Medium CVE-2021-43784 fixed in 1.0.3
- Medium CVE-2023-28642 fixed in 1.1.5
- Medium CVE-2023-28642 fixed in 1.1.5
- Medium CVE-2016-9962 fixed in 1.0.0-rc3
- Low GHSA-g54h-m393-cpwq fixed in 1.0.0-rc91
- Low CVE-2023-25809 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 17 known vulnerabilities in expat@2.2.5-3ubuntu0.2 (rabbitmq:3.8.14-management)
How to fix
Update expat from 2.2.5-3ubuntu0.2 to 2.2.5-3ubuntu0.4 or later in rabbitmq:3.8.14-management. 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.5-3ubuntu0.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-25235 fixed in 2.2.5-3ubuntu0.4
- High CVE-2022-25236 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-25313 fixed in 2.2.5-3ubuntu0.7
- Medium CVE-2022-23990 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-25314 fixed in 2.2.5-3ubuntu0.7
- Medium CVE-2022-43680 fixed in 2.2.5-3ubuntu0.8
- Medium CVE-2021-46143 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-40674 fixed in 2.2.5-3ubuntu0.8
- Medium CVE-2022-22825 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-22826 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-22827 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-22822 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-22823 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-22824 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-23852 fixed in 2.2.5-3ubuntu0.4
- Medium CVE-2022-25315 fixed in 2.2.5-3ubuntu0.7
- Low CVE-2021-45960 fixed in 2.2.5-3ubuntu0.4
High 14 known vulnerabilities in v5@5.3.0 (portainer/portainer:latest)
How to fix
Update v5 from 5.3.0 to 5.19.0 or later in portainer/portainer: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.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
- High CVE-2026-45022 fixed in 5.19.0
- High CVE-2023-49568 fixed in 5.11.0
- High CVE-2025-21614 fixed in 5.13.0
- High CVE-2026-44973 fixed in 5.9.0
- High CVE-2025-21613 fixed in 5.13.0
- High CVE-2023-49569 fixed in 5.11.0
- Medium CVE-2026-25934 fixed in 5.16.5
- Medium CVE-2026-41506 fixed in 5.18.0
- Medium CVE-2026-34165 fixed in 5.17.1
- Medium CVE-2026-45571 fixed in 5.19.1
- Medium CVE-2026-44740 fixed in 5.9.0
- Medium GHSA-w5pp-99ch-qj29 fixed in 5.19.1
- Low CVE-2026-45570 fixed in 5.19.1
- Low CVE-2026-33762 fixed in 5.17.1
High 14 known vulnerabilities in openssl@1.1.1-1ubuntu2.1~18.04.9 (rabbitmq:3.8.14-management)
How to fix
Update openssl from 1.1.1-1ubuntu2.1~18.04.9 to 1.1.1-1ubuntu2.1~18.04.21 or later in rabbitmq:3.8.14-management. 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.1-1ubuntu2.1~18.04.21); 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-0286 fixed in 1.1.1-1ubuntu2.1~18.04.21
- High CVE-2022-0778 fixed in 1.1.1-1ubuntu2.1~18.04.15
- High CVE-2021-3711 fixed in 1.1.1-1ubuntu2.1~18.04.13
- Medium CVE-2022-2097 fixed in 1.1.1-1ubuntu2.1~18.04.20
- Medium CVE-2022-4304 fixed in 1.1.1-1ubuntu2.1~18.04.21
- Medium CVE-2023-2650 fixed in 1.1.1-1ubuntu2.1~18.04.23
- Medium CVE-2022-1292 fixed in 1.1.1-1ubuntu2.1~18.04.17
- Medium CVE-2022-2068 fixed in 1.1.1-1ubuntu2.1~18.04.19
- Medium CVE-2021-3712 fixed in 1.1.1-1ubuntu2.1~18.04.13
- Medium CVE-2022-4450 fixed in 1.1.1-1ubuntu2.1~18.04.21
- Medium CVE-2023-0215 fixed in 1.1.1-1ubuntu2.1~18.04.21
- Low CVE-2023-0465 fixed in 1.1.1-1ubuntu2.1~18.04.22
- Low CVE-2023-0466 fixed in 1.1.1-1ubuntu2.1~18.04.22
- Low CVE-2023-0464 fixed in 1.1.1-1ubuntu2.1~18.04.22
High 8 known vulnerabilities in perl@5.40.1-6 (postgres)
How to fix
No fixed version of perl is available yet. Check whether postgres 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
- High CVE-2026-48962 fixed in no fix yet
- High CVE-2026-42497 fixed in no fix yet
- High CVE-2026-48959 fixed in no fix yet
- High CVE-2026-9538 fixed in no fix yet
- High CVE-2026-42496 fixed in no fix yet
- Medium CVE-2025-15649 fixed in no fix yet
- Low CVE-2011-4116 fixed in no fix yet
- Low CVE-2026-48961 fixed in no fix yet
High 7 known vulnerabilities in buildkit@0.10.4 (portainer/portainer:latest)
How to fix
Update buildkit from 0.10.4 to 0.28.1 or later in portainer/portainer: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.28.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-33748 fixed in 0.28.1
- High CVE-2026-33747 fixed in 0.28.1
- High CVE-2024-23651 fixed in 0.12.5
- High CVE-2024-23653 fixed in 0.12.5
- High CVE-2024-23652 fixed in 0.12.5
- Medium CVE-2024-23650 fixed in 0.12.5
- Medium CVE-2023-26054 fixed in 0.11.4
High 6 known vulnerabilities in grpc@1.43.0 (portainer/portainer:latest)
How to fix
Update grpc from 1.43.0 to 1.56.3 or later in portainer/portainer: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.56.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-2023-44487 fixed in 1.56.3
- High CVE-2023-44487 fixed in 1.56.3
- High GHSA-m425-mq94-257g fixed in 1.56.3
- High GHSA-m425-mq94-257g fixed in 1.56.3
- High CVE-2026-33186 fixed in 1.79.3
- High CVE-2026-33186 fixed in 1.79.3
High 5 known vulnerabilities in cli@20.10.17%2Bincompatible (portainer/portainer:latest)
How to fix
Update cli from 20.10.17%2Bincompatible to 29.2.0 or later in portainer/portainer: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 29.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-2025-15558 fixed in 29.2.0
- High CVE-2025-15558 fixed in 29.2.0
- High CVE-2025-15558 fixed in 29.2.0
- Medium CVE-2021-41092 fixed in 20.10.9
- Medium CVE-2021-41092 fixed in 0.0.0-20210923182634-c2ea9bc90bac
High 4 known vulnerabilities in systemd@237-3ubuntu10.46 (rabbitmq:3.8.14-management)
How to fix
Update systemd from 237-3ubuntu10.46 to 237-3ubuntu10.49 or later in rabbitmq:3.8.14-management. 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 237-3ubuntu10.49); 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-2021-33910 fixed in 237-3ubuntu10.49
- Medium CVE-2022-3821 fixed in 237-3ubuntu10.57
- Medium CVE-2022-2526 fixed in 237-3ubuntu10.56
- Low CVE-2020-13529 fixed in 237-3ubuntu10.49
High 3 known vulnerabilities in logrus@1.9.0 (portainer/portainer:latest)
How to fix
Update logrus from 1.9.0 to 1.9.1 or later in portainer/portainer: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.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-65637 fixed in 1.9.1
- High CVE-2025-65637 fixed in 1.8.3
- High CVE-2025-65637 fixed in 1.8.3
High 3 known vulnerabilities in otelhttp@0.29.0 (portainer/portainer:latest)
How to fix
Update otelhttp from 0.29.0 to 0.44.0 or later in portainer/portainer: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.44.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-21698 fixed in 0.44.0
- High CVE-2023-25151 fixed in 0.44.0
- High CVE-2023-45142 fixed in 0.44.0
High 3 known vulnerabilities in otelhttptrace@0.29.0 (portainer/portainer:latest)
How to fix
Update otelhttptrace from 0.29.0 to 0.44.0 or later in portainer/portainer: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.44.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-21698 fixed in 0.44.0
- High CVE-2023-25151 fixed in 0.44.0
- High CVE-2023-45142 fixed in 0.44.0
High 3 known vulnerabilities in text@0.3.3 (portainer/portainer:latest)
How to fix
Update text from 0.3.3 to 0.3.7 or later in portainer/portainer: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.3.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-2021-38561 fixed in 0.3.7
- High CVE-2022-32149 fixed in 0.3.8
- High CVE-2022-32149 fixed in 0.3.8
High 3 known vulnerabilities in v3@3.0.0-20220729163034-26163d82560f (portainer/portainer:latest)
How to fix
Update v3 from 3.0.0-20220729163034-26163d82560f to 3.1.0 or later in portainer/portainer: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.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-2026-33540 fixed in 3.1.0
- High CVE-2026-35172 fixed in 3.1.0
- Medium CVE-2026-41888 fixed in 3.1.1
High 2 known vulnerabilities in distribution@2.8.0%2Bincompatible (portainer/portainer:latest)
How to fix
Update distribution from 2.8.0%2Bincompatible to 2.8.2-beta.1 or later in portainer/portainer: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 2.8.2-beta.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-2023-2253 fixed in 2.8.2-beta.1
- High CVE-2023-2253 fixed in 2.8.2-beta.1
High 2 known vulnerabilities in oauth2@0.0.0-20211104180415-d3ed0bb246c8 (portainer/portainer:latest)
How to fix
Update oauth2 from 0.0.0-20211104180415-d3ed0bb246c8 to 0.27.0 or later in portainer/portainer: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.27.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-22868 fixed in 0.27.0
- High CVE-2025-22868 fixed in 0.27.0
High 2 known vulnerabilities in protobuf@1.3.1 (portainer/portainer:latest)
How to fix
Update protobuf from 1.3.1 to 1.3.2 or later in portainer/portainer: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.3.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-2021-3121 fixed in 1.3.2
- Medium CVE-2024-24786 fixed in 1.33.0
High 2 known vulnerabilities in v4@4.2.0 (portainer/portainer:latest)
How to fix
Update v4 from 4.2.0 to 4.5.2 or later in portainer/portainer: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.5.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-30204 fixed in 4.5.2
- Low CVE-2024-51744 fixed in 4.5.1
High 2 known vulnerabilities in yaml.v3@3.0.0-20200615113413-eeeca48fe776 (portainer/portainer:latest)
How to fix
Update yaml.v3 from 3.0.0-20200615113413-eeeca48fe776 to 3.0.0-20220521103104-8f96da9f5d5e or later in portainer/portainer: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.0-20220521103104-8f96da9f5d5e); 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-28948 fixed in 3.0.0-20220521103104-8f96da9f5d5e
- High CVE-2022-28948 fixed in 3.0.0-20220521103104-8f96da9f5d5e
High 1 known vulnerability in chisel@0.0.0-20190724232113-f3a8df20e389 (portainer/portainer:latest)
How to fix
Update chisel from 0.0.0-20190724232113-f3a8df20e389 to 0.0.0-20240805055020-59e5362e6bd6 or later in portainer/portainer: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.0.0-20240805055020-59e5362e6bd6); 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-43798 fixed in 0.0.0-20240805055020-59e5362e6bd6
High 1 known vulnerability in jwt@3.2.2%2Bincompatible (portainer/portainer:latest)
How to fix
No fixed version of jwt is available yet. Check whether portainer/portainer:latest needs jwt 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-30204 fixed in no fix yet
High 1 known vulnerability in otelgrpc@0.29.0 (portainer/portainer:latest)
How to fix
Update otelgrpc from 0.29.0 to 0.46.0 or later in portainer/portainer: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.46.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-2023-47108 fixed in 0.46.0
High 1 known vulnerability in spdystream@0.2.0 (portainer/portainer:latest)
How to fix
Update spdystream from 0.2.0 to 0.5.1 or later in portainer/portainer: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.5.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-35469 fixed in 0.5.1
Medium 68
Medium 10 known vulnerabilities in glibc@2.27-3ubuntu1.4 (rabbitmq:3.8.14-management)
How to fix
Update glibc from 2.27-3ubuntu1.4 to 2.27-3ubuntu1.5 or later in rabbitmq:3.8.14-management. 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.27-3ubuntu1.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-2021-3999 fixed in 2.27-3ubuntu1.5
- Low CVE-2020-29562 fixed in 2.27-3ubuntu1.5
- Low CVE-2020-27618 fixed in 2.27-3ubuntu1.5
- Low CVE-2016-10228 fixed in 2.27-3ubuntu1.5
- Low CVE-2019-25013 fixed in 2.27-3ubuntu1.5
- Low CVE-2021-3326 fixed in 2.27-3ubuntu1.5
- Low CVE-2020-6096 fixed in 2.27-3ubuntu1.5
- Low CVE-2021-35942 fixed in 2.27-3ubuntu1.5
- Low CVE-2022-23218 fixed in 2.27-3ubuntu1.5
- Low CVE-2022-23219 fixed in 2.27-3ubuntu1.5
Medium 9 known vulnerabilities in python3.6@3.6.9-1~18.04ubuntu1.4 (rabbitmq:3.8.14-management)
How to fix
Update python3.6 from 3.6.9-1~18.04ubuntu1.4 to 3.6.9-1~18.04ubuntu1.7 or later in rabbitmq:3.8.14-management. 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.9-1~18.04ubuntu1.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-2021-4189 fixed in 3.6.9-1~18.04ubuntu1.7
- Medium CVE-2021-3733 fixed in 3.6.9-1~18.04ubuntu1.6
- Medium CVE-2021-3737 fixed in 3.6.9-1~18.04ubuntu1.6
- Medium CVE-2022-0391 fixed in 3.6.9-1~18.04ubuntu1.7
- Medium CVE-2022-45061 fixed in 3.6.9-1~18.04ubuntu1.9
- Medium CVE-2023-24329 fixed in 3.6.9-1~18.04ubuntu1.13
- Medium CVE-2022-37454 fixed in 3.6.9-1~18.04ubuntu1.10
- Low CVE-2021-3426 fixed in 3.6.9-1~18.04ubuntu1.7
- Low CVE-2015-20107 fixed in 3.6.9-1~18.04ubuntu1.8
Medium 6 known vulnerabilities in sys@0.0.0-20211216021012-1d35b9e2eb4e (portainer/portainer:latest)
How to fix
Update sys from 0.0.0-20211216021012-1d35b9e2eb4e to 0.0.0-20220412211240-33da011f77ad or later in portainer/portainer: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.0.0-20220412211240-33da011f77ad); 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-29526 fixed in 0.0.0-20220412211240-33da011f77ad
- Medium CVE-2022-29526 fixed in 0.0.0-20220412211240-33da011f77ad
- Low CVE-2026-39824 fixed in 0.44.0
- Low CVE-2026-39824 fixed in 0.44.0
- Low CVE-2026-39824 fixed in 0.44.0
- Low CVE-2026-39824 fixed in 0.44.0
Medium 5 known vulnerabilities in krb5@1.21.3-5 (postgres)
How to fix
Update krb5 from 1.21.3-5 to 1.21.3-5+deb13u1 or later in postgres. 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.21.3-5+deb13u1); 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-40355 fixed in 1.21.3-5+deb13u1
- Medium CVE-2026-40356 fixed in 1.21.3-5+deb13u1
- 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
Medium 5 known vulnerabilities in ncurses@6.1-1ubuntu1.18.04 (rabbitmq:3.8.14-management)
How to fix
Update ncurses from 6.1-1ubuntu1.18.04 to 6.1-1ubuntu1.18.04.1 or later in rabbitmq:3.8.14-management. 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
- Medium CVE-2023-29491 fixed in 6.1-1ubuntu1.18.04.1
- Low CVE-2019-17594 fixed in 6.1-1ubuntu1.18.04.1
- Low CVE-2019-17595 fixed in 6.1-1ubuntu1.18.04.1
- Low CVE-2022-29458 fixed in 6.1-1ubuntu1.18.04.1
- Low CVE-2021-39537 fixed in 6.1-1ubuntu1.18.04.1
Medium 4 known vulnerabilities in libxml2@2.12.7%2Bdfsg%2Breally2.9.14-2.1%2Bdeb13u2 (postgres)
How to fix
No fixed version of libxml2 is available yet. Check whether postgres 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
- Medium CVE-2026-6732 fixed in no fix yet
- 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
Medium 3 known vulnerabilities in sqlite3@3.22.0-1ubuntu0.4 (rabbitmq:3.8.14-management)
How to fix
Update sqlite3 from 3.22.0-1ubuntu0.4 to 3.22.0-1ubuntu0.6 or later in rabbitmq:3.8.14-management. 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.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-35525 fixed in 3.22.0-1ubuntu0.6
- Medium CVE-2022-35737 fixed in 3.22.0-1ubuntu0.7
- Low CVE-2021-36690 fixed in 3.22.0-1ubuntu0.5
Medium 2 known vulnerabilities in helm@3.9.3 (portainer/portainer:latest)
How to fix
No fixed version of helm is available yet. Check whether portainer/portainer:latest needs helm 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-55198 fixed in no fix yet
- Medium CVE-2025-55199 fixed in no fix yet
Medium 2 known vulnerabilities in tar@1.35%2Bdfsg-3.1 (postgres)
How to fix
No fixed version of tar is available yet. Check whether postgres 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 2 known vulnerabilities in gnupg2@2.2.4-1ubuntu1.4 (rabbitmq:3.8.14-management)
How to fix
Update gnupg2 from 2.2.4-1ubuntu1.4 to 2.2.4-1ubuntu1.6 or later in rabbitmq:3.8.14-management. 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.4-1ubuntu1.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-2022-34903 fixed in 2.2.4-1ubuntu1.6
- Low CVE-2019-13050 fixed in 2.2.4-1ubuntu1.5
Medium 2 known vulnerabilities in gnutls28@3.5.18-1ubuntu1.4 (rabbitmq:3.8.14-management)
How to fix
Update gnutls28 from 3.5.18-1ubuntu1.4 to 3.5.18-1ubuntu1.6 or later in rabbitmq:3.8.14-management. 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.18-1ubuntu1.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-2022-2509 fixed in 3.5.18-1ubuntu1.6
- Low CVE-2021-4209 fixed in 3.5.18-1ubuntu1.6
Medium 2 known vulnerabilities in libgcrypt20@1.8.1-4ubuntu1.2 (rabbitmq:3.8.14-management)
How to fix
Update libgcrypt20 from 1.8.1-4ubuntu1.2 to 1.8.1-4ubuntu1.3 or later in rabbitmq:3.8.14-management. 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.1-4ubuntu1.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-2021-40528 fixed in 1.8.1-4ubuntu1.3
- Low CVE-2021-33560 fixed in 1.8.1-4ubuntu1.3
Medium 2 known vulnerabilities in nettle@3.4-1ubuntu0.1 (rabbitmq:3.8.14-management)
How to fix
Update nettle from 3.4-1ubuntu0.1 to 3.4.1-0ubuntu0.18.04.1 or later in rabbitmq:3.8.14-management. 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.4.1-0ubuntu0.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-2021-3580 fixed in 3.4.1-0ubuntu0.18.04.1
- Low CVE-2018-16869 fixed in 3.4.1-0ubuntu0.18.04.1
Medium 2 known vulnerabilities in perl@5.26.1-6ubuntu0.5 (rabbitmq:3.8.14-management)
How to fix
Update perl from 5.26.1-6ubuntu0.5 to 5.26.1-6ubuntu0.6 or later in rabbitmq:3.8.14-management. 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 tar@1.29b-2ubuntu0.2 (rabbitmq:3.8.14-management)
How to fix
Update tar from 1.29b-2ubuntu0.2 to 1.29b-2ubuntu0.4 or later in rabbitmq:3.8.14-management. 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.29b-2ubuntu0.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-2022-48303 fixed in 1.29b-2ubuntu0.4
- Low CVE-2021-20193 fixed in 1.29b-2ubuntu0.3
Medium 2 known vulnerabilities in zlib@1%3A1.2.11.dfsg-0ubuntu2 (rabbitmq:3.8.14-management)
How to fix
Update zlib from 1%3A1.2.11.dfsg-0ubuntu2 to 1:1.2.11.dfsg-0ubuntu2.1 or later in rabbitmq:3.8.14-management. 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 CVE-2022-37434 fixed in 1:1.2.11.dfsg-0ubuntu2.2
Medium 1 known vulnerability in buildx@0.8.2 (portainer/portainer:latest)
How to fix
Update buildx from 0.8.2 to 0.21.3 or later in portainer/portainer: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.21.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-0495 fixed in 0.21.3
Medium 1 known vulnerability in filepath-securejoin@0.2.3 (portainer/portainer:latest)
How to fix
Update filepath-securejoin from 0.2.3 to 0.2.4 or later in portainer/portainer: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
- Medium GHSA-6xv5-86q9-7xr8 fixed in 0.2.4
Medium 1 known vulnerability in bzip2@1.0.8-6 (postgres)
How to fix
No fixed version of bzip2 is available yet. Check whether postgres needs bzip2 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-42250 fixed in no fix yet
Medium 1 known vulnerability in dpkg@1.19.0.5ubuntu2.3 (rabbitmq:3.8.14-management)
How to fix
Update dpkg from 1.19.0.5ubuntu2.3 to 1.19.0.5ubuntu2.4 or later in rabbitmq:3.8.14-management. 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.19.0.5ubuntu2.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-2022-1664 fixed in 1.19.0.5ubuntu2.4
Medium 1 known vulnerability in e2fsprogs@1.44.1-1ubuntu1.3 (rabbitmq:3.8.14-management)
How to fix
Update e2fsprogs from 1.44.1-1ubuntu1.3 to 1.44.1-1ubuntu1.4 or later in rabbitmq:3.8.14-management. 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.44.1-1ubuntu1.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-2022-1304 fixed in 1.44.1-1ubuntu1.4
Medium 1 known vulnerability in gzip@1.6-5ubuntu1 (rabbitmq:3.8.14-management)
How to fix
Update gzip from 1.6-5ubuntu1 to 1.6-5ubuntu1.2 or later in rabbitmq:3.8.14-management. 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-5ubuntu1.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-1271 fixed in 1.6-5ubuntu1.2
Medium 1 known vulnerability in lz4@0.0~r131-2ubuntu3 (rabbitmq:3.8.14-management)
How to fix
Update lz4 from 0.0~r131-2ubuntu3 to 0.0~r131-2ubuntu3.1 or later in rabbitmq:3.8.14-management. 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.0~r131-2ubuntu3.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-2021-3520 fixed in 0.0~r131-2ubuntu3.1
Medium 1 known vulnerability in xz-utils@5.2.2-1.3 (rabbitmq:3.8.14-management)
How to fix
Update xz-utils from 5.2.2-1.3 to 5.2.2-1.3ubuntu0.1 or later in rabbitmq:3.8.14-management. 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-1.3ubuntu0.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-2022-1271 fixed in 5.2.2-1.3ubuntu0.1
Low 43
Low 7 known vulnerabilities in glibc@2.41-12%2Bdeb13u3 (postgres)
How to fix
No fixed version of glibc is available yet. Check whether postgres 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 openldap@2.6.10%2Bdfsg-1 (postgres)
How to fix
No fixed version of openldap is available yet. Check whether postgres 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.13-1~deb13u1 (postgres)
How to fix
No fixed version of systemd is available yet. Check whether postgres 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 4 known vulnerabilities in libsepol@2.7-1 (rabbitmq:3.8.14-management)
How to fix
Update libsepol from 2.7-1 to 2.7-1ubuntu0.1 or later in rabbitmq:3.8.14-management. 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-1ubuntu0.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-36084 fixed in 2.7-1ubuntu0.1
- Low CVE-2021-36085 fixed in 2.7-1ubuntu0.1
- Low CVE-2021-36086 fixed in 2.7-1ubuntu0.1
- Low CVE-2021-36087 fixed in 2.7-1ubuntu0.1
Low 3 known vulnerabilities in libgcrypt20@1.11.0-7 (postgres)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether postgres 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 CVE-2026-41989 fixed in 1.11.0-7+deb13u1
Low 2 known vulnerabilities in coreutils@9.7-3 (postgres)
How to fix
No fixed version of coreutils is available yet. Check whether postgres 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 sqlite3@3.46.1-7%2Bdeb13u1 (postgres)
How to fix
No fixed version of sqlite3 is available yet. Check whether postgres 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 CVE-2025-70873 fixed in no fix yet
Low 2 known vulnerabilities in util-linux@2.41-5 (postgres)
How to fix
No fixed version of util-linux is available yet. Check whether postgres 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 CVE-2025-14104 fixed in no fix yet
Low 2 known vulnerabilities in pcre3@2%3A8.39-9 (rabbitmq:3.8.14-management)
How to fix
Update pcre3 from 2%3A8.39-9 to 2:8.39-9ubuntu0.1 or later in rabbitmq:3.8.14-management. 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.39-9ubuntu0.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-2020-14155 fixed in 2:8.39-9ubuntu0.1
- Low CVE-2019-20838 fixed in 2:8.39-9ubuntu0.1
Low 1 known vulnerability in image-spec@1.0.1 (portainer/portainer:latest)
How to fix
Update image-spec from 1.0.1 to 1.0.2 or later in portainer/portainer: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.0.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 GHSA-77vh-xpmg-72qh fixed in 1.0.2
Low 1 known vulnerability in apt@3.0.3 (postgres)
How to fix
No fixed version of apt is available yet. Check whether postgres 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)
How to fix
No fixed version of gnupg2 is available yet. Check whether postgres 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 gnutls28@3.8.9-3%2Bdeb13u4 (postgres)
How to fix
No fixed version of gnutls28 is available yet. Check whether postgres needs gnutls28 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-3389 fixed in no fix yet
Low 1 known vulnerability in libxslt@1.1.35-1.2%2Bdeb13u3 (postgres)
How to fix
No fixed version of libxslt is available yet. Check whether postgres 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.6-1~deb13u1 (postgres)
How to fix
No fixed version of openssl is available yet. Check whether postgres 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 shadow@1%3A4.17.4-2 (postgres)
How to fix
No fixed version of shadow is available yet. Check whether postgres 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 sys@0.1.0 (postgres)
How to fix
Update sys from 0.1.0 to 0.44.0 or later in postgres. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.44.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-39824 fixed in 0.44.0
Low 1 known vulnerability in bash@4.4.18-2ubuntu1.2 (rabbitmq:3.8.14-management)
How to fix
Update bash from 4.4.18-2ubuntu1.2 to 4.4.18-2ubuntu1.3 or later in rabbitmq:3.8.14-management. 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.4.18-2ubuntu1.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
- Low CVE-2019-18276 fixed in 4.4.18-2ubuntu1.3
Low 1 known vulnerability in gmp@2%3A6.1.2%2Bdfsg-2 (rabbitmq:3.8.14-management)
How to fix
Update gmp from 2%3A6.1.2%2Bdfsg-2 to 2:6.1.2+dfsg-2ubuntu0.1 or later in rabbitmq:3.8.14-management. 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:6.1.2+dfsg-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
- Low CVE-2021-43618 fixed in 2:6.1.2+dfsg-2ubuntu0.1
Low 1 known vulnerability in pam@1.1.8-3.6ubuntu2.18.04.2 (rabbitmq:3.8.14-management)
How to fix
Update pam from 1.1.8-3.6ubuntu2.18.04.2 to 1.1.8-3.6ubuntu2.18.04.4 or later in rabbitmq:3.8.14-management. 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.8-3.6ubuntu2.18.04.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-2022-28321 fixed in 1.1.8-3.6ubuntu2.18.04.4
Low 1 known vulnerability in shadow@1%3A4.5-1ubuntu2 (rabbitmq:3.8.14-management)
How to fix
Update shadow from 1%3A4.5-1ubuntu2 to 1:4.5-1ubuntu2.2 or later in rabbitmq:3.8.14-management. 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:4.5-1ubuntu2.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-2018-7169 fixed in 1:4.5-1ubuntu2.2
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 1 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.