Repository scan
geoprism-registry
terraframe/geoprism-registry · branch main · scanned 2 Apr 2026
High 565
High 94 known vulnerabilities in stdlib@1.16.7 (postgis/postgis:14-3.2)
How to fix
Update stdlib from 1.16.7 to 1.19.9 or later in postgis/postgis:14-3.2. 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.9); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2021-39293 fixed in 1.16.8
- High CVE-2021-41771 fixed in 1.16.10
- High CVE-2021-41772 fixed in 1.16.10
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-24921 fixed in 1.16.15
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-28327 fixed in 1.17.9
- High CVE-2022-2879 fixed in 1.18.7
- High CVE-2022-2880 fixed in 1.18.7
- High CVE-2022-29804 fixed in 1.17.11
- High CVE-2022-30630 fixed in 1.17.12
- High CVE-2022-30631 fixed in 1.17.12
- High CVE-2022-30632 fixed in 1.17.12
- High CVE-2022-30633 fixed in 1.17.12
- High CVE-2022-30634 fixed in 1.17.11
- and 74 more
High 68 known vulnerabilities in tiff@4.2.0-1%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update tiff from 4.2.0-1%2Bdeb11u1 to 4.2.0-1+deb11u6 or later in postgis/postgis:14-3.2. 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.2.0-1+deb11u6); 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-52356 fixed in 4.2.0-1+deb11u6
- High CVE-2024-7006 fixed in 4.2.0-1+deb11u6
- High CVE-2022-3570 fixed in 4.2.0-1+deb11u3
- High CVE-2026-4775 fixed in no fix yet
- High CVE-2023-25434 fixed in 4.2.0-1+deb11u4
- High CVE-2025-9900 fixed in 4.2.0-1+deb11u7
- Medium CVE-2022-1354 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-1622 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-1623 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2056 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2057 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2058 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2867 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2868 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-2869 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-3597 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-3598 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-3599 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-3626 fixed in 4.2.0-1+deb11u3
- Medium CVE-2022-3627 fixed in 4.2.0-1+deb11u3
- and 48 more
High 56 known vulnerabilities in libde265@1.0.8-1 (postgis/postgis:14-3.2)
How to fix
Update libde265 from 1.0.8-1 to 1.0.11-0+deb11u1 or later in postgis/postgis:14-3.2. 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.11-0+deb11u1); 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-36409 fixed in 1.0.11-0+deb11u1
- High CVE-2022-47655 fixed in 1.0.11-0+deb11u1
- High CVE-2022-47664 fixed in 1.0.11-0+deb11u1
- High CVE-2022-47665 fixed in 1.0.11-0+deb11u1
- High CVE-2023-25221 fixed in 1.0.11-0+deb11u1
- High CVE-2023-43887 fixed in 1.0.11-0+deb11u2
- High CVE-2026-33164 fixed in no fix yet
- High CVE-2020-21598 fixed in 1.0.11-0+deb11u1
- High CVE-2023-27103 fixed in 1.0.11-0+deb11u2
- High CVE-2023-49465 fixed in 1.0.11-0+deb11u3
- High CVE-2023-49467 fixed in 1.0.11-0+deb11u3
- High CVE-2023-49468 fixed in 1.0.11-0+deb11u3
- High CVE-2022-1253 fixed in 1.0.11-0+deb11u1
- Medium CVE-2021-36408 fixed in 1.0.11-0+deb11u1
- Medium CVE-2021-36410 fixed in 1.0.11-0+deb11u1
- Medium CVE-2021-36411 fixed in 1.0.11-0+deb11u1
- Medium CVE-2023-24752 fixed in 1.0.11-0+deb11u1
- Medium CVE-2023-24754 fixed in 1.0.11-0+deb11u1
- Medium CVE-2023-24755 fixed in 1.0.11-0+deb11u1
- Medium CVE-2023-24756 fixed in 1.0.11-0+deb11u1
- and 36 more
High 42 known vulnerabilities in mariadb-10.5@1%3A10.5.15-0%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update mariadb-10.5 from 1%3A10.5.15-0%2Bdeb11u1 to 1:10.5.18-0+deb11u1 or later in postgis/postgis:14-3.2. 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.5.18-0+deb11u1); 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-46669 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27376 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27377 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27378 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27379 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27380 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27381 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27382 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27383 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27384 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27386 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27387 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27444 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27445 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27446 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27447 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27448 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27449 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27451 fixed in 1:10.5.18-0+deb11u1
- High CVE-2022-27452 fixed in 1:10.5.18-0+deb11u1
- and 22 more
High 27 known vulnerabilities in openssl@1.1.1n-0%2Bdeb11u3 (postgis/postgis:14-3.2)
How to fix
Update openssl from 1.1.1n-0%2Bdeb11u3 to 1.1.1n-0+deb11u4 or later in postgis/postgis:14-3.2. 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.1n-0+deb11u4); 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.1n-0+deb11u4
- High CVE-2025-69419 fixed in 1.1.1w-0+deb11u5
- High CVE-2023-0464 fixed in 1.1.1n-0+deb11u5
- High CVE-2024-4741 fixed in 1.1.1w-0+deb11u2
- High CVE-2025-69420 fixed in 1.1.1w-0+deb11u5
- High CVE-2025-69421 fixed in 1.1.1w-0+deb11u5
- High CVE-2025-9230 fixed in 1.1.1w-0+deb11u4
- High CVE-2024-5535 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2022-4304 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2022-4450 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0215 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2025-69418 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2024-13176 fixed in 1.1.1w-0+deb11u3
- Medium CVE-2024-9143 fixed in 1.1.1w-0+deb11u2
- Medium CVE-2025-68160 fixed in 1.1.1w-0+deb11u5
- Medium CVE-2022-2097 fixed in 1.1.1n-0+deb11u4
- Medium CVE-2023-0465 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-0466 fixed in 1.1.1n-0+deb11u5
- Medium CVE-2023-3446 fixed in 1.1.1v-0~deb11u1
- Medium CVE-2023-3817 fixed in 1.1.1v-0~deb11u1
- and 7 more
High 26 known vulnerabilities in curl@7.74.0-1.3%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update curl from 7.74.0-1.3%2Bdeb11u2 to 7.74.0-1.3+deb11u12 or later in postgis/postgis:14-3.2. 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.74.0-1.3+deb11u12); 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-2398 fixed in 7.74.0-1.3+deb11u12
- High CVE-2023-27533 fixed in 7.74.0-1.3+deb11u8
- High CVE-2023-27534 fixed in 7.74.0-1.3+deb11u8
- High CVE-2022-32221 fixed in 7.74.0-1.3+deb11u5
- High CVE-2023-38545 fixed in 7.74.0-1.3+deb11u10
- Medium CVE-2023-23916 fixed in 7.74.0-1.3+deb11u7
- Medium CVE-2023-27538 fixed in 7.74.0-1.3+deb11u8
- Medium CVE-2022-43552 fixed in 7.74.0-1.3+deb11u5
- Medium CVE-2023-27535 fixed in 7.74.0-1.3+deb11u8
- Medium CVE-2023-27536 fixed in 7.74.0-1.3+deb11u8
- Medium CVE-2023-28321 fixed in 7.74.0-1.3+deb11u9
- Medium CVE-2023-46218 fixed in 7.74.0-1.3+deb11u11
- Medium CVE-2024-7264 fixed in 7.74.0-1.3+deb11u13
- Medium CVE-2024-8096 fixed in 7.74.0-1.3+deb11u14
- Low CVE-2021-22922 fixed in no fix yet
- Low CVE-2021-22923 fixed in no fix yet
- Low CVE-2023-28320 fixed in no fix yet
- Low CVE-2024-2379 fixed in no fix yet
- Low CVE-2025-0725 fixed in no fix yet
- Low CVE-2025-10966 fixed in no fix yet
- and 6 more
High 23 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7%2Bdeb11u2 to 2.9.10+dfsg-6.7+deb11u5 or later in postgis/postgis:14-3.2. 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.10+dfsg-6.7+deb11u5); 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-2309 fixed in 2.9.10+dfsg-6.7+deb11u5
- High CVE-2022-40303 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-25062 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-6021 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2022-40304 fixed in 2.9.10+dfsg-6.7+deb11u3
- High CVE-2024-56171 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-24928 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2022-49043 fixed in 2.9.10+dfsg-6.7+deb11u6
- High CVE-2025-49794 fixed in 2.9.10+dfsg-6.7+deb11u8
- High CVE-2025-49796 fixed in 2.9.10+dfsg-6.7+deb11u8
- Medium CVE-2025-32414 fixed in 2.9.10+dfsg-6.7+deb11u7
- Medium CVE-2016-3709 fixed in 2.9.10+dfsg-6.7+deb11u5
- Medium CVE-2025-9714 fixed in 2.9.10+dfsg-6.7+deb11u9
- Medium CVE-2023-28484 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-29469 fixed in 2.9.10+dfsg-6.7+deb11u4
- Medium CVE-2023-39615 fixed in 2.9.10+dfsg-6.7+deb11u6
- Medium CVE-2023-45322 fixed in 2.9.10+dfsg-6.7+deb11u6
- Low CVE-2024-34459 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-6170 fixed in 2.9.10+dfsg-6.7+deb11u8
- Low CVE-2025-8732 fixed in no fix yet
- and 3 more
High 18 known vulnerabilities in poppler@20.09.0-3.1 (postgis/postgis:14-3.2)
How to fix
Update poppler from 20.09.0-3.1 to 20.09.0-3.1+deb11u1 or later in postgis/postgis:14-3.2. 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 20.09.0-3.1+deb11u1); 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-38784 fixed in 20.09.0-3.1+deb11u1
- Medium CVE-2025-32364 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2025-32365 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2024-56378 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2020-36024 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2020-36023 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2022-27337 fixed in 20.09.0-3.1+deb11u1
- Medium CVE-2022-37050 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2022-37051 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2022-37052 fixed in 20.09.0-3.1+deb11u2
- Medium CVE-2022-38349 fixed in 20.09.0-3.1+deb11u2
- Low CVE-2013-4472 fixed in no fix yet
- Low CVE-2017-2814 fixed in no fix yet
- Low CVE-2017-2818 fixed in no fix yet
- Low CVE-2017-2820 fixed in no fix yet
- Low CVE-2017-9083 fixed in no fix yet
- Low CVE-2022-24106 fixed in no fix yet
- Low CVE-2024-6239 fixed in no fix yet
High 17 known vulnerabilities in aa_ER@saaho (postgis/postgis:14-3.2)
How to fix
Update aa_ER from saaho to 2.31-13+deb11u9 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.31-13+deb11u9); 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-2961 fixed in 2.31-13+deb11u9
- High CVE-2024-33601 fixed in 2.31-13+deb11u10
- High CVE-2024-33602 fixed in 2.31-13+deb11u10
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2021-3999 fixed in 2.31-13+deb11u4
- High CVE-2023-4911 fixed in 2.31-13+deb11u7
- High CVE-2025-4802 fixed in 2.31-13+deb11u13
- High CVE-2024-33599 fixed in 2.31-13+deb11u10
- Medium CVE-2024-33600 fixed in 2.31-13+deb11u10
- Medium CVE-2025-0395 fixed in 2.31-13+deb11u12
- 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
High 15 known vulnerabilities in openjpeg2@2.4.0-3 (postgis/postgis:14-3.2)
How to fix
Update openjpeg2 from 2.4.0-3 to 2.4.0-3+deb11u1 or later in postgis/postgis:14-3.2. 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.0-3+deb11u1); 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-3575 fixed in 2.4.0-3+deb11u1
- Medium CVE-2021-29338 fixed in 2.4.0-3+deb11u1
- Medium CVE-2022-1122 fixed in 2.4.0-3+deb11u1
- Medium CVE-2024-56826 fixed in 2.4.0-3+deb11u1
- Medium CVE-2024-56827 fixed in 2.4.0-3+deb11u1
- Medium CVE-2025-50952 fixed in 2.4.0-3+deb11u2
- Low CVE-2016-10505 fixed in no fix yet
- Low CVE-2016-9113 fixed in no fix yet
- Low CVE-2016-9114 fixed in no fix yet
- Low CVE-2016-9115 fixed in no fix yet
- Low CVE-2016-9116 fixed in no fix yet
- Low CVE-2016-9117 fixed in no fix yet
- Low CVE-2016-9580 fixed in no fix yet
- Low CVE-2016-9581 fixed in no fix yet
- Low CVE-2018-16376 fixed in no fix yet
High 14 known vulnerabilities in libpng1.6@1.6.37-3 (postgis/postgis:14-3.2)
How to fix
Update libpng1.6 from 1.6.37-3 to 1.6.37-3+deb11u1 or later in postgis/postgis:14-3.2. 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.37-3+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-64720 fixed in 1.6.37-3+deb11u1
- High CVE-2025-65018 fixed in 1.6.37-3+deb11u1
- High CVE-2025-66293 fixed in 1.6.37-3+deb11u1
- High CVE-2026-33416 fixed in no fix yet
- High CVE-2026-33636 fixed in no fix yet
- High CVE-2026-25646 fixed in 1.6.37-3+deb11u2
- Medium CVE-2025-64505 fixed in 1.6.37-3+deb11u1
- Medium CVE-2025-64506 fixed in 1.6.37-3+deb11u1
- Medium CVE-2026-22695 fixed in 1.6.37-3+deb11u2
- Medium CVE-2026-22801 fixed in 1.6.37-3+deb11u2
- Low CVE-2019-6129 fixed in no fix yet
- Low CVE-2021-4214 fixed in no fix yet
- Low CVE-2025-28164 fixed in no fix yet
- Low CVE-2026-3713 fixed in no fix yet
High 13 known vulnerabilities in expat@2.2.10-2%2Bdeb11u3 (postgis/postgis:14-3.2)
How to fix
Update expat from 2.2.10-2%2Bdeb11u3 to 2.2.10-2+deb11u5 or later in postgis/postgis:14-3.2. 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.10-2+deb11u5); 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.2.10-2+deb11u5
- High CVE-2023-52425 fixed in 2.2.10-2+deb11u6
- High CVE-2024-45490 fixed in 2.2.10-2+deb11u6
- High CVE-2022-40674 fixed in 2.2.10-2+deb11u4
- High CVE-2024-45491 fixed in 2.2.10-2+deb11u6
- High CVE-2024-45492 fixed in 2.2.10-2+deb11u6
- Medium CVE-2026-32776 fixed in no fix yet
- Medium CVE-2026-32777 fixed in no fix yet
- Medium CVE-2024-50602 fixed in 2.2.10-2+deb11u7
- Low CVE-2013-0340 fixed in no fix yet
- Low CVE-2023-52426 fixed in no fix yet
- Low CVE-2024-28757 fixed in no fix yet
- Low CVE-2026-32778 fixed in no fix yet
High 13 known vulnerabilities in gnutls28@3.7.1-5%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update gnutls28 from 3.7.1-5%2Bdeb11u2 to 3.7.1-5+deb11u3 or later in postgis/postgis:14-3.2. 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.7.1-5+deb11u3); 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-0361 fixed in 3.7.1-5+deb11u3
- High CVE-2024-0553 fixed in 3.7.1-5+deb11u5
- High CVE-2024-0567 fixed in 3.7.1-5+deb11u5
- Medium CVE-2025-9820 fixed in 3.7.1-5+deb11u9
- Medium CVE-2024-28835 fixed in 3.7.1-5+deb11u6
- Medium CVE-2024-12243 fixed in 3.7.1-5+deb11u7
- Medium CVE-2024-28834 fixed in 3.7.1-5+deb11u6
- Medium CVE-2025-14831 fixed in 3.7.1-5+deb11u9
- Medium CVE-2023-5981 fixed in 3.7.1-5+deb11u4
- Medium CVE-2025-32988 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-32990 fixed in 3.7.1-5+deb11u8
- Medium CVE-2025-6395 fixed in 3.7.1-5+deb11u8
- Low CVE-2011-3389 fixed in no fix yet
High 12 known vulnerabilities in systemd@247.3-7 (postgis/postgis:14-3.2)
How to fix
Update systemd from 247.3-7 to 247.3-7+deb11u6 or later in postgis/postgis:14-3.2. 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 247.3-7+deb11u6); 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-50387 fixed in 247.3-7+deb11u6
- High CVE-2023-50868 fixed in 247.3-7+deb11u6
- Medium CVE-2025-4598 fixed in 247.3-7+deb11u7
- Medium CVE-2022-3821 fixed in 247.3-7+deb11u2
- Medium CVE-2022-4415 fixed in 247.3-7+deb11u2
- Medium CVE-2026-29111 fixed in no fix yet
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- Low CVE-2013-4392 fixed in no fix yet
- Low CVE-2020-13529 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
High 10 known vulnerabilities in runc@1.0.1 (postgis/postgis:14-3.2)
How to fix
Update runc from 1.0.1 to 1.1.5 or later in postgis/postgis:14-3.2. 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-52565 fixed in 1.2.8
- High CVE-2025-52881 fixed in 1.2.8
- High CVE-2024-21626 fixed in 1.1.12
- Medium CVE-2024-45310 fixed in 1.1.14
- 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
- Low CVE-2023-25809 fixed in 1.1.5
High 9 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u6 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.18.3-6+deb11u6); 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-24528 fixed in 1.18.3-6+deb11u6
- High CVE-2024-37370 fixed in 1.18.3-6+deb11u5
- High CVE-2022-42898 fixed in 1.18.3-6+deb11u3
- High CVE-2024-37371 fixed in 1.18.3-6+deb11u5
- Medium CVE-2025-3576 fixed in 1.18.3-6+deb11u7
- Medium CVE-2023-36054 fixed in 1.18.3-6+deb11u4
- 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
High 9 known vulnerabilities in nss@2%3A3.61-1%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update nss from 2%3A3.61-1%2Bdeb11u2 to 2:3.61-1+deb11u4 or later in postgis/postgis:14-3.2. 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:3.61-1+deb11u4); 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-0743 fixed in 2:3.61-1+deb11u4
- High CVE-2023-0767 fixed in 2:3.61-1+deb11u3
- High CVE-2024-6609 fixed in 2:3.61-1+deb11u4
- High CVE-2024-6602 fixed in 2:3.61-1+deb11u4
- High CVE-2026-2781 fixed in 2:3.61-1+deb11u5
- Low CVE-2017-11695 fixed in no fix yet
- Low CVE-2017-11696 fixed in no fix yet
- Low CVE-2017-11697 fixed in no fix yet
- Low CVE-2017-11698 fixed in no fix yet
High 8 known vulnerabilities in giflib@5.1.9-2 (postgis/postgis:14-3.2)
How to fix
No fixed version of giflib is available yet. Check whether postgis/postgis:14-3.2 needs giflib at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-26740 fixed in no fix yet
- Medium CVE-2026-23868 fixed in no fix yet
- Low CVE-2020-23922 fixed in no fix yet
- Low CVE-2021-40633 fixed in no fix yet
- Low CVE-2022-28506 fixed in no fix yet
- Low CVE-2023-39742 fixed in no fix yet
- Low CVE-2023-48161 fixed in no fix yet
- Low CVE-2024-45993 fixed in no fix yet
High 8 known vulnerabilities in libxslt@1.1.34-4 (postgis/postgis:14-3.2)
How to fix
Update libxslt from 1.1.34-4 to 1.1.34-4+deb11u3 or later in postgis/postgis:14-3.2. 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.34-4+deb11u3); 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-7424 fixed in 1.1.34-4+deb11u3
- High CVE-2024-55549 fixed in 1.1.34-4+deb11u2
- High CVE-2025-24855 fixed in 1.1.34-4+deb11u2
- High CVE-2021-30560 fixed in 1.1.34-4+deb11u1
- Medium CVE-2025-10911 fixed in no fix yet
- Low CVE-2015-9019 fixed in no fix yet
- Low CVE-2023-40403 fixed in 1.1.34-4+deb11u3
- Low CVE-2025-11731 fixed in no fix yet
High 6 known vulnerabilities in libheif@1.11.0-1 (postgis/postgis:14-3.2)
How to fix
Update libheif from 1.11.0-1 to 1.11.0-1+deb11u2 or later in postgis/postgis:14-3.2. 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.11.0-1+deb11u2); 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-0996 fixed in 1.11.0-1+deb11u2
- High CVE-2024-41311 fixed in 1.11.0-1+deb11u1
- Medium CVE-2023-29659 fixed in 1.11.0-1+deb11u2
- Low CVE-2023-49463 fixed in no fix yet
- Low CVE-2024-25269 fixed in no fix yet
- Low CVE-2026-3949 fixed in no fix yet
High 6 known vulnerabilities in protobuf-java@3.5.1 (terraframe/geoprism-registry:latest)
How to fix
Update protobuf-java from 3.5.1 to 3.16.1 or later in terraframe/geoprism-registry: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.16.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-2021-22569 fixed in 3.16.1
- High CVE-2022-3509 fixed in 3.16.3
- High CVE-2022-3510 fixed in 3.16.3
- High CVE-2024-7254 fixed in 3.25.5
- Medium CVE-2021-22570 fixed in 3.15.0
- Medium CVE-2022-3171 fixed in 3.16.3
High 5 known vulnerabilities in aom@1.0.0.errata1-3 (postgis/postgis:14-3.2)
How to fix
Update aom from 1.0.0.errata1-3 to 1.0.0.errata1-3+deb11u1 or later in postgis/postgis:14-3.2. 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.0.errata1-3+deb11u1); 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-2020-36131 fixed in 1.0.0.errata1-3+deb11u1
- High CVE-2020-36133 fixed in 1.0.0.errata1-3+deb11u1
- High CVE-2024-5171 fixed in 1.0.0.errata1-3+deb11u2
- Medium CVE-2020-36130 fixed in 1.0.0.errata1-3+deb11u1
- Medium CVE-2020-36135 fixed in 1.0.0.errata1-3+deb11u1
High 5 known vulnerabilities in perl@5.32.1-4%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update perl from 5.32.1-4%2Bdeb11u2 to 5.32.1-4+deb11u3 or later in postgis/postgis:14-3.2. 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.32.1-4+deb11u3); 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-47038 fixed in 5.32.1-4+deb11u3
- High CVE-2020-16156 fixed in 5.32.1-4+deb11u4
- High CVE-2023-31484 fixed in 5.32.1-4+deb11u4
- Low CVE-2011-4116 fixed in no fix yet
- Low CVE-2023-31486 fixed in no fix yet
High 4 known vulnerabilities in jackson-core@2.11.2 (orientdb:3.2)
How to fix
Update jackson-core from 2.11.2 to 2.15.0 or later in orientdb:3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.15.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-52999 fixed in 2.15.0
- Medium CVE-2025-49128 fixed in 2.13.0
- Medium GHSA-72hv-8253-57qq fixed in 2.18.6
- Medium GHSA-72hv-8253-57qq fixed in 2.21.1
High 4 known vulnerabilities in json@20180813 (terraframe/geoprism-registry:latest)
How to fix
Update json from 20180813 to 20230227 or later in terraframe/geoprism-registry: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 20230227); 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-45688 fixed in 20230227
- High CVE-2022-45689 fixed in 20220320
- High CVE-2022-45690 fixed in 20220320
- High CVE-2023-5072 fixed in 20231013
High 3 known vulnerabilities in hazelcast@3.12.13 (orientdb:3.2)
How to fix
No fixed version of hazelcast is available yet. Check whether orientdb:3.2 needs hazelcast 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-45860 fixed in no fix yet
- High CVE-2023-33265 fixed in 5.0.5
- High CVE-2023-45859 fixed in no fix yet
High 3 known vulnerabilities in nghttp2@1.43.0-1 (postgis/postgis:14-3.2)
How to fix
No fixed version of nghttp2 is available yet. Check whether postgis/postgis:14-3.2 needs nghttp2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-27135 fixed in no fix yet
- Medium CVE-2024-28182 fixed in 1.43.0-1+deb11u2
- Low CVE-2023-44487 fixed in 1.43.0-1+deb11u1
High 3 known vulnerabilities in pcre2@10.36-2 (postgis/postgis:14-3.2)
How to fix
Update pcre2 from 10.36-2 to 10.36-2+deb11u1 or later in postgis/postgis:14-3.2. 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.36-2+deb11u1); 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-1586 fixed in 10.36-2+deb11u1
- High CVE-2022-1587 fixed in 10.36-2+deb11u1
- Low CVE-2022-41409 fixed in no fix yet
High 2 known vulnerabilities in freetype@2.10.4%2Bdfsg-1%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update freetype from 2.10.4%2Bdfsg-1%2Bdeb11u1 to 2.10.4+dfsg-1+deb11u2 or later in postgis/postgis:14-3.2. 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.10.4+dfsg-1+deb11u2); 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-27363 fixed in 2.10.4+dfsg-1+deb11u2
- Low CVE-2022-31782 fixed in no fix yet
High 2 known vulnerabilities in gnupg2@2.2.27-2%2Bdeb11u2 (postgis/postgis:14-3.2)
How to fix
Update gnupg2 from 2.2.27-2%2Bdeb11u2 to 2.2.27-2+deb11u3 or later in postgis/postgis:14-3.2. 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.27-2+deb11u3); 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-68973 fixed in 2.2.27-2+deb11u3
- Low CVE-2022-3219 fixed in no fix yet
High 2 known vulnerabilities in libksba@1.5.0-3 (postgis/postgis:14-3.2)
How to fix
Update libksba from 1.5.0-3 to 1.5.0-3+deb11u1 or later in postgis/postgis:14-3.2. 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.0-3+deb11u1); 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-3515 fixed in 1.5.0-3+deb11u1
- High CVE-2022-47629 fixed in 1.5.0-3+deb11u2
High 2 known vulnerabilities in libtasn1-6@4.16.0-2 (postgis/postgis:14-3.2)
How to fix
Update libtasn1-6 from 4.16.0-2 to 4.16.0-2+deb11u1 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.16.0-2+deb11u1); 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-46848 fixed in 4.16.0-2+deb11u1
- Medium CVE-2024-12133 fixed in 4.16.0-2+deb11u2
High 2 known vulnerabilities in ncurses@6.2%2B20201114-2 (postgis/postgis:14-3.2)
How to fix
Update ncurses from 6.2%2B20201114-2 to 6.2+20201114-2+deb11u1 or later in postgis/postgis:14-3.2. 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.2+20201114-2+deb11u1); 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-29458 fixed in 6.2+20201114-2+deb11u1
- High CVE-2023-29491 fixed in 6.2+20201114-2+deb11u2
High 2 known vulnerabilities in pam@1.4.0-9%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update pam from 1.4.0-9%2Bdeb11u1 to 1.4.0-9+deb11u2 or later in postgis/postgis:14-3.2. 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.0-9+deb11u2); 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-6020 fixed in 1.4.0-9+deb11u2
- Medium CVE-2024-22365 fixed in 1.4.0-9+deb11u2
High 2 known vulnerabilities in xerces-c@3.2.3%2Bdebian-3 (postgis/postgis:14-3.2)
How to fix
Update xerces-c from 3.2.3%2Bdebian-3 to 3.2.3+debian-3+deb11u1 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.2.3+debian-3+deb11u1); 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-37536 fixed in 3.2.3+debian-3+deb11u1
- Low CVE-2012-0880 fixed in no fix yet
High 2 known vulnerabilities in lz4-java@1.8.0 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of lz4-java is available yet. Check whether terraframe/geoprism-registry:latest needs lz4-java at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2025-66566 fixed in no fix yet
- High CVE-2025-12183 fixed in 1.8.1
High 2 known vulnerabilities in org.hl7.fhir.utilities@6.4.0 (terraframe/geoprism-registry:latest)
How to fix
Update org.hl7.fhir.utilities from 6.4.0 to 6.9.4 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.9.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-2026-34359 fixed in 6.9.4
- High CVE-2026-33180 fixed in 6.9.0
High 2 known vulnerabilities in org.hl7.fhir.validation@6.4.0 (terraframe/geoprism-registry:latest)
How to fix
Update org.hl7.fhir.validation from 6.4.0 to 6.9.4 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.9.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-2026-34361 fixed in 6.9.4
- High CVE-2026-33180 fixed in 6.9.0
High 1 known vulnerability in e2scrub@.service (postgis/postgis:14-3.2)
How to fix
Update e2scrub from .service to 1.46.2-2+deb11u1 or later in postgis/postgis:14-3.2. 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.46.2-2+deb11u1); 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-1304 fixed in 1.46.2-2+deb11u1
High 1 known vulnerability in icu@67.1-7 (postgis/postgis:14-3.2)
How to fix
Update icu from 67.1-7 to 67.1-7+deb11u1 or later in postgis/postgis:14-3.2. 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 67.1-7+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-5222 fixed in 67.1-7+deb11u1
and 22 more groups with 22 findings
Medium 95
Medium 10 known vulnerabilities in curl@8.5.0-2ubuntu10.6 (terraframe/geoprism-registry:latest)
How to fix
Update curl from 8.5.0-2ubuntu10.6 to 8.5.0-2ubuntu10.7 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.5.0-2ubuntu10.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-14017 fixed in 8.5.0-2ubuntu10.7
- Medium CVE-2026-1965 fixed in 8.5.0-2ubuntu10.8
- Medium CVE-2026-3783 fixed in 8.5.0-2ubuntu10.8
- Low CVE-2025-0167 fixed in 8.5.0-2ubuntu10.8
- Low CVE-2025-10148 fixed in 8.5.0-2ubuntu10.7
- Low CVE-2025-14524 fixed in 8.5.0-2ubuntu10.7
- Low CVE-2025-14819 fixed in 8.5.0-2ubuntu10.7
- Low CVE-2025-15079 fixed in 8.5.0-2ubuntu10.7
- Low CVE-2025-15224 fixed in 8.5.0-2ubuntu10.7
- Low CVE-2026-3784 fixed in 8.5.0-2ubuntu10.8
Medium 10 known vulnerabilities in libpng1.6@1.6.43-5build1 (terraframe/geoprism-registry:latest)
How to fix
Update libpng1.6 from 1.6.43-5build1 to 1.6.43-5ubuntu0.4 or later in terraframe/geoprism-registry: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.43-5ubuntu0.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-28162 fixed in 1.6.43-5ubuntu0.4
- Medium CVE-2025-28164 fixed in 1.6.43-5ubuntu0.4
- Medium CVE-2025-64505 fixed in 1.6.43-5ubuntu0.1
- Medium CVE-2025-64506 fixed in 1.6.43-5ubuntu0.1
- Medium CVE-2025-64720 fixed in 1.6.43-5ubuntu0.1
- Medium CVE-2025-65018 fixed in 1.6.43-5ubuntu0.1
- Medium CVE-2025-66293 fixed in 1.6.43-5ubuntu0.3
- Medium CVE-2026-22695 fixed in 1.6.43-5ubuntu0.3
- Medium CVE-2026-22801 fixed in 1.6.43-5ubuntu0.3
- Medium CVE-2026-25646 fixed in 1.6.43-5ubuntu0.5
Medium 9 known vulnerabilities in binutils@2.42-4ubuntu2.6 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of binutils is available yet. Check whether terraframe/geoprism-registry:latest 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
- Medium CVE-2025-1180 fixed in no fix yet
- Medium CVE-2025-11412 fixed in 2.42-4ubuntu2.8
- Medium CVE-2025-11413 fixed in 2.42-4ubuntu2.8
- Medium CVE-2025-11414 fixed in 2.42-4ubuntu2.8
- Medium CVE-2025-11494 fixed in 2.42-4ubuntu2.8
- Medium CVE-2025-11839 fixed in 2.42-4ubuntu2.7
- Medium CVE-2025-11840 fixed in 2.42-4ubuntu2.7
- Low CVE-2025-1152 fixed in no fix yet
- Low CVE-2017-13716 fixed in no fix yet
Medium 8 known vulnerabilities in openssl@3.0.13-0ubuntu3.6 (terraframe/geoprism-registry:latest)
How to fix
Update openssl from 3.0.13-0ubuntu3.6 to 3.0.13-0ubuntu3.7 or later in terraframe/geoprism-registry: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.13-0ubuntu3.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-15467 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2025-68160 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2025-69418 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2025-69419 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2025-69420 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2026-22795 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2026-22796 fixed in 3.0.13-0ubuntu3.7
- Low CVE-2025-69421 fixed in 3.0.13-0ubuntu3.7
Medium 7 known vulnerabilities in sqlite3@3.34.1-3 (postgis/postgis:14-3.2)
How to fix
Update sqlite3 from 3.34.1-3 to 3.34.1-3+deb11u1 or later in postgis/postgis:14-3.2. 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.34.1-3+deb11u1); 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.34.1-3+deb11u1
- Low CVE-2021-36690 fixed in 3.34.1-3+deb11u1
- Low CVE-2021-45346 fixed in no fix yet
- Low CVE-2022-35737 fixed in no fix yet
- Low CVE-2025-29088 fixed in no fix yet
- Low CVE-2025-52099 fixed in no fix yet
- Low CVE-2025-70873 fixed in no fix yet
Medium 7 known vulnerabilities in libssh@0.10.6-2ubuntu0.2 (terraframe/geoprism-registry:latest)
How to fix
Update libssh from 0.10.6-2ubuntu0.2 to 0.10.6-2ubuntu0.3 or later in terraframe/geoprism-registry: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.10.6-2ubuntu0.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-0964 fixed in 0.10.6-2ubuntu0.3
- Medium CVE-2026-0967 fixed in 0.10.6-2ubuntu0.3
- Medium CVE-2026-0968 fixed in 0.10.6-2ubuntu0.3
- Medium CVE-2026-3731 fixed in 0.10.6-2ubuntu0.4
- Low CVE-2025-8277 fixed in 0.10.6-2ubuntu0.3
- Low CVE-2026-0965 fixed in 0.10.6-2ubuntu0.3
- Low CVE-2026-0966 fixed in 0.10.6-2ubuntu0.3
Medium 4 known vulnerabilities in shadow@1%3A4.8.1-1 (postgis/postgis:14-3.2)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in postgis/postgis:14-3.2. 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.8.1-1+deb11u1); 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-4641 fixed in 1:4.8.1-1+deb11u1
- Low CVE-2007-5686 fixed in no fix yet
- Low CVE-2013-4235 fixed in no fix yet
- Low CVE-2023-29383 fixed in 1:4.8.1-1+deb11u1
Medium 3 known vulnerabilities in tar@1.34%2Bdfsg-1 (postgis/postgis:14-3.2)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in postgis/postgis:14-3.2. 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+dfsg-1+deb11u1); 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-39804 fixed in 1.34+dfsg-1+deb11u1
- Low CVE-2005-2541 fixed in no fix yet
- Low CVE-2022-48303 fixed in 1.34+dfsg-1+deb11u1
Medium 3 known vulnerabilities in be_BY@latin (terraframe/geoprism-registry:latest)
How to fix
Update be_BY from latin to 2.39-0ubuntu8.7 or later in terraframe/geoprism-registry: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.39-0ubuntu8.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-15281 fixed in 2.39-0ubuntu8.7
- Medium CVE-2026-0861 fixed in 2.39-0ubuntu8.7
- Medium CVE-2026-0915 fixed in 2.39-0ubuntu8.7
Medium 3 known vulnerabilities in expat@2.6.1-2ubuntu0.3 (terraframe/geoprism-registry:latest)
How to fix
Update expat from 2.6.1-2ubuntu0.3 to 2.6.1-2ubuntu0.4 or later in terraframe/geoprism-registry: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.6.1-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-2026-24515 fixed in 2.6.1-2ubuntu0.4
- Medium CVE-2025-66382 fixed in no fix yet
- Medium CVE-2026-25210 fixed in 2.6.1-2ubuntu0.4
Medium 3 known vulnerabilities in spring-webmvc@6.1.20 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of spring-webmvc is available yet. Check whether terraframe/geoprism-registry:latest needs spring-webmvc 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-41242 fixed in no fix yet
- Medium CVE-2026-22737 fixed in no fix yet
- Low CVE-2026-22735 fixed in no fix yet
Medium 2 known vulnerabilities in gdal@3.2.2%2Bdfsg-2%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
Update gdal from 3.2.2%2Bdfsg-2%2Bdeb11u1 to 3.2.2+dfsg-2+deb11u2 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.2.2+dfsg-2+deb11u2); 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-45943 fixed in 3.2.2+dfsg-2+deb11u2
- Low CVE-2025-29480 fixed in no fix yet
Medium 2 known vulnerabilities in libwebp@0.6.1-2.1 (postgis/postgis:14-3.2)
How to fix
Update libwebp from 0.6.1-2.1 to 0.6.1-2.1+deb11u1 or later in postgis/postgis:14-3.2. 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.6.1-2.1+deb11u1); 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-1999 fixed in 0.6.1-2.1+deb11u1
- Low CVE-2023-4863 fixed in 0.6.1-2.1+deb11u2
Medium 2 known vulnerabilities in gnutls28@3.8.3-1.1ubuntu3.4 (terraframe/geoprism-registry:latest)
How to fix
Update gnutls28 from 3.8.3-1.1ubuntu3.4 to 3.8.3-1.1ubuntu3.5 or later in terraframe/geoprism-registry: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.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-2025-14831 fixed in 3.8.3-1.1ubuntu3.5
- Low CVE-2025-9820 fixed in 3.8.3-1.1ubuntu3.5
Medium 2 known vulnerabilities in tomcat-catalina@11.0.14 (terraframe/geoprism-registry:latest)
How to fix
Update tomcat-catalina from 11.0.14 to 11.0.15 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 11.0.15); 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-66614 fixed in 11.0.15
- Low CVE-2026-24733 fixed in 11.0.15
Medium 1 known vulnerability in expat@2.6.1-2ubuntu0.4 (orientdb:3.2)
How to fix
No fixed version of expat is available yet. Check whether orientdb:3.2 needs expat 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-66382 fixed in no fix yet
Medium 1 known vulnerability in systemd@255.4-1ubuntu8.12 (orientdb:3.2)
How to fix
Update systemd from 255.4-1ubuntu8.12 to 255.4-1ubuntu8.14 or later in orientdb:3.2. 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.14); 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-29111 fixed in 255.4-1ubuntu8.14
Medium 1 known vulnerability in tar@1.35%2Bdfsg-3build1 (orientdb:3.2)
How to fix
No fixed version of tar is available yet. Check whether orientdb:3.2 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
Medium 1 known vulnerability in wget@1.21.4-1ubuntu4.1 (orientdb:3.2)
How to fix
No fixed version of wget is available yet. Check whether orientdb:3.2 needs wget 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-2021-31879 fixed in no fix yet
Medium 1 known vulnerability in dav1d@0.7.1-3 (postgis/postgis:14-3.2)
How to fix
Update dav1d from 0.7.1-3 to 0.7.1-3+deb11u1 or later in postgis/postgis:14-3.2. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.7.1-3+deb11u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-1580 fixed in 0.7.1-3+deb11u1
Medium 1 known vulnerability in sys@0.0.0-20210817142637-7d9622a276b7 (postgis/postgis:14-3.2)
How to fix
Update sys from 0.0.0-20210817142637-7d9622a276b7 to 0.0.0-20220412211240-33da011f77ad or later in postgis/postgis:14-3.2. 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 1 known vulnerability in commons-httpclient@3.1 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of commons-httpclient is available yet. Check whether terraframe/geoprism-registry:latest needs commons-httpclient 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-2012-5783 fixed in no fix yet
Medium 1 known vulnerability in commons-lang@2.6 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of commons-lang is available yet. Check whether terraframe/geoprism-registry:latest needs commons-lang 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-48924 fixed in no fix yet
Medium 1 known vulnerability in commons-lang3@3.17.0 (terraframe/geoprism-registry:latest)
How to fix
Update commons-lang3 from 3.17.0 to 3.18.0 or later in terraframe/geoprism-registry: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.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-48924 fixed in 3.18.0
Medium 1 known vulnerability in freetype@2.13.2%2Bdfsg-1build3 (terraframe/geoprism-registry:latest)
How to fix
Update freetype from 2.13.2%2Bdfsg-1build3 to 2.13.2+dfsg-1ubuntu0.1 or later in terraframe/geoprism-registry: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.13.2+dfsg-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
- Medium CVE-2026-23865 fixed in 2.13.2+dfsg-1ubuntu0.1
Medium 1 known vulnerability in jackson-core@2.18.1 (terraframe/geoprism-registry:latest)
How to fix
Update jackson-core from 2.18.1 to 2.18.6 or later in terraframe/geoprism-registry: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.18.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 GHSA-72hv-8253-57qq fixed in 2.18.6
Medium 1 known vulnerability in libtasn1-6@4.19.0-3ubuntu0.24.04.1 (terraframe/geoprism-registry:latest)
How to fix
Update libtasn1-6 from 4.19.0-3ubuntu0.24.04.1 to 4.19.0-3ubuntu0.24.04.2 or later in terraframe/geoprism-registry: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.19.0-3ubuntu0.24.04.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-2025-13151 fixed in 4.19.0-3ubuntu0.24.04.2
Medium 1 known vulnerability in log4j-core@2.17.1 (terraframe/geoprism-registry:latest)
How to fix
Update log4j-core from 2.17.1 to 2.25.3 or later in terraframe/geoprism-registry: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.25.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-68161 fixed in 2.25.3
Medium 1 known vulnerability in nimbus-jose-jwt@9.37.3 (terraframe/geoprism-registry:latest)
How to fix
Update nimbus-jose-jwt from 9.37.3 to 10.0.2 or later in terraframe/geoprism-registry: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.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-2025-53864 fixed in 10.0.2
Medium 1 known vulnerability in poi@4.1.2 (terraframe/geoprism-registry:latest)
How to fix
Update poi from 4.1.2 to 5.2.1 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.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-26336 fixed in 5.2.1
Medium 1 known vulnerability in poi-ooxml@4.1.2 (terraframe/geoprism-registry:latest)
How to fix
Update poi-ooxml from 4.1.2 to 5.4.0 or later in terraframe/geoprism-registry: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.4.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-31672 fixed in 5.4.0
Medium 1 known vulnerability in spring-web@6.1.20 (terraframe/geoprism-registry:latest)
How to fix
Update spring-web from 6.1.20 to 6.1.21 or later in terraframe/geoprism-registry:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.1.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
- Medium CVE-2025-41234 fixed in 6.1.21
Medium 1 known vulnerability in systemd@255.4-1ubuntu8.11 (terraframe/geoprism-registry:latest)
How to fix
Update systemd from 255.4-1ubuntu8.11 to 255.4-1ubuntu8.14 or later in terraframe/geoprism-registry: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.14); 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-29111 fixed in 255.4-1ubuntu8.14
Medium 1 known vulnerability in tar@1.35%2Bdfsg-3build1 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of tar is available yet. Check whether terraframe/geoprism-registry:latest 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
Medium 1 known vulnerability in wget@1.21.4-1ubuntu4.1 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of wget is available yet. Check whether terraframe/geoprism-registry:latest needs wget 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-2021-31879 fixed in no fix yet
Low 130
Low 99 known vulnerabilities in hdf5@1.10.6%2Brepack-4%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
No fixed version of hdf5 is available yet. Check whether postgis/postgis:14-3.2 needs hdf5 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-17507 fixed in no fix yet
- Low CVE-2018-13869 fixed in no fix yet
- Low CVE-2018-13870 fixed in no fix yet
- Low CVE-2018-14031 fixed in no fix yet
- Low CVE-2018-14033 fixed in no fix yet
- Low CVE-2018-14034 fixed in no fix yet
- Low CVE-2018-14035 fixed in no fix yet
- Low CVE-2018-14460 fixed in no fix yet
- Low CVE-2018-15671 fixed in no fix yet
- Low CVE-2018-16438 fixed in no fix yet
- Low CVE-2018-17432 fixed in no fix yet
- Low CVE-2018-17433 fixed in no fix yet
- Low CVE-2018-17435 fixed in no fix yet
- Low CVE-2018-17436 fixed in no fix yet
- Low CVE-2018-17439 fixed in no fix yet
- Low CVE-2019-8396 fixed in no fix yet
- Low CVE-2019-8397 fixed in no fix yet
- Low CVE-2019-8398 fixed in no fix yet
- Low CVE-2019-9151 fixed in no fix yet
- Low CVE-2019-9152 fixed in no fix yet
- and 79 more
Low 5 known vulnerabilities in openldap@2.4.57%2Bdfsg-3%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
No fixed version of openldap is available yet. Check whether postgis/postgis:14-3.2 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 5 known vulnerabilities in pcre3@2%3A8.39-13 (postgis/postgis:14-3.2)
How to fix
No fixed version of pcre3 is available yet. Check whether postgis/postgis:14-3.2 needs pcre3 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-11164 fixed in no fix yet
- Low CVE-2017-16231 fixed in no fix yet
- Low CVE-2017-7245 fixed in no fix yet
- Low CVE-2017-7246 fixed in no fix yet
- Low CVE-2019-20838 fixed in no fix yet
Low 4 known vulnerabilities in libsepol@3.1-1 (postgis/postgis:14-3.2)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in postgis/postgis:14-3.2. 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-1+deb11u1); 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 3.1-1+deb11u1
- Low CVE-2021-36085 fixed in 3.1-1+deb11u1
- Low CVE-2021-36086 fixed in 3.1-1+deb11u1
- Low CVE-2021-36087 fixed in 3.1-1+deb11u1
Low 3 known vulnerabilities in util-linux@2.36.1-8%2Bdeb11u1 (postgis/postgis:14-3.2)
How to fix
No fixed version of util-linux is available yet. Check whether postgis/postgis:14-3.2 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 CVE-2024-28085 fixed in 2.36.1-8+deb11u2
Low 2 known vulnerabilities in lcms2@2.12~rc1-2 (postgis/postgis:14-3.2)
How to fix
No fixed version of lcms2 is available yet. Check whether postgis/postgis:14-3.2 needs lcms2 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-29069 fixed in no fix yet
- Low CVE-2025-29070 fixed in no fix yet
Low 2 known vulnerabilities in libgcrypt20@1.8.7-6 (postgis/postgis:14-3.2)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether postgis/postgis:14-3.2 needs libgcrypt20 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2018-6829 fixed in no fix yet
- Low CVE-2024-2236 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (orientdb:3.2)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether orientdb:3.2 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-2024-2236 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (orientdb:3.2)
How to fix
No fixed version of shadow is available yet. Check whether orientdb:3.2 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-2024-56433 fixed in no fix yet
Low 1 known vulnerability in apt@2.2.4 (postgis/postgis:14-3.2)
How to fix
No fixed version of apt is available yet. Check whether postgis/postgis:14-3.2 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 gcc-10@10.2.1-6 (postgis/postgis:14-3.2)
How to fix
No fixed version of gcc-10 is available yet. Check whether postgis/postgis:14-3.2 needs gcc-10 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-4039 fixed in no fix yet
Low 1 known vulnerability in gcc-9@9.3.0-22 (postgis/postgis:14-3.2)
How to fix
No fixed version of gcc-9 is available yet. Check whether postgis/postgis:14-3.2 needs gcc-9 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-4039 fixed in no fix yet
Low 1 known vulnerability in jbigkit@2.1-3.1 (postgis/postgis:14-3.2)
How to fix
No fixed version of jbigkit is available yet. Check whether postgis/postgis:14-3.2 needs jbigkit 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-9937 fixed in no fix yet
Low 1 known vulnerability in unixodbc@2.3.6-0.1 (postgis/postgis:14-3.2)
How to fix
No fixed version of unixodbc is available yet. Check whether postgis/postgis:14-3.2 needs unixodbc 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-1013 fixed in no fix yet
Low 1 known vulnerability in commons-configuration@1.9 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of commons-configuration is available yet. Check whether terraframe/geoprism-registry:latest needs commons-configuration 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-46392 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether terraframe/geoprism-registry:latest 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-2024-2236 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (terraframe/geoprism-registry:latest)
How to fix
No fixed version of shadow is available yet. Check whether terraframe/geoprism-registry:latest 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-2024-56433 fixed in no fix yet
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 2 Apr 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.