Repository scan
farmOS
farmOS/farmOS · branch 7.x-1.x · scanned 24 Apr 2026
High 417
High 82 known vulnerabilities in curl@7.74.0-1.3%2Bb1 (farmos/farmos:7.x-1.8)
How to fix
Update curl from 7.74.0-1.3%2Bb1 to 7.74.0-1.3+deb11u2 or later in farmos/farmos:7.x-1.8. 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+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-2021-22946 fixed in 7.74.0-1.3+deb11u2
- High CVE-2021-22946 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27775 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27775 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27781 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27781 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27782 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-27782 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-22576 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-22576 fixed in 7.74.0-1.3+deb11u2
- High CVE-2024-2398 fixed in 7.74.0-1.3+deb11u12
- 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-27533 fixed in 7.74.0-1.3+deb11u8
- High CVE-2023-27534 fixed in 7.74.0-1.3+deb11u8
- High CVE-2023-27534 fixed in 7.74.0-1.3+deb11u8
- High CVE-2021-22945 fixed in 7.74.0-1.3+deb11u2
- High CVE-2021-22945 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-32207 fixed in 7.74.0-1.3+deb11u2
- High CVE-2022-32207 fixed in 7.74.0-1.3+deb11u2
- and 62 more
High 47 known vulnerabilities in apache-htcacheclean@.service (farmos/farmos:7.x-1.8)
How to fix
Update apache-htcacheclean from .service to 2.4.59-1~deb11u1 or later in farmos/farmos:7.x-1.8. 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.59-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-2023-38709 fixed in 2.4.59-1~deb11u1
- High CVE-2025-49812 fixed in 2.4.65-1~deb11u1
- High CVE-2006-20001 fixed in 2.4.56-1~deb11u1
- High CVE-2022-22719 fixed in 2.4.53-1~deb11u1
- High CVE-2022-26377 fixed in 2.4.54-1~deb11u1
- High CVE-2022-29404 fixed in 2.4.54-1~deb11u1
- High CVE-2022-30522 fixed in 2.4.54-1~deb11u1
- High CVE-2022-30556 fixed in 2.4.54-1~deb11u1
- High CVE-2023-27522 fixed in 2.4.56-1~deb11u1
- High CVE-2023-31122 fixed in 2.4.59-1~deb11u1
- High CVE-2023-43622 fixed in 2.4.59-1~deb11u1
- High CVE-2024-27316 fixed in 2.4.59-1~deb11u1
- High CVE-2024-38477 fixed in 2.4.61-1~deb11u1
- High CVE-2024-39573 fixed in 2.4.61-1~deb11u1
- High CVE-2024-42516 fixed in 2.4.65-1~deb11u1
- High CVE-2024-43204 fixed in 2.4.65-1~deb11u1
- High CVE-2024-47252 fixed in 2.4.65-1~deb11u1
- High CVE-2025-49630 fixed in 2.4.65-1~deb11u1
- High CVE-2025-53020 fixed in 2.4.65-1~deb11u1
- High CVE-2025-55753 fixed in 2.4.66-1~deb11u1
- and 27 more
High 36 known vulnerabilities in openssl@1.1.1k-1%2Bdeb11u1 (farmos/farmos:7.x-1.8)
How to fix
Update openssl from 1.1.1k-1%2Bdeb11u1 to 1.1.1n-0+deb11u4 or later in farmos/farmos:7.x-1.8. 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-2022-1292 fixed in 1.1.1n-0+deb11u2
- High CVE-2022-2068 fixed in 1.1.1n-0+deb11u3
- High CVE-2025-69419 fixed in 1.1.1w-0+deb11u5
- High CVE-2022-0778 fixed in 1.1.1k-1+deb11u2
- 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-2026-28388 fixed in no fix yet
- High CVE-2026-28389 fixed in no fix yet
- High CVE-2026-28390 fixed in no fix yet
- High CVE-2026-28387 fixed in no fix yet
- High CVE-2024-5535 fixed in 1.1.1w-0+deb11u2
- High CVE-2026-31789 fixed in no fix yet
- 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
- and 16 more
High 26 known vulnerabilities in libxml2@2.9.10%2Bdfsg-6.7 (farmos/farmos:7.x-1.8)
How to fix
Update libxml2 from 2.9.10%2Bdfsg-6.7 to 2.9.10+dfsg-6.7+deb11u5 or later in farmos/farmos:7.x-1.8. 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-23308 fixed in 2.9.10+dfsg-6.7+deb11u1
- 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-2022-29824 fixed in 2.9.10+dfsg-6.7+deb11u2
- 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
- Medium CVE-2026-6732 fixed in no fix yet
- and 6 more
High 26 known vulnerabilities in postgresql-13@13.5-0%2Bdeb11u1 (farmos/farmos:7.x-1.8)
How to fix
Update postgresql-13 from 13.5-0%2Bdeb11u1 to 13.11-0+deb11u1 or later in farmos/farmos:7.x-1.8. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 13.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-2023-2454 fixed in 13.11-0+deb11u1
- High CVE-2023-39417 fixed in 13.13-0+deb11u1
- High CVE-2022-2625 fixed in 13.8-0+deb11u1
- High CVE-2024-0985 fixed in 13.14-0+deb11u1
- High CVE-2025-1094 fixed in 13.20-0+deb11u1
- High CVE-2022-1552 fixed in 13.7-0+deb11u1
- High CVE-2023-5869 fixed in 13.13-0+deb11u1
- High CVE-2024-10979 fixed in 13.17-0+deb11u1
- High CVE-2024-7348 fixed in 13.16-0+deb11u1
- High CVE-2025-8714 fixed in 13.22-0+deb11u1
- High CVE-2025-8715 fixed in 13.22-0+deb11u1
- High CVE-2026-2004 fixed in 13.23-0+deb11u2
- High CVE-2026-2005 fixed in 13.23-0+deb11u2
- High CVE-2026-2006 fixed in 13.23-0+deb11u2
- Medium CVE-2024-10976 fixed in 13.17-0+deb11u1
- Medium CVE-2024-10978 fixed in 13.17-0+deb11u1
- Medium CVE-2023-5868 fixed in 13.13-0+deb11u1
- Medium CVE-2026-2003 fixed in 13.23-0+deb11u2
- Medium CVE-2023-2455 fixed in 13.11-0+deb11u1
- Medium CVE-2025-12818 fixed in 13.23-0+deb11u1
- and 6 more
High 25 known vulnerabilities in expat@2.2.10-2 (farmos/farmos:7.x-1.8)
How to fix
Update expat from 2.2.10-2 to 2.2.10-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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+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-23990 fixed in 2.2.10-2+deb11u1
- High CVE-2022-25314 fixed in 2.2.10-2+deb11u2
- 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-2021-46143 fixed in 2.2.10-2+deb11u1
- High CVE-2022-40674 fixed in 2.2.10-2+deb11u4
- High CVE-2021-45960 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22825 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22826 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22827 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22822 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22823 fixed in 2.2.10-2+deb11u1
- High CVE-2022-22824 fixed in 2.2.10-2+deb11u1
- High CVE-2022-23852 fixed in 2.2.10-2+deb11u1
- High CVE-2022-25235 fixed in 2.2.10-2+deb11u2
- High CVE-2022-25236 fixed in 2.2.10-2+deb11u2
- High CVE-2022-25315 fixed in 2.2.10-2+deb11u2
- High CVE-2024-45491 fixed in 2.2.10-2+deb11u6
- High CVE-2024-45492 fixed in 2.2.10-2+deb11u6
- and 5 more
High 25 known vulnerabilities in stdlib@1.24.6 (mariadb:latest)
How to fix
Update stdlib from 1.24.6 to 1.24.9 or later in mariadb: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.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-2025-68121 fixed in 1.24.13
- Medium CVE-2025-58183 fixed in 1.24.8
- Medium CVE-2025-47912 fixed in 1.24.8
- Medium CVE-2025-58185 fixed in 1.24.8
- Medium CVE-2025-58186 fixed in 1.24.8
- Medium CVE-2025-58189 fixed in 1.24.8
- Medium CVE-2025-61724 fixed in 1.24.8
- Medium CVE-2025-61730 fixed in 1.24.12
- Medium CVE-2026-32288 fixed in 1.25.9
- Medium CVE-2026-27142 fixed in 1.25.8
- and 5 more
High 23 known vulnerabilities in glibc@2.31-13%2Bdeb11u2 (farmos/farmos:7.x-1.8)
How to fix
Update glibc from 2.31-13%2Bdeb11u2 to 2.31-13+deb11u9 or later in farmos/farmos:7.x-1.8. 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-2026-5928 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
- High CVE-2021-33574 fixed in 2.31-13+deb11u3
- High CVE-2022-23218 fixed in 2.31-13+deb11u3
- High CVE-2022-23219 fixed in 2.31-13+deb11u3
- High CVE-2026-5450 fixed in no fix yet
- 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
- and 3 more
High 16 known vulnerabilities in glib2.0@2.66.8-1 (farmos/farmos:7.x-1.8)
How to fix
Update glib2.0 from 2.66.8-1 to 2.66.8-1+deb11u7 or later in farmos/farmos:7.x-1.8. 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.66.8-1+deb11u7); 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-13601 fixed in 2.66.8-1+deb11u7
- High CVE-2024-52533 fixed in 2.66.8-1+deb11u5
- Medium CVE-2026-1484 fixed in 2.66.8-1+deb11u8
- Medium CVE-2025-4373 fixed in 2.66.8-1+deb11u7
- Medium CVE-2024-34397 fixed in 2.66.8-1+deb11u2
- Medium CVE-2026-1489 fixed in 2.66.8-1+deb11u8
- Medium CVE-2023-29499 fixed in 2.66.8-1+deb11u1
- Medium CVE-2023-32611 fixed in 2.66.8-1+deb11u1
- Medium CVE-2023-32665 fixed in 2.66.8-1+deb11u1
- Medium CVE-2025-14087 fixed in 2.66.8-1+deb11u7
- Medium CVE-2025-14512 fixed in 2.66.8-1+deb11u7
- Low CVE-2012-0039 fixed in no fix yet
- Low CVE-2026-1485 fixed in 2.66.8-1+deb11u8
- Low CVE-2025-3360 fixed in 2.66.8-1+deb11u6
- Low CVE-2025-7039 fixed in 2.66.8-1+deb11u7
- Low CVE-2026-0988 fixed in 2.66.8-1+deb11u8
High 16 known vulnerabilities in systemd@247.3-6 (farmos/farmos:7.x-1.8)
How to fix
Update systemd from 247.3-6 to 247.3-7+deb11u6 or later in farmos/farmos:7.x-1.8. 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-2021-3997 fixed in 247.3-7
- 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 247.3-7+deb11u8
- Medium CVE-2023-7008 fixed in 247.3-7+deb11u6
- Medium CVE-2026-40225 fixed in 247.3-7+deb11u8
- Medium CVE-2026-40226 fixed in 247.3-7+deb11u8
- Medium CVE-2026-4105 fixed in 247.3-7+deb11u8
- 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 15 known vulnerabilities in gnutls28@3.7.1-5 (farmos/farmos:7.x-1.8)
How to fix
Update gnutls28 from 3.7.1-5 to 3.7.1-5+deb11u3 or later in farmos/farmos:7.x-1.8. 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-2022-2509 fixed in 3.7.1-5+deb11u2
- 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-2021-4209 fixed in 3.7.1-5+deb11u1
- 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 15 known vulnerabilities in libpng1.6@1.6.37-3 (farmos/farmos:7.x-1.8)
How to fix
Update libpng1.6 from 1.6.37-3 to 1.6.37-3+deb11u1 or later in farmos/farmos:7.x-1.8. 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 1.6.37-3+deb11u3
- High CVE-2026-33636 fixed in 1.6.37-3+deb11u3
- High CVE-2026-25646 fixed in 1.6.37-3+deb11u2
- Medium CVE-2026-34757 fixed in no fix yet
- 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 10 known vulnerabilities in php@7.4.27 (farmos/farmos:7.x-1.8)
How to fix
Update php from 7.4.27 to 7.4.32 or later in farmos/farmos:7.x-1.8. 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.4.32); 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-31626 fixed in 7.4.32
- High CVE-2023-0568 fixed in 7.4.33
- High CVE-2023-0662 fixed in 7.4.33
- High CVE-2023-0567 fixed in 7.4.33
- High CVE-2022-31625 fixed in 7.4.32
- High CVE-2021-21708 fixed in 7.4.28
- High CVE-2022-37454 fixed in 7.4.33
- Medium CVE-2022-31629 fixed in 7.4.32
- Medium CVE-2022-31630 fixed in 7.4.33
- Low CVE-2022-31628 fixed in 7.4.32
High 9 known vulnerabilities in krb5@1.18.3-6%2Bdeb11u1 (farmos/farmos:7.x-1.8)
How to fix
Update krb5 from 1.18.3-6%2Bdeb11u1 to 1.18.3-6+deb11u6 or later in farmos/farmos:7.x-1.8. 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 6 known vulnerabilities in openldap@2.4.57%2Bdfsg-3 (farmos/farmos:7.x-1.8)
How to fix
Update openldap from 2.4.57%2Bdfsg-3 to 2.4.57+dfsg-3+deb11u1 or later in farmos/farmos:7.x-1.8. 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.57+dfsg-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-29155 fixed in 2.4.57+dfsg-3+deb11u1
- 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
High 6 known vulnerabilities in perl@5.32.1-4%2Bdeb11u2 (farmos/farmos:7.x-1.8)
How to fix
Update perl from 5.32.1-4%2Bdeb11u2 to 5.32.1-4+deb11u3 or later in farmos/farmos:7.x-1.8. 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
- Medium CVE-2025-40909 fixed in 5.32.1-4+deb11u5
- Low CVE-2011-4116 fixed in no fix yet
- Low CVE-2023-31486 fixed in no fix yet
High 5 known vulnerabilities in freetype@2.10.4%2Bdfsg-1 (farmos/farmos:7.x-1.8)
How to fix
Update freetype from 2.10.4%2Bdfsg-1 to 2.10.4+dfsg-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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+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-27405 fixed in 2.10.4+dfsg-1+deb11u1
- High CVE-2022-27406 fixed in 2.10.4+dfsg-1+deb11u1
- High CVE-2025-27363 fixed in 2.10.4+dfsg-1+deb11u2
- High CVE-2022-27404 fixed in 2.10.4+dfsg-1+deb11u1
- Low CVE-2022-31782 fixed in no fix yet
High 3 known vulnerabilities in gnupg2@2.2.27-2 (farmos/farmos:7.x-1.8)
How to fix
Update gnupg2 from 2.2.27-2 to 2.2.27-2+deb11u3 or later in farmos/farmos:7.x-1.8. 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
- Medium CVE-2022-34903 fixed in 2.2.27-2+deb11u2
- Low CVE-2022-3219 fixed in no fix yet
High 3 known vulnerabilities in nghttp2@1.43.0-1 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of nghttp2 is available yet. Check whether farmos/farmos:7.x-1.8 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 (farmos/farmos:7.x-1.8)
How to fix
Update pcre2 from 10.36-2 to 10.36-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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 libtasn1-6@4.16.0-2 (farmos/farmos:7.x-1.8)
How to fix
Update libtasn1-6 from 4.16.0-2 to 4.16.0-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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 (farmos/farmos:7.x-1.8)
How to fix
Update ncurses from 6.2%2B20201114-2 to 6.2+20201114-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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 (farmos/farmos:7.x-1.8)
How to fix
Update pam from 1.4.0-9%2Bdeb11u1 to 1.4.0-9+deb11u2 or later in farmos/farmos:7.x-1.8. 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 underscore@1.9.1 (farmos/farmos:7.x-1.8)
How to fix
Update underscore from 1.9.1 to 1.13.8 or later in farmos/farmos:7.x-1.8. 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.13.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-27601 fixed in 1.13.8
- High CVE-2021-23358 fixed in 1.12.1
High 2 known vulnerabilities in zlib@1%3A1.2.11.dfsg-2 (farmos/farmos:7.x-1.8)
How to fix
Update zlib from 1%3A1.2.11.dfsg-2 to 1:1.2.11.dfsg-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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-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-2018-25032 fixed in 1:1.2.11.dfsg-2+deb11u1
- High CVE-2022-37434 fixed in 1:1.2.11.dfsg-2+deb11u2
High 1 known vulnerability in apr@1.7.0-6%2Bdeb11u1 (farmos/farmos:7.x-1.8)
How to fix
Update apr from 1.7.0-6%2Bdeb11u1 to 1.7.0-6+deb11u2 or later in farmos/farmos:7.x-1.8. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.7.0-6+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-2022-24963 fixed in 1.7.0-6+deb11u2
High 1 known vulnerability in cyrus-sasl2@2.1.27%2Bdfsg-2.1 (farmos/farmos:7.x-1.8)
How to fix
Update cyrus-sasl2 from 2.1.27%2Bdfsg-2.1 to 2.1.27+dfsg-2.1+deb11u1 or later in farmos/farmos:7.x-1.8. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.1.27+dfsg-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
- High CVE-2022-24407 fixed in 2.1.27+dfsg-2.1+deb11u1
High 1 known vulnerability in dpkg@1.20.9 (farmos/farmos:7.x-1.8)
How to fix
Update dpkg from 1.20.9 to 1.20.10 or later in farmos/farmos:7.x-1.8. 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.10); 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-1664 fixed in 1.20.10
High 1 known vulnerability in e2scrub@.service (farmos/farmos:7.x-1.8)
How to fix
Update e2scrub from .service to 1.46.2-2+deb11u1 or later in farmos/farmos:7.x-1.8. 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 gmp@2%3A6.2.1%2Bdfsg-1 (farmos/farmos:7.x-1.8)
How to fix
Update gmp from 2%3A6.2.1%2Bdfsg-1 to 2:6.2.1+dfsg-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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.2.1+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
- High CVE-2021-43618 fixed in 2:6.2.1+dfsg-1+deb11u1
High 1 known vulnerability in gzip@1.10-4 (farmos/farmos:7.x-1.8)
How to fix
Update gzip from 1.10-4 to 1.10-4+deb11u1 or later in farmos/farmos:7.x-1.8. 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-4+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-1271 fixed in 1.10-4+deb11u1
High 1 known vulnerability in icu@67.1-7 (farmos/farmos:7.x-1.8)
How to fix
Update icu from 67.1-7 to 67.1-7+deb11u1 or later in farmos/farmos:7.x-1.8. 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
High 1 known vulnerability in libssh2@1.9.0-2 (farmos/farmos:7.x-1.8)
How to fix
Update libssh2 from 1.9.0-2 to 1.9.0-2+deb11u1 or later in farmos/farmos:7.x-1.8. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.9.0-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-2020-22218 fixed in 1.9.0-2+deb11u1
High 1 known vulnerability in libtirpc@1.3.1-1 (farmos/farmos:7.x-1.8)
How to fix
Update libtirpc from 1.3.1-1 to 1.3.1-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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.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
- High CVE-2021-46828 fixed in 1.3.1-1+deb11u1
High 1 known vulnerability in xz-utils@5.2.5-2 (farmos/farmos:7.x-1.8)
How to fix
Update xz-utils from 5.2.5-2 to 5.2.5-2.1~deb11u1 or later in farmos/farmos:7.x-1.8. 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.5-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
- High CVE-2022-1271 fixed in 5.2.5-2.1~deb11u1
Medium 35
Medium 7 known vulnerabilities in sqlite3@3.34.1-3 (farmos/farmos:7.x-1.8)
How to fix
Update sqlite3 from 3.34.1-3 to 3.34.1-3+deb11u1 or later in farmos/farmos:7.x-1.8. 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 5 known vulnerabilities in util-linux@2.36.1-8 (farmos/farmos:7.x-1.8)
How to fix
Update util-linux from 2.36.1-8 to 2.36.1-8+deb11u1 or later in farmos/farmos:7.x-1.8. 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.1-8+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-2021-3995 fixed in 2.36.1-8+deb11u1
- Medium CVE-2021-3996 fixed in 2.36.1-8+deb11u1
- 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
Medium 4 known vulnerabilities in shadow@1%3A4.8.1-1 (farmos/farmos:7.x-1.8)
How to fix
Update shadow from 1%3A4.8.1-1 to 1:4.8.1-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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 libgcrypt20@1.8.7-6 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether farmos/farmos:7.x-1.8 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 tar@1.34%2Bdfsg-1 (farmos/farmos:7.x-1.8)
How to fix
Update tar from 1.34%2Bdfsg-1 to 1.34+dfsg-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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 glibc@2.39-0ubuntu8.7 (mariadb:latest)
How to fix
No fixed version of glibc is available yet. Check whether mariadb:latest needs glibc at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2026-4046 fixed in no fix yet
- Medium CVE-2026-4437 fixed in no fix yet
- Medium CVE-2026-4438 fixed in no fix yet
Medium 2 known vulnerabilities in lua5.3@5.3.3-1.1 (farmos/farmos:7.x-1.8)
How to fix
Update lua5.3 from 5.3.3-1.1 to 5.3.3-1.1+deb11u1 or later in farmos/farmos:7.x-1.8. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.3.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
- Medium CVE-2020-24370 fixed in 5.3.3-1.1+deb11u1
- Low CVE-2019-6706 fixed in 5.3.3-1.1+deb11u1
Medium 2 known vulnerabilities in tar@1.35%2Bdfsg-3build1 (mariadb:latest)
How to fix
No fixed version of tar is available yet. Check whether mariadb: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 CVE-2026-5704 fixed in no fix yet
Medium 1 known vulnerability in apr-util@1.6.1-5 (farmos/farmos:7.x-1.8)
How to fix
Update apr-util from 1.6.1-5 to 1.6.1-5+deb11u1 or later in farmos/farmos:7.x-1.8. 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.1-5+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-2022-25147 fixed in 1.6.1-5+deb11u1
Medium 1 known vulnerability in file@1%3A5.39-3 (farmos/farmos:7.x-1.8)
How to fix
Update file from 1%3A5.39-3 to 1:5.39-3+deb11u1 or later in farmos/farmos:7.x-1.8. 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.39-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-2022-48554 fixed in 1:5.39-3+deb11u1
Medium 1 known vulnerability in libsodium@1.0.18-1 (farmos/farmos:7.x-1.8)
How to fix
Update libsodium from 1.0.18-1 to 1.0.18-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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.18-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-2025-69277 fixed in 1.0.18-1+deb11u1
Medium 1 known vulnerability in dpkg@1.22.6ubuntu6.5 (mariadb:latest)
How to fix
No fixed version of dpkg is available yet. Check whether mariadb:latest needs dpkg at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2026-2219 fixed in no fix yet
Medium 1 known vulnerability in libcap2@1%3A2.66-5ubuntu2.2 (mariadb:latest)
How to fix
Update libcap2 from 1%3A2.66-5ubuntu2.2 to 1:2.66-5ubuntu2.4 or later in mariadb:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1:2.66-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-2026-4878 fixed in 1:2.66-5ubuntu2.4
Medium 1 known vulnerability in util-linux@2.39.3-9ubuntu6.5 (mariadb:latest)
How to fix
No fixed version of util-linux is available yet. Check whether mariadb:latest 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
- Medium CVE-2026-27456 fixed in no fix yet
Low 127
Low 96 known vulnerabilities in binutils@2.35.2-2 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of binutils is available yet. Check whether farmos/farmos:7.x-1.8 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
- Low CVE-2017-13716 fixed in no fix yet
- Low CVE-2018-20673 fixed in no fix yet
- Low CVE-2018-20712 fixed in no fix yet
- Low CVE-2018-9996 fixed in no fix yet
- Low CVE-2019-1010204 fixed in no fix yet
- Low CVE-2020-19726 fixed in no fix yet
- Low CVE-2020-35448 fixed in no fix yet
- Low CVE-2021-20197 fixed in no fix yet
- Low CVE-2021-20284 fixed in no fix yet
- Low CVE-2021-32256 fixed in no fix yet
- Low CVE-2021-3487 fixed in no fix yet
- Low CVE-2021-3530 fixed in no fix yet
- Low CVE-2021-3549 fixed in no fix yet
- Low CVE-2021-3826 fixed in no fix yet
- Low CVE-2021-45078 fixed in no fix yet
- Low CVE-2021-46174 fixed in no fix yet
- Low CVE-2021-46195 fixed in no fix yet
- Low CVE-2022-35205 fixed in no fix yet
- Low CVE-2022-35206 fixed in no fix yet
- Low CVE-2022-38533 fixed in no fix yet
- and 76 more
Low 5 known vulnerabilities in pcre3@2%3A8.39-13 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of pcre3 is available yet. Check whether farmos/farmos:7.x-1.8 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 (farmos/farmos:7.x-1.8)
How to fix
Update libsepol from 3.1-1 to 3.1-1+deb11u1 or later in farmos/farmos:7.x-1.8. 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 4 known vulnerabilities in patch@2.7.6-7 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of patch is available yet. Check whether farmos/farmos:7.x-1.8 needs patch 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-4651 fixed in no fix yet
- Low CVE-2018-6951 fixed in no fix yet
- Low CVE-2018-6952 fixed in no fix yet
- Low CVE-2021-45261 fixed in no fix yet
Low 3 known vulnerabilities in re2c@2.0.3-1 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of re2c is available yet. Check whether farmos/farmos:7.x-1.8 needs re2c 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-21232 fixed in no fix yet
- Low CVE-2022-23901 fixed in no fix yet
- Low CVE-2026-2903 fixed in no fix yet
Low 2 known vulnerabilities in coreutils@8.32-4%2Bb1 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of coreutils is available yet. Check whether farmos/farmos:7.x-1.8 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 m4@1.4.18-5 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of m4 is available yet. Check whether farmos/farmos:7.x-1.8 needs m4 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-2008-1687 fixed in no fix yet
- Low CVE-2008-1688 fixed in no fix yet
Low 2 known vulnerabilities in elfutils@0.190-1.1ubuntu0.1 (mariadb:latest)
How to fix
No fixed version of elfutils is available yet. Check whether mariadb:latest needs elfutils 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-1376 fixed in no fix yet
- Low CVE-2025-1352 fixed in no fix yet
Low 1 known vulnerability in apt@2.2.4 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of apt is available yet. Check whether farmos/farmos:7.x-1.8 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 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of gcc-10 is available yet. Check whether farmos/farmos:7.x-1.8 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 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of gcc-9 is available yet. Check whether farmos/farmos:7.x-1.8 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 jansson@2.13.1-1.1 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of jansson is available yet. Check whether farmos/farmos:7.x-1.8 needs jansson 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-2020-36325 fixed in no fix yet
Low 1 known vulnerability in sed@4.7-1 (farmos/farmos:7.x-1.8)
How to fix
No fixed version of sed is available yet. Check whether farmos/farmos:7.x-1.8 needs sed at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2026-5958 fixed in no fix yet
Low 1 known vulnerability in libbpf@1.3.0-2build2 (mariadb:latest)
How to fix
No fixed version of libbpf is available yet. Check whether mariadb:latest needs libbpf 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-29481 fixed in no fix yet
Low 1 known vulnerability in libgcrypt20@1.10.3-2build1 (mariadb:latest)
How to fix
No fixed version of libgcrypt20 is available yet. Check whether mariadb: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 rsync@3.2.7-1ubuntu1.2 (mariadb:latest)
How to fix
No fixed version of rsync is available yet. Check whether mariadb:latest needs rsync at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Low CVE-2026-41035 fixed in no fix yet
Low 1 known vulnerability in shadow@1%3A4.13%2Bdfsg1-4ubuntu3.2 (mariadb:latest)
How to fix
No fixed version of shadow is available yet. Check whether mariadb: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 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.