Repository scan
openboxes
openboxes/openboxes · branch master · scanned 21 May 2026
High 163
High 98 known vulnerabilities in stdlib@1.18.2 (mysql:5.7)
How to fix
Update stdlib from 1.18.2 to 1.19.9 or later in mysql:5.7. 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 78 more
High 11 known vulnerabilities in cryptography@3.2.1 (mysql:5.7)
How to fix
Update cryptography from 3.2.1 to 39.0.1 or later in mysql:5.7. 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 39.0.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-0286 fixed in 39.0.1
- High CVE-2026-26007 fixed in 46.0.5
- High CVE-2023-50782 fixed in 42.0.0
- High CVE-2020-36242 fixed in 3.3.2
- Medium CVE-2024-0727 fixed in 42.0.2
- Medium CVE-2023-49083 fixed in 41.0.6
- Medium CVE-2023-23931 fixed in 39.0.1
- Low GHSA-5cpq-8wj7-hf2v fixed in 41.0.0
- Low GHSA-jm77-qphf-c4w8 fixed in 41.0.3
- Low GHSA-v8gr-m533-ghj9 fixed in 41.0.4
- Low CVE-2026-34073 fixed in 46.0.6
High 10 known vulnerabilities in tomcat-catalina@7.0.109 (tomcat:7)
How to fix
Update tomcat-catalina from 7.0.109 to 9.0.118 or later in tomcat:7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.118); 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-42498 fixed in 9.0.118
- High CVE-2026-41284 fixed in 9.0.118
- High CVE-2026-43513 fixed in 9.0.118
- High CVE-2026-43515 fixed in 9.0.118
- High CVE-2024-52316 fixed in 9.0.96
- High CVE-2026-41293 fixed in 9.0.118
- High CVE-2026-43512 fixed in 9.0.118
- Medium CVE-2025-66614 fixed in 9.0.112
- Low CVE-2026-24733 fixed in 9.0.112
- Low CVE-2026-43514 fixed in 9.0.118
High 9 known vulnerabilities in runc@1.1.0 (mysql:5.7)
How to fix
Update runc from 1.1.0 to 1.1.5 or later in mysql:5.7. 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-2023-28642 fixed in 1.1.5
- Low CVE-2023-25809 fixed in 1.1.5
High 7 known vulnerabilities in libxml2@2.9.1-6.0.3.el7_9.6 (mysql:5.7)
How to fix
Update libxml2 from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.5.el7_9.6 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.9.1-6.0.5.el7_9.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
- High CVE-2024-56171 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-24928 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
- Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 7 known vulnerabilities in libxml2-python@2.9.1-6.0.3.el7_9.6 (mysql:5.7)
How to fix
Update libxml2-python from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.5.el7_9.6 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.9.1-6.0.5.el7_9.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
- High CVE-2024-56171 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-24928 fixed in 0:2.9.1-6.0.5.el7_9.6
- High CVE-2025-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
- High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
- Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 4 known vulnerabilities in krb5-libs@1.15.1-55.0.1.el7_9 (mysql:5.7)
How to fix
Update krb5-libs from 1.15.1-55.0.1.el7_9 to 0:1.15.1-55.0.7.el7_9 or later in mysql:5.7. 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:1.15.1-55.0.7.el7_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-2024-3596 fixed in 0:1.15.1-55.0.7.el7_9
- Medium CVE-2024-37370 fixed in 0:1.15.1-55.0.3.el7_9
- Medium CVE-2024-37371 fixed in 0:1.15.1-55.0.3.el7_9
- Medium CVE-2025-24528 fixed in 0:1.15.1-55.0.9.el7_9
High 4 known vulnerabilities in python@2.7.5-94.0.1.el7_9 (mysql:5.7)
How to fix
Update python from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.7.5-94.0.7.el7_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-2026-4519 fixed in 0:2.7.5-94.0.7.el7_9
- Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
- Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
- Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 4 known vulnerabilities in python-libs@2.7.5-94.0.1.el7_9 (mysql:5.7)
How to fix
Update python-libs from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.7.5-94.0.7.el7_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-2026-4519 fixed in 0:2.7.5-94.0.7.el7_9
- Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
- Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
- Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 3 known vulnerabilities in setuptools@58.1.0 (mysql:5.7)
How to fix
Update setuptools from 58.1.0 to 70.0.0 or later in mysql:5.7. 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 70.0.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-2024-6345 fixed in 70.0.0
- High CVE-2025-47273 fixed in 78.1.1
- High CVE-2022-40897 fixed in 65.5.1
High 1 known vulnerability in gnupg2@2.0.22-5.el7_5 (mysql:5.7)
How to fix
Update gnupg2 from 2.0.22-5.el7_5 to 0:2.0.22-5.0.1.el7_5 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.0.22-5.0.1.el7_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-2025-68973 fixed in 0:2.0.22-5.0.1.el7_5
High 1 known vulnerability in sqlite@3.7.17-8.el7_7.1 (mysql:5.7)
How to fix
Update sqlite from 3.7.17-8.el7_7.1 to 0:3.7.17-8.0.1.el7_9.1 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:3.7.17-8.0.1.el7_9.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-6965 fixed in 0:3.7.17-8.0.1.el7_9.1
High 1 known vulnerability in zlib@1.2.7-21.el7_9 (mysql:5.7)
How to fix
Update zlib from 1.2.7-21.el7_9 to 0:1.2.7-21.0.1.el7_9 or later in mysql:5.7. 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:1.2.7-21.0.1.el7_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-2016-9840 fixed in 0:1.2.7-21.0.1.el7_9
High 1 known vulnerability in tomcat-coyote@7.0.109 (tomcat:7)
How to fix
Update tomcat-coyote from 7.0.109 to 9.0.116 or later in tomcat:7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.116); 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-24880 fixed in 9.0.116
High 1 known vulnerability in tomcat-tribes@7.0.109 (tomcat:7)
How to fix
No fixed version of tomcat-tribes is available yet. Check whether tomcat:7 needs tomcat-tribes 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-29146 fixed in no fix yet
High 1 known vulnerability in tomcat-util@7.0.109 (tomcat:7)
How to fix
No fixed version of tomcat-util is available yet. Check whether tomcat:7 needs tomcat-util at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2024-38286 fixed in no fix yet
Medium 17
Medium 5 known vulnerabilities in pip@23.0.1 (mysql:5.7)
How to fix
Update pip from 23.0.1 to 26.1 or later in mysql:5.7. 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 26.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-3219 fixed in 26.1
- Medium CVE-2026-6357 fixed in 26.1
- Medium CVE-2025-8869 fixed in 25.3
- Medium CVE-2023-5752 fixed in 23.3
- Low CVE-2026-1703 fixed in 26.0
Medium 2 known vulnerabilities in paramiko@2.11.0 (mysql:5.7)
How to fix
Update paramiko from 2.11.0 to 3.4.0 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.4.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-2023-48795 fixed in 3.4.0
- Low CVE-2026-44405 fixed in no fix yet
Medium 1 known vulnerability in e2fsprogs@1.42.9-19.0.1.el7 (mysql:5.7)
How to fix
Update e2fsprogs from 1.42.9-19.0.1.el7 to 0:1.45.4-3.0.7.el7 or later in mysql:5.7. 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:1.45.4-3.0.7.el7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-1304 fixed in 0:1.45.4-3.0.7.el7
Medium 1 known vulnerability in gcc@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update gcc from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. 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:4.8.5-45.0.1.el7_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
- Medium CVE-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in glib2@2.56.1-9.el7_9 (mysql:5.7)
How to fix
Update glib2 from 2.56.1-9.el7_9 to 0:2.56.1-9.0.3.el7_9 or later in mysql:5.7. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0:2.56.1-9.0.3.el7_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
- Medium CVE-2025-13601 fixed in 0:2.56.1-9.0.3.el7_9
Medium 1 known vulnerability in libcom_err@1.42.9-19.0.1.el7 (mysql:5.7)
How to fix
Update libcom_err from 1.42.9-19.0.1.el7 to 0:1.45.4-3.0.7.el7 or later in mysql:5.7. 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:1.45.4-3.0.7.el7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-1304 fixed in 0:1.45.4-3.0.7.el7
Medium 1 known vulnerability in libgcc@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update libgcc from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. 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:4.8.5-45.0.1.el7_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
- Medium CVE-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in libstdc%2B%2B@4.8.5-44.0.3.el7 (mysql:5.7)
How to fix
Update libstdc%2B%2B from 4.8.5-44.0.3.el7 to 0:4.8.5-45.0.1.el7_9 or later in mysql:5.7. 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:4.8.5-45.0.1.el7_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
- Medium CVE-2020-11023 fixed in 0:4.8.5-45.0.1.el7_9
Medium 1 known vulnerability in openssl@1%3A1.0.2k-26.el7_9 (mysql:5.7)
How to fix
Update openssl from 1%3A1.0.2k-26.el7_9 to 1:1.0.2k-26.0.1.el7_9 or later in mysql:5.7. 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.0.2k-26.0.1.el7_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
- Medium CVE-2025-9230 fixed in 1:1.0.2k-26.0.1.el7_9
Medium 1 known vulnerability in openssl-libs@1%3A1.0.2k-26.el7_9 (mysql:5.7)
How to fix
Update openssl-libs from 1%3A1.0.2k-26.el7_9 to 1:1.0.2k-26.0.1.el7_9 or later in mysql:5.7. 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.0.2k-26.0.1.el7_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
- Medium CVE-2025-9230 fixed in 1:1.0.2k-26.0.1.el7_9
Medium 1 known vulnerability in pynacl@1.4.0 (mysql:5.7)
How to fix
Update pynacl from 1.4.0 to 1.6.2 or later in mysql:5.7. 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.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-69277 fixed in 1.6.2
Medium 1 known vulnerability in mercurial@4.8.2 (tomcat:7)
How to fix
Update mercurial from 4.8.2 to 4.9 or later in tomcat:7. 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.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
- Medium CVE-2019-3902 fixed in 4.9
Low 2
Low 1 known vulnerability in certifi@2023.7.22 (mysql:5.7)
How to fix
Update certifi from 2023.7.22 to 2024.7.4 or later in mysql:5.7. 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 2024.7.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-39689 fixed in 2024.7.4
Low 1 known vulnerability in pyopenssl@20.0.1 (mysql:5.7)
How to fix
Update pyopenssl from 20.0.1 to 26.0.0 or later in mysql:5.7. 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 26.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-27448 fixed in 26.0.0
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 21 May 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.