InfraScan Cloud

Repository scan

SORMAS-Project

SORMAS-Foundation/SORMAS-Project · branch main · scanned 2 Apr 2026

COverall
CSecurity
–Reliability · N/A
ACost
109findings · 0 critical, 44 high
—no cost findings with a savings estimate

High 99

High 30 known vulnerabilities in curl@8.5.0-r0 (hzibraunschweig/sormas-postgres:latest) Security · 30 CVEs

How to fix

Update curl from 8.5.0-r0 to 8.12.0-r0 or later in hzibraunschweig/sormas-postgres: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.12.0-r0); 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-0665 fixed in 8.12.0-r0
  • High CVE-2025-0725 fixed in 8.12.0-r0
  • High CVE-2024-6197 fixed in 8.9.0-r0
  • High CVE-2025-5399 fixed in 8.14.1-r0
  • High CVE-2025-9086 fixed in 8.14.1-r2
  • High CVE-2026-3805 fixed in no fix yet
  • High CVE-2024-2398 fixed in 8.7.1-r0
  • Medium CVE-2024-6874 fixed in 8.9.0-r0
  • Medium CVE-2025-10966 fixed in no fix yet
  • Medium CVE-2025-5025 fixed in 8.14.0-r0
  • Medium CVE-2024-0853 fixed in no fix yet
  • Medium CVE-2025-10148 fixed in 8.14.1-r2
  • Medium CVE-2025-14524 fixed in no fix yet
  • Medium CVE-2025-14819 fixed in no fix yet
  • Medium CVE-2025-15079 fixed in no fix yet
  • Medium CVE-2026-3783 fixed in no fix yet
  • Medium CVE-2025-13034 fixed in no fix yet
  • Medium CVE-2024-2379 fixed in 8.7.1-r0
  • Medium CVE-2025-14017 fixed in no fix yet
  • Medium CVE-2024-2466 fixed in 8.7.1-r0
  • and 10 more
High 13 known vulnerabilities in python3@3.11.9-r0 (hzibraunschweig/sormas-postgres:latest) Security · 13 CVEs

How to fix

Update python3 from 3.11.9-r0 to 3.11.10-r0 or later in hzibraunschweig/sormas-postgres: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.11.10-r0); 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-4032 fixed in 3.11.10-r0
  • High CVE-2024-6232 fixed in 3.11.10-r0
  • High CVE-2024-7592 fixed in 3.11.10-r0
  • High CVE-2025-4138 fixed in 3.11.13-r0
  • High CVE-2025-4330 fixed in 3.11.13-r0
  • High CVE-2024-8088 fixed in 3.11.9-r1
  • High CVE-2025-4517 fixed in 3.11.13-r0
  • Medium CVE-2023-27043 fixed in 3.11.10-r0
  • Medium CVE-2024-12718 fixed in 3.11.13-r0
  • Medium CVE-2024-9287 fixed in 3.11.11-r0
  • Medium CVE-2024-6923 fixed in 3.11.10-r0
  • Medium CVE-2025-4516 fixed in 3.11.12-r1
  • Medium CVE-2025-0938 fixed in 3.11.12-r0
High 12 known vulnerabilities in postgresql16@16.3-r0 (hzibraunschweig/sormas-postgres:latest) Security · 12 CVEs

How to fix

Update postgresql16 from 16.3-r0 to 16.8-r0 or later in hzibraunschweig/sormas-postgres: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 16.8-r0); 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-1094 fixed in 16.8-r0
  • High CVE-2024-10979 fixed in 16.5-r0
  • High CVE-2024-7348 fixed in 16.4-r0
  • High CVE-2025-8714 fixed in 16.10-r0
  • High CVE-2025-8715 fixed in 16.10-r0
  • Medium CVE-2024-10976 fixed in 16.5-r0
  • Medium CVE-2024-10978 fixed in 16.5-r0
  • Medium CVE-2025-12818 fixed in 16.11-r0
  • Medium CVE-2025-4207 fixed in 16.9-r0
  • Low CVE-2024-10977 fixed in 16.5-r0
  • Low CVE-2025-12817 fixed in 16.11-r0
  • Low CVE-2025-8713 fixed in 16.10-r0
High 10 known vulnerabilities in binutils@2.41-r0 (hzibraunschweig/sormas-postgres:latest) Security · 10 CVEs

How to fix

No fixed version of binutils is available yet. Check whether hzibraunschweig/sormas-postgres: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

  • High CVE-2025-69649 fixed in no fix yet
  • High CVE-2025-69650 fixed in no fix yet
  • Medium CVE-2025-5244 fixed in no fix yet
  • Medium CVE-2025-5245 fixed in no fix yet
  • Medium CVE-2025-69644 fixed in no fix yet
  • Medium CVE-2025-69651 fixed in no fix yet
  • Medium CVE-2025-69647 fixed in no fix yet
  • Medium CVE-2025-69648 fixed in no fix yet
  • Medium CVE-2025-69652 fixed in no fix yet
  • Medium CVE-2025-0840 fixed in 2.41-r1
High 8 known vulnerabilities in libxml2@2.11.8-r0 (hzibraunschweig/sormas-postgres:latest) Security · 8 CVEs

How to fix

No fixed version of libxml2 is available yet. Check whether hzibraunschweig/sormas-postgres:latest needs libxml2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-6021 fixed in no fix yet
  • High CVE-2024-56171 fixed in 2.11.8-r1
  • High CVE-2025-24928 fixed in 2.11.8-r1
  • High CVE-2024-40896 fixed in no fix yet
  • Medium CVE-2025-32414 fixed in 2.11.8-r3
  • Medium CVE-2025-9714 fixed in no fix yet
  • Low CVE-2025-27113 fixed in 2.11.8-r2
  • Low CVE-2025-32415 fixed in 2.11.8-r3
High 7 known vulnerabilities in openssl@3.1.5-r0 (hzibraunschweig/sormas-postgres:latest) Security · 7 CVEs

How to fix

Update openssl from 3.1.5-r0 to 3.1.6-r0 or later in hzibraunschweig/sormas-postgres:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.6-r0); 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-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2025-9230 fixed in 3.1.8-r1
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2025-9232 fixed in 3.1.8-r1
High 6 known vulnerabilities in expat@2.6.2-r0 (hzibraunschweig/sormas-postgres:latest) Security · 6 CVEs

How to fix

Update expat from 2.6.2-r0 to 2.6.3-r0 or later in hzibraunschweig/sormas-postgres: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.3-r0); 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-45490 fixed in 2.6.3-r0
  • High CVE-2024-8176 fixed in 2.7.0-r0
  • High CVE-2025-59375 fixed in 2.7.2-r0
  • High CVE-2024-45491 fixed in 2.6.3-r0
  • High CVE-2024-45492 fixed in 2.6.3-r0
  • Medium CVE-2024-50602 fixed in 2.6.4-r0
High 2 known vulnerabilities in libxslt@1.1.39-r0 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

Update libxslt from 1.1.39-r0 to 1.1.39-r1 or later in hzibraunschweig/sormas-postgres:latest. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.39-r1); 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-55549 fixed in 1.1.39-r1
  • High CVE-2025-24855 fixed in 1.1.39-r1
High 2 known vulnerabilities in nghttp2@1.58.0-r0 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

No fixed version of nghttp2 is available yet. Check whether hzibraunschweig/sormas-postgres:latest 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 no fix yet
High 2 known vulnerabilities in setuptools@68.2.2 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

Update setuptools from 68.2.2 to 70.0.0 or later in hzibraunschweig/sormas-postgres: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 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 2 known vulnerabilities in sqlite@3.44.2-r0 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

Update sqlite from 3.44.2-r0 to 3.44.2-r2 or later in hzibraunschweig/sormas-postgres: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.44.2-r2); 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.44.2-r2
  • Medium CVE-2025-3277 fixed in no fix yet
High 2 known vulnerabilities in xz@5.4.5-r0 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

Update xz from 5.4.5-r0 to 5.4.5-r1 or later in hzibraunschweig/sormas-postgres: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.5-r1); 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-31115 fixed in 5.4.5-r1
  • Medium CVE-2024-47611 fixed in no fix yet
High 1 known vulnerability in icu@74.1-r0 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

Update icu from 74.1-r0 to 74.1-r1 or later in hzibraunschweig/sormas-postgres: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 74.1-r1); 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 74.1-r1
High 1 known vulnerability in musl@1.2.4_git20230717-r4 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

Update musl from 1.2.4_git20230717-r4 to 1.2.4_git20230717-r5 or later in hzibraunschweig/sormas-postgres: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.4_git20230717-r5); 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-26519 fixed in 1.2.4_git20230717-r5
High 1 known vulnerability in py3-setuptools@68.2.2-r0 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

Update py3-setuptools from 68.2.2-r0 to 70.3.0-r0 or later in hzibraunschweig/sormas-postgres: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 70.3.0-r0); 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.3.0-r0

Medium 8

Medium 5 known vulnerabilities in busybox@1.36.1-r18 (hzibraunschweig/sormas-postgres:latest) Security · 5 CVEs

How to fix

Update busybox from 1.36.1-r18 to 1.36.1-r19 or later in hzibraunschweig/sormas-postgres: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.36.1-r19); 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-42364 fixed in 1.36.1-r19
  • Medium CVE-2023-42365 fixed in 1.36.1-r19
  • Medium CVE-2025-60876 fixed in no fix yet
  • Low CVE-2024-58251 fixed in 1.36.1-r21
  • Low CVE-2025-46394 fixed in 1.36.1-r21
Medium 2 known vulnerabilities in pip@23.3.1 (hzibraunschweig/sormas-postgres:latest) Security · 2 CVEs

How to fix

Update pip from 23.3.1 to 25.3 or later in hzibraunschweig/sormas-postgres: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 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-8869 fixed in 25.3
  • Low CVE-2026-1703 fixed in 26.0
Medium 1 known vulnerability in openldap@2.6.6-r1 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

No fixed version of openldap is available yet. Check whether hzibraunschweig/sormas-postgres:latest 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

  • Medium CVE-2026-22185 fixed in no fix yet

Low 2

Low 1 known vulnerability in util-linux@2.39.3-r0 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

No fixed version of util-linux is available yet. Check whether hzibraunschweig/sormas-postgres: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

  • Low CVE-2024-28085 fixed in no fix yet
Low 1 known vulnerability in zlib@1.3.1-r0 (hzibraunschweig/sormas-postgres:latest) Security · 1 CVE

How to fix

No fixed version of zlib is available yet. Check whether hzibraunschweig/sormas-postgres:latest needs zlib 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-27171 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.