Repository scan
kolibri
learningequality/kolibri · branch develop · scanned 24 Apr 2026
High 162
High 90 known vulnerabilities in stdlib@1.18.2 (postgres:12)
How to fix
Update stdlib from 1.18.2 to 1.19.9 or later in postgres:12. 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-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.18.4
- 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.18.3
- High CVE-2022-30630 fixed in 1.18.4
- High CVE-2022-30631 fixed in 1.18.4
- High CVE-2022-30632 fixed in 1.18.4
- High CVE-2022-30633 fixed in 1.18.4
- High CVE-2022-30634 fixed in 1.18.3
- High CVE-2022-30635 fixed in 1.18.4
- High CVE-2022-32189 fixed in 1.18.5
- High CVE-2022-41715 fixed in 1.18.7
- High CVE-2022-41716 fixed in 1.18.8
- High CVE-2022-41720 fixed in 1.18.9
- High CVE-2022-41722 fixed in 1.19.6
- High CVE-2022-41723 fixed in 1.19.6
- High CVE-2022-41724 fixed in 1.19.6
- and 70 more
High 19 known vulnerabilities in openssl@3.0.15-1~deb12u1 (postgres:12)
How to fix
Update openssl from 3.0.15-1~deb12u1 to 3.0.18-1~deb12u2 or later in postgres:12. 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.18-1~deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-69419 fixed in 3.0.18-1~deb12u2
- High CVE-2025-69420 fixed in 3.0.18-1~deb12u2
- High CVE-2025-69421 fixed in 3.0.18-1~deb12u2
- High CVE-2025-9230 fixed in 3.0.17-1~deb12u3
- High CVE-2026-28388 fixed in 3.0.19-1~deb12u2
- High CVE-2026-28389 fixed in 3.0.19-1~deb12u2
- High CVE-2026-28390 fixed in 3.0.19-1~deb12u2
- High CVE-2026-28387 fixed in 3.0.19-1~deb12u2
- High CVE-2026-31789 fixed in 3.0.19-1~deb12u2
- Medium CVE-2025-69418 fixed in 3.0.18-1~deb12u2
- Medium CVE-2024-13176 fixed in 3.0.16-1~deb12u1
- Medium CVE-2025-68160 fixed in 3.0.18-1~deb12u2
- Medium CVE-2026-22796 fixed in 3.0.18-1~deb12u2
- Medium CVE-2026-22795 fixed in 3.0.18-1~deb12u2
- Low CVE-2010-0928 fixed in no fix yet
- Low CVE-2025-15467 fixed in 3.0.18-1~deb12u2
- Low CVE-2025-27587 fixed in no fix yet
- Low CVE-2025-9232 fixed in 3.0.17-1~deb12u3
- Low CVE-2026-31790 fixed in 3.0.19-1~deb12u2
High 18 known vulnerabilities in libxml2@2.9.14%2Bdfsg-1.3~deb12u1 (postgres:12)
How to fix
Update libxml2 from 2.9.14%2Bdfsg-1.3~deb12u1 to 2.9.14+dfsg-1.3~deb12u2 or later in postgres:12. 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.14+dfsg-1.3~deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-25062 fixed in 2.9.14+dfsg-1.3~deb12u2
- High CVE-2025-6021 fixed in 2.9.14+dfsg-1.3~deb12u3
- High CVE-2024-56171 fixed in 2.9.14+dfsg-1.3~deb12u2
- High CVE-2025-24928 fixed in 2.9.14+dfsg-1.3~deb12u2
- High CVE-2022-49043 fixed in 2.9.14+dfsg-1.3~deb12u2
- High CVE-2025-49794 fixed in 2.9.14+dfsg-1.3~deb12u3
- High CVE-2025-49796 fixed in 2.9.14+dfsg-1.3~deb12u3
- Medium CVE-2025-32414 fixed in 2.9.14+dfsg-1.3~deb12u2
- Medium CVE-2025-9714 fixed in 2.9.14+dfsg-1.3~deb12u5
- Medium CVE-2023-39615 fixed in 2.9.14+dfsg-1.3~deb12u2
- Medium CVE-2023-45322 fixed in 2.9.14+dfsg-1.3~deb12u2
- Medium CVE-2026-6732 fixed in no fix yet
- Low CVE-2024-34459 fixed in 2.9.14+dfsg-1.3~deb12u2
- Low CVE-2025-6170 fixed in 2.9.14+dfsg-1.3~deb12u3
- Low CVE-2025-8732 fixed in no fix yet
- Low CVE-2026-1757 fixed in no fix yet
- Low CVE-2025-27113 fixed in 2.9.14+dfsg-1.3~deb12u2
- Low CVE-2025-32415 fixed in 2.9.14+dfsg-1.3~deb12u2
High 10 known vulnerabilities in glibc@2.36-9%2Bdeb12u9 (postgres:12)
How to fix
Update glibc from 2.36-9%2Bdeb12u9 to 2.36-9+deb12u11 or later in postgres:12. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.36-9+deb12u11); 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-4802 fixed in 2.36-9+deb12u11
- Medium CVE-2025-8058 fixed in 2.36-9+deb12u13
- Medium CVE-2025-0395 fixed in 2.36-9+deb12u10
- 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 6 known vulnerabilities in krb5@1.20.1-2%2Bdeb12u2 (postgres:12)
How to fix
Update krb5 from 1.20.1-2%2Bdeb12u2 to 1.20.1-2+deb12u3 or later in postgres:12. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.20.1-2+deb12u3); 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.20.1-2+deb12u3
- Medium CVE-2025-3576 fixed in 1.20.1-2+deb12u4
- Low CVE-2018-5709 fixed in no fix yet
- Low CVE-2024-26458 fixed in no fix yet
- Low CVE-2024-26461 fixed in no fix yet
- Low CVE-2024-26462 fixed in 1.20.1-2+deb12u3
High 5 known vulnerabilities in libxslt@1.1.35-1 (postgres:12)
How to fix
Update libxslt from 1.1.35-1 to 1.1.35-1+deb12u2 or later in postgres:12. 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.35-1+deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-7424 fixed in 1.1.35-1+deb12u2
- High CVE-2024-55549 fixed in 1.1.35-1+deb12u1
- High CVE-2025-24855 fixed in 1.1.35-1+deb12u1
- Low CVE-2015-9019 fixed in no fix yet
- Low CVE-2023-40403 fixed in 1.1.35-1+deb12u2
High 5 known vulnerabilities in perl@5.36.0-7%2Bdeb12u1 (postgres:12)
How to fix
Update perl from 5.36.0-7%2Bdeb12u1 to 5.36.0-7+deb12u3 or later in postgres:12. 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.36.0-7+deb12u3); 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-31484 fixed in 5.36.0-7+deb12u3
- Medium CVE-2025-40909 fixed in 5.36.0-7+deb12u3
- Low CVE-2011-4116 fixed in no fix yet
- Low CVE-2023-31486 fixed in no fix yet
- Low CVE-2024-56406 fixed in 5.36.0-7+deb12u2
High 4 known vulnerabilities in sqlite3@3.40.1-2%2Bdeb12u1 (postgres:12)
How to fix
Update sqlite3 from 3.40.1-2%2Bdeb12u1 to 3.40.1-2+deb12u2 or later in postgres:12. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.40.1-2+deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-6965 fixed in 3.40.1-2+deb12u2
- Low CVE-2021-45346 fixed in no fix yet
- Low CVE-2025-29088 fixed in no fix yet
- Low CVE-2025-70873 fixed in no fix yet
High 2 known vulnerabilities in gnupg2@2.2.40-1.1 (postgres:12)
How to fix
Update gnupg2 from 2.2.40-1.1 to 2.2.40-1.1+deb12u2 or later in postgres:12. 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.40-1.1+deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-68973 fixed in 2.2.40-1.1+deb12u2
- Low CVE-2022-3219 fixed in no fix yet
High 2 known vulnerabilities in pam@1.5.2-6%2Bdeb12u1 (postgres:12)
How to fix
Update pam from 1.5.2-6%2Bdeb12u1 to 1.5.2-6+deb12u2 or later in postgres:12. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.5.2-6+deb12u2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-6020 fixed in 1.5.2-6+deb12u2
- Medium CVE-2024-22365 fixed in 1.5.2-6+deb12u2
High 1 known vulnerability in icu@72.1-3 (postgres:12)
How to fix
Update icu from 72.1-3 to 72.1-3+deb12u1 or later in postgres:12. 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 72.1-3+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-5222 fixed in 72.1-3+deb12u1
Medium 23
Medium 8 known vulnerabilities in gnutls28@3.7.9-2%2Bdeb12u3 (postgres:12)
How to fix
Update gnutls28 from 3.7.9-2%2Bdeb12u3 to 3.7.9-2+deb12u6 or later in postgres:12. 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.9-2+deb12u6); 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-9820 fixed in 3.7.9-2+deb12u6
- Medium CVE-2024-12243 fixed in 3.7.9-2+deb12u4
- Medium CVE-2025-14831 fixed in 3.7.9-2+deb12u6
- Medium CVE-2025-32988 fixed in 3.7.9-2+deb12u5
- Medium CVE-2025-32990 fixed in 3.7.9-2+deb12u5
- Medium CVE-2025-6395 fixed in 3.7.9-2+deb12u5
- Low CVE-2011-3389 fixed in no fix yet
- Low CVE-2025-32989 fixed in 3.7.9-2+deb12u5
Medium 5 known vulnerabilities in systemd@252.33-1~deb12u1 (postgres:12)
How to fix
Update systemd from 252.33-1~deb12u1 to 252.38-1~deb12u1 or later in postgres:12. 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 252.38-1~deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-4598 fixed in 252.38-1~deb12u1
- 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
Medium 3 known vulnerabilities in libgcrypt20@1.10.1-3 (postgres:12)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether postgres:12 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
- Medium CVE-2026-41989 fixed in no fix yet
- Low CVE-2018-6829 fixed in no fix yet
- Low CVE-2024-2236 fixed in no fix yet
Medium 3 known vulnerabilities in shadow@1%3A4.13%2Bdfsg1-1 (postgres:12)
How to fix
Update shadow from 1%3A4.13%2Bdfsg1-1 to 1:4.13+dfsg1-1+deb12u1 or later in postgres:12. 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.13+dfsg1-1+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-4641 fixed in 1:4.13+dfsg1-1+deb12u1
- Low CVE-2007-5686 fixed in no fix yet
- Low CVE-2023-29383 fixed in 1:4.13+dfsg1-1+deb12u1
Medium 2 known vulnerabilities in tar@1.34%2Bdfsg-1.2%2Bdeb12u1 (postgres:12)
How to fix
No fixed version of tar is available yet. Check whether postgres:12 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 1 known vulnerability in libcap2@1%3A2.66-4 (postgres:12)
How to fix
Update libcap2 from 1%3A2.66-4 to 1:2.66-4+deb12u1 or later in postgres:12. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1:2.66-4+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-1390 fixed in 1:2.66-4+deb12u1
Medium 1 known vulnerability in libtasn1-6@4.19.0-2 (postgres:12)
How to fix
Update libtasn1-6 from 4.19.0-2 to 4.19.0-2+deb12u1 or later in postgres:12. 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-2+deb12u1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-12133 fixed in 4.19.0-2+deb12u1
Low 14
Low 5 known vulnerabilities in openldap@2.5.13%2Bdfsg-5 (postgres:12)
How to fix
No fixed version of openldap is available yet. Check whether postgres:12 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 2 known vulnerabilities in coreutils@9.1-1 (postgres:12)
How to fix
No fixed version of coreutils is available yet. Check whether postgres:12 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 gcc-12@12.2.0-14 (postgres:12)
How to fix
No fixed version of gcc-12 is available yet. Check whether postgres:12 needs gcc-12 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2022-27943 fixed in no fix yet
- Low CVE-2023-4039 fixed in 12.2.0-14+deb12u1
Low 2 known vulnerabilities in util-linux@2.38.1-5%2Bdeb12u3 (postgres:12)
How to fix
No fixed version of util-linux is available yet. Check whether postgres:12 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 1 known vulnerability in apt@2.6.1 (postgres:12)
How to fix
No fixed version of apt is available yet. Check whether postgres:12 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 llvm-toolchain-16@1%3A16.0.6-15~deb12u1 (postgres:12)
How to fix
No fixed version of llvm-toolchain-16 is available yet. Check whether postgres:12 needs llvm-toolchain-16 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-31852 fixed in no fix yet
Low 1 known vulnerability in xz-utils@5.4.1-0.2 (postgres:12)
How to fix
Update xz-utils from 5.4.1-0.2 to 5.4.1-1 or later in postgres:12. 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.1-1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2025-31115 fixed in 5.4.1-1
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 24 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.