Repository scan
kpipe
eschizoid/kpipe · branch main · scanned 11 May 2026
High 362
High 42 known vulnerabilities in stdlib@1.23.3 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update stdlib from 1.23.3 to 1.24.9 or later in otel/opentelemetry-collector-contrib:0.114.0. 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-2026-33811 fixed in 1.25.10
- High CVE-2026-33814 fixed in 1.25.10
- High CVE-2026-39820 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2025-22871 fixed in 1.23.8
- High CVE-2025-68121 fixed in 1.24.13
- Medium CVE-2025-22866 fixed in 1.23.6
- Medium CVE-2025-58183 fixed in 1.24.8
- Medium CVE-2025-22870 fixed in 1.23.7
- and 22 more
High 38 known vulnerabilities in stdlib@1.23.7 (grafana/grafana:11.6.0)
How to fix
Update stdlib from 1.23.7 to 1.24.9 or later in grafana/grafana:11.6.0. 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-2026-33811 fixed in 1.25.10
- High CVE-2026-33814 fixed in 1.25.10
- High CVE-2026-39820 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- High CVE-2025-22871 fixed in 1.23.8
- 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
- and 18 more
High 37 known vulnerabilities in stdlib@1.24.3 (prom/prometheus:v3.4.0)
How to fix
Update stdlib from 1.24.3 to 1.24.4 or later in prom/prometheus:v3.4.0. 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.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-22874 fixed in 1.24.4
- 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-2026-33811 fixed in 1.25.10
- High CVE-2026-33814 fixed in 1.25.10
- High CVE-2026-39820 fixed in 1.25.10
- High CVE-2026-39836 fixed in 1.25.10
- High CVE-2026-42499 fixed in 1.25.10
- 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
- and 17 more
High 20 known vulnerabilities in stdlib@1.26.0 (confluentinc/cp-kafka:8.2.0)
How to fix
Update stdlib from 1.26.0 to 1.26.1 or later in confluentinc/cp-kafka:8.2.0. 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.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
- High CVE-2026-25679 fixed in 1.26.1
- High CVE-2026-27137 fixed in 1.26.1
- High CVE-2026-32280 fixed in 1.26.2
- High CVE-2026-32281 fixed in 1.26.2
- High CVE-2026-32283 fixed in 1.26.2
- High CVE-2026-33811 fixed in 1.26.3
- High CVE-2026-33814 fixed in 1.26.3
- High CVE-2026-39820 fixed in 1.26.3
- High CVE-2026-39836 fixed in 1.26.3
- High CVE-2026-42499 fixed in 1.26.3
- High CVE-2026-33810 fixed in 1.26.2
- Medium CVE-2026-39825 fixed in 1.26.3
- Medium CVE-2026-32288 fixed in 1.26.2
- Medium CVE-2026-27138 fixed in 1.26.1
- Medium CVE-2026-27142 fixed in 1.26.1
- Medium CVE-2026-32289 fixed in 1.26.2
- Medium CVE-2026-39823 fixed in 1.26.3
- Medium CVE-2026-39826 fixed in 1.26.3
- Medium CVE-2026-32282 fixed in 1.26.2
- Low CVE-2026-27139 fixed in 1.26.1
High 20 known vulnerabilities in stdlib@1.26.0 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update stdlib from 1.26.0 to 1.26.1 or later in confluentinc/cp-schema-registry:8.2.0. 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.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
- High CVE-2026-25679 fixed in 1.26.1
- High CVE-2026-27137 fixed in 1.26.1
- High CVE-2026-32280 fixed in 1.26.2
- High CVE-2026-32281 fixed in 1.26.2
- High CVE-2026-32283 fixed in 1.26.2
- High CVE-2026-33811 fixed in 1.26.3
- High CVE-2026-33814 fixed in 1.26.3
- High CVE-2026-39820 fixed in 1.26.3
- High CVE-2026-39836 fixed in 1.26.3
- High CVE-2026-42499 fixed in 1.26.3
- High CVE-2026-33810 fixed in 1.26.2
- Medium CVE-2026-39825 fixed in 1.26.3
- Medium CVE-2026-32288 fixed in 1.26.2
- Medium CVE-2026-27138 fixed in 1.26.1
- Medium CVE-2026-27142 fixed in 1.26.1
- Medium CVE-2026-32289 fixed in 1.26.2
- Medium CVE-2026-39823 fixed in 1.26.3
- Medium CVE-2026-39826 fixed in 1.26.3
- Medium CVE-2026-32282 fixed in 1.26.2
- Low CVE-2026-27139 fixed in 1.26.1
High 19 known vulnerabilities in openssl@3.3.3-r0 (grafana/grafana:11.6.0)
How to fix
Update openssl from 3.3.3-r0 to 3.3.6-r0 or later in grafana/grafana:11.6.0. 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.3.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-2025-69419 fixed in 3.3.6-r0
- High CVE-2025-69420 fixed in 3.3.6-r0
- High CVE-2025-69421 fixed in 3.3.6-r0
- High CVE-2025-9230 fixed in 3.3.5-r0
- High CVE-2026-28388 fixed in 3.3.7-r0
- High CVE-2026-28389 fixed in 3.3.7-r0
- High CVE-2026-28390 fixed in 3.3.7-r0
- High CVE-2026-31790 fixed in 3.3.7-r0
- High CVE-2026-28387 fixed in 3.3.7-r0
- High CVE-2025-15467 fixed in 3.3.6-r0
- High CVE-2026-31789 fixed in 3.3.7-r0
- Medium CVE-2025-69418 fixed in 3.3.6-r0
- Medium CVE-2025-68160 fixed in 3.3.6-r0
- Medium CVE-2026-22796 fixed in 3.3.6-r0
- Medium CVE-2026-22795 fixed in 3.3.6-r0
- Medium CVE-2025-15468 fixed in 3.3.6-r0
- Medium CVE-2025-66199 fixed in 3.3.6-r0
- Medium CVE-2025-9232 fixed in 3.3.5-r0
- Medium CVE-2025-9231 fixed in 3.3.5-r0
High 16 known vulnerabilities in curl@8.12.1-r1 (grafana/grafana:11.6.0)
How to fix
Update curl from 8.12.1-r1 to 8.14.1-r0 or later in grafana/grafana:11.6.0. 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.14.1-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-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
- Medium CVE-2025-10966 fixed in no fix yet
- Medium CVE-2025-5025 fixed in 8.14.0-r0
- 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-2025-14017 fixed in no fix yet
- Medium CVE-2025-4947 fixed in 8.14.0-r0
- Medium CVE-2026-1965 fixed in no fix yet
- Medium CVE-2026-3784 fixed in no fix yet
- Low CVE-2025-15224 fixed in no fix yet
High 8 known vulnerabilities in libpng@2%3A1.6.37-12.el9_7.1 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of libpng is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs libpng 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-25646 fixed in no fix yet
- High CVE-2025-64720 fixed in no fix yet
- High CVE-2025-65018 fixed in no fix yet
- High CVE-2025-66293 fixed in no fix yet
- High CVE-2026-22020 fixed in no fix yet
- Medium CVE-2026-3713 fixed in no fix yet
- Medium CVE-2026-33416 fixed in no fix yet
- Medium CVE-2026-33636 fixed in no fix yet
High 8 known vulnerabilities in libpng@2%3A1.6.37-12.el9_7.1 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of libpng is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs libpng 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-25646 fixed in no fix yet
- High CVE-2025-64720 fixed in no fix yet
- High CVE-2025-65018 fixed in no fix yet
- High CVE-2025-66293 fixed in no fix yet
- High CVE-2026-22020 fixed in no fix yet
- Medium CVE-2026-3713 fixed in no fix yet
- Medium CVE-2026-33416 fixed in no fix yet
- Medium CVE-2026-33636 fixed in no fix yet
High 7 known vulnerabilities in netty-codec-http@4.1.130.Final (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update netty-codec-http from 4.1.130.Final to 4.1.133.Final or later in confluentinc/cp-schema-registry:8.2.0. 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.1.133.Final); 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-42584 fixed in 4.1.133.Final
- High CVE-2026-33870 fixed in 4.1.132.Final
- High CVE-2026-42587 fixed in 4.1.133.Final
- Medium CVE-2026-41417 fixed in 4.1.133.Final
- Medium CVE-2026-42581 fixed in 4.1.133.Final
- Medium CVE-2026-42580 fixed in 4.1.133.Final
- Medium CVE-2026-42585 fixed in 4.1.133.Final
High 6 known vulnerabilities in python3.9@3.9.25-3.el9_7 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of python3.9 is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs python3.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
- High CVE-2026-4519 fixed in no fix yet
- High CVE-2026-4786 fixed in no fix yet
- High CVE-2026-6100 fixed in no fix yet
- Medium CVE-2025-15366 fixed in no fix yet
- Medium CVE-2025-15367 fixed in no fix yet
- Medium CVE-2025-12084 fixed in no fix yet
High 6 known vulnerabilities in python3.9@3.9.25-3.el9_7 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of python3.9 is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs python3.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
- High CVE-2026-4519 fixed in no fix yet
- High CVE-2026-4786 fixed in no fix yet
- High CVE-2026-6100 fixed in no fix yet
- Medium CVE-2025-15366 fixed in no fix yet
- Medium CVE-2025-15367 fixed in no fix yet
- Medium CVE-2025-12084 fixed in no fix yet
High 6 known vulnerabilities in net@0.31.0 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update net from 0.31.0 to 0.53.0 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.53.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-2026-33814 fixed in 0.53.0
- Medium CVE-2025-22870 fixed in 0.36.0
- Medium CVE-2024-45338 fixed in 0.33.0
- Medium CVE-2025-22872 fixed in 0.38.0
- Medium CVE-2025-47911 fixed in 0.45.0
- Medium CVE-2025-58190 fixed in 0.45.0
High 5 known vulnerabilities in crypto@0.29.0 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update crypto from 0.29.0 to 0.35.0 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.35.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-22869 fixed in 0.35.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2024-45337 fixed in 0.31.0
- Medium CVE-2025-47914 fixed in 0.45.0
- Medium CVE-2025-58181 fixed in 0.45.0
High 5 known vulnerabilities in prometheus@0.0.0-20250517064749-546b1d242e20%2Bdirty (prom/prometheus:v3.4.0)
How to fix
Update prometheus from 0.0.0-20250517064749-546b1d242e20%2Bdirty to 0.0.0-20260427144041-eb173f5256d4 or later in prom/prometheus:v3.4.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.0.0-20260427144041-eb173f5256d4); 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-42151 fixed in 0.0.0-20260427144041-eb173f5256d4
- High CVE-2026-42154 fixed in 0.311.3
- Medium GHSA-fw8g-cg8f-9j28 fixed in 0.311.3
- Medium CVE-2026-40179 fixed in 0.311.2-0.20260410083055-07c6232d159b
- Medium CVE-2026-40179 fixed in no fix yet
High 4 known vulnerabilities in glibc@2.34-231.el9_7.10 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of glibc is available yet. Check whether confluentinc/cp-kafka:8.2.0 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
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2026-0861 fixed in no fix yet
- Medium CVE-2026-0915 fixed in no fix yet
- Low CVE-2025-15281 fixed in no fix yet
High 4 known vulnerabilities in gnutls@3.8.3-9.el9 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of gnutls is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs gnutls 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-33845 fixed in no fix yet
- High CVE-2026-33846 fixed in no fix yet
- Medium CVE-2025-14831 fixed in no fix yet
- Medium CVE-2026-3833 fixed in no fix yet
High 4 known vulnerabilities in glibc@2.34-231.el9_7.10 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of glibc is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 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
- High CVE-2026-4046 fixed in no fix yet
- High CVE-2026-0861 fixed in no fix yet
- Medium CVE-2026-0915 fixed in no fix yet
- Low CVE-2025-15281 fixed in no fix yet
High 4 known vulnerabilities in gnutls@3.8.3-9.el9 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of gnutls is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs gnutls 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-33845 fixed in no fix yet
- High CVE-2026-33846 fixed in no fix yet
- Medium CVE-2025-14831 fixed in no fix yet
- Medium CVE-2026-3833 fixed in no fix yet
High 4 known vulnerabilities in net@0.36.0 (grafana/grafana:11.6.0)
How to fix
Update net from 0.36.0 to 0.53.0 or later in grafana/grafana:11.6.0. 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.53.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-2026-33814 fixed in 0.53.0
- Medium CVE-2025-22872 fixed in 0.38.0
- Medium CVE-2025-47911 fixed in 0.45.0
- Medium CVE-2025-58190 fixed in 0.45.0
High 4 known vulnerabilities in prometheus@0.301.0 (grafana/grafana:11.6.0)
How to fix
Update prometheus from 0.301.0 to 0.311.3 or later in grafana/grafana:11.6.0. 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.311.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
- High CVE-2026-42151 fixed in 0.311.3
- High CVE-2026-42154 fixed in 0.311.3
- Medium GHSA-fw8g-cg8f-9j28 fixed in 0.311.3
- Medium CVE-2026-40179 fixed in 0.311.2-0.20260410083055-07c6232d159b
High 4 known vulnerabilities in prometheus@0.54.1 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update prometheus from 0.54.1 to 0.311.3 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.311.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
- High CVE-2026-42151 fixed in 0.311.3
- High CVE-2026-42154 fixed in 0.311.3
- Medium GHSA-fw8g-cg8f-9j28 fixed in 0.311.3
- Medium CVE-2026-40179 fixed in 0.311.2-0.20260410083055-07c6232d159b
High 3 known vulnerabilities in gnupg2@2.3.3-5.el9_7 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of gnupg2 is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs gnupg2 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-68973 fixed in no fix yet
- High CVE-2026-24881 fixed in no fix yet
- High CVE-2026-24882 fixed in no fix yet
High 3 known vulnerabilities in gnupg2@2.3.3-5.el9_7 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of gnupg2 is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs gnupg2 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-68973 fixed in no fix yet
- High CVE-2026-24881 fixed in no fix yet
- High CVE-2026-24882 fixed in no fix yet
High 3 known vulnerabilities in crypto@0.35.0 (grafana/grafana:11.6.0)
How to fix
Update crypto from 0.35.0 to 0.43.0 or later in grafana/grafana:11.6.0. 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.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-47913 fixed in 0.43.0
- Medium CVE-2025-47914 fixed in 0.45.0
- Medium CVE-2025-58181 fixed in 0.45.0
High 3 known vulnerabilities in pgx@5.7.2#v5 (grafana/grafana:11.6.0)
How to fix
Update pgx from 5.7.2#v5 to 5.9.0 or later in grafana/grafana:11.6.0. 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.9.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-2026-33815 fixed in 5.9.0
- High CVE-2026-33816 fixed in 5.9.0
- Low CVE-2026-41889 fixed in 5.9.2
High 3 known vulnerabilities in docker@27.3.1%2Bincompatible (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
No fixed version of docker is available yet. Check whether otel/opentelemetry-collector-contrib:0.114.0 needs docker 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-34040 fixed in no fix yet
- Medium CVE-2026-33997 fixed in no fix yet
- Low CVE-2025-54410 fixed in 28.0.0
High 3 known vulnerabilities in pgx@5.7.1#v5 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update pgx from 5.7.1#v5 to 5.9.0 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.9.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-2026-33815 fixed in 5.9.0
- High CVE-2026-33816 fixed in 5.9.0
- Low CVE-2026-41889 fixed in 5.9.2
High 3 known vulnerabilities in runc@1.1.14 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update runc from 1.1.14 to 1.2.8 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.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-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 3 known vulnerabilities in crypto@0.37.0 (prom/prometheus:v3.4.0)
How to fix
Update crypto from 0.37.0 to 0.43.0 or later in prom/prometheus:v3.4.0. 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.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-47913 fixed in 0.43.0
- Medium CVE-2025-47914 fixed in 0.45.0
- Medium CVE-2025-58181 fixed in 0.45.0
High 3 known vulnerabilities in net@0.39.0 (prom/prometheus:v3.4.0)
How to fix
Update net from 0.39.0 to 0.53.0 or later in prom/prometheus:v3.4.0. 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.53.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-2026-33814 fixed in 0.53.0
- Medium CVE-2025-47911 fixed in 0.45.0
- Medium CVE-2025-58190 fixed in 0.45.0
High 2 known vulnerabilities in jetty-http@12.0.25 (confluentinc/cp-kafka:8.2.0)
How to fix
Update jetty-http from 12.0.25 to 12.0.33 or later in confluentinc/cp-kafka:8.2.0. 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 12.0.33); 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-2332 fixed in 12.0.33
- Low CVE-2025-11143 fixed in 12.0.31
High 2 known vulnerabilities in krb5@1.21.1-8.el9_6 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of krb5 is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs krb5 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-40356 fixed in no fix yet
- Medium CVE-2026-40355 fixed in no fix yet
High 2 known vulnerabilities in libarchive@3.5.3-6.el9_6 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of libarchive is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs libarchive 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-4424 fixed in no fix yet
- Medium CVE-2026-5121 fixed in no fix yet
High 2 known vulnerabilities in jetty-http@12.0.25 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update jetty-http from 12.0.25 to 12.0.33 or later in confluentinc/cp-schema-registry:8.2.0. 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 12.0.33); 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-2332 fixed in 12.0.33
- Low CVE-2025-11143 fixed in 12.0.31
High 2 known vulnerabilities in krb5@1.21.1-8.el9_6 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of krb5 is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs krb5 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-40356 fixed in no fix yet
- Medium CVE-2026-40355 fixed in no fix yet
High 2 known vulnerabilities in libarchive@3.5.3-6.el9_6 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of libarchive is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs libarchive 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-4424 fixed in no fix yet
- Medium CVE-2026-5121 fixed in no fix yet
High 2 known vulnerabilities in netty-codec-http2@4.1.130.Final (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update netty-codec-http2 from 4.1.130.Final to 4.1.133.Final or later in confluentinc/cp-schema-registry:8.2.0. 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.1.133.Final); 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-42587 fixed in 4.1.133.Final
- High CVE-2026-33871 fixed in 4.1.132.Final
High 2 known vulnerabilities in c-ares@1.34.3-r0 (grafana/grafana:11.6.0)
How to fix
Update c-ares from 1.34.3-r0 to 1.34.5-r0 or later in grafana/grafana:11.6.0. 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.5-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-31498 fixed in 1.34.5-r0
- Medium CVE-2025-62408 fixed in 1.34.6-r0
High 2 known vulnerabilities in jwt@5.2.1#v5 (grafana/grafana:11.6.0)
How to fix
Update jwt from 5.2.1#v5 to 5.2.2 or later in grafana/grafana:11.6.0. 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.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
- High CVE-2025-30204 fixed in 5.2.2
- High CVE-2025-30204 fixed in 4.5.2
and 37 more groups with 46 findings
Medium 83
Medium 8 known vulnerabilities in openfga@1.8.6 (grafana/grafana:11.6.0)
How to fix
Update openfga from 1.8.6 to 1.14.0 or later in grafana/grafana:11.6.0. 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.14.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-2026-34972 fixed in 1.14.0
- Medium CVE-2026-41131 fixed in 1.14.1
- Medium CVE-2025-46331 fixed in 1.8.11
- Medium CVE-2025-48371 fixed in 1.8.13
- Medium CVE-2025-64751 fixed in 1.11.1
- Medium CVE-2026-24851 fixed in 1.11.3
- Medium CVE-2026-33729 fixed in 1.13.1
- Medium CVE-2026-40293 fixed in 1.14.0
Medium 3 known vulnerabilities in log4j-core@2.25.3 (confluentinc/cp-kafka:8.2.0)
How to fix
Update log4j-core from 2.25.3 to 2.25.4 or later in confluentinc/cp-kafka:8.2.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.25.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-34477 fixed in 2.25.4
- Medium CVE-2026-34478 fixed in 2.25.4
- Medium CVE-2026-34480 fixed in 2.25.4
Medium 3 known vulnerabilities in log4j-core@2.25.3 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update log4j-core from 2.25.3 to 2.25.4 or later in confluentinc/cp-schema-registry:8.2.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.25.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-34477 fixed in 2.25.4
- Medium CVE-2026-34478 fixed in 2.25.4
- Medium CVE-2026-34480 fixed in 2.25.4
Medium 3 known vulnerabilities in busybox@1.37.0-r12 (grafana/grafana:11.6.0)
How to fix
No fixed version of busybox is available yet. Check whether grafana/grafana:11.6.0 needs busybox 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-60876 fixed in no fix yet
- Low CVE-2024-58251 fixed in 1.37.0-r14
- Low CVE-2025-46394 fixed in 1.37.0-r14
Medium 3 known vulnerabilities in aws-sdk-go-v2@1.32.5#service/kinesis (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update aws-sdk-go-v2 from 1.32.5#service/kinesis to 1.43.5 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.43.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.43.5
- Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.97.3
- Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.7.8
Medium 3 known vulnerabilities in exporters@0.7.0#otlp/otlplog/otlploghttp (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update exporters from 0.7.0#otlp/otlplog/otlploghttp to 0.19.0 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.19.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-2026-39882 fixed in 0.19.0
- Medium CVE-2026-39882 fixed in 1.43.0
- Medium CVE-2026-39882 fixed in 1.43.0
Medium 3 known vulnerabilities in mapstructure@2.2.1#v2 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update mapstructure from 2.2.1#v2 to 2.4.0 or later in otel/opentelemetry-collector-contrib:0.114.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.4.0); 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-11065 fixed in 2.4.0
- Medium GHSA-2464-8j7c-4cjm fixed in 2.4.0
- Medium GHSA-fv92-fjc5-jj9h fixed in 2.3.0
Medium 3 known vulnerabilities in mapstructure@2.2.1#v2 (prom/prometheus:v3.4.0)
How to fix
Update mapstructure from 2.2.1#v2 to 2.4.0 or later in prom/prometheus:v3.4.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.4.0); 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-11065 fixed in 2.4.0
- Medium GHSA-2464-8j7c-4cjm fixed in 2.4.0
- Medium GHSA-fv92-fjc5-jj9h fixed in 2.3.0
Medium 2 known vulnerabilities in glib2@2.68.4-18.el9_7.1 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of glib2 is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs glib2 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-13601 fixed in no fix yet
- Low CVE-2025-7039 fixed in no fix yet
Medium 2 known vulnerabilities in jackson-core@2.19.2 (confluentinc/cp-kafka:8.2.0)
How to fix
Update jackson-core from 2.19.2 to 2.21.1 or later in confluentinc/cp-kafka:8.2.0. 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.21.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 GHSA-72hv-8253-57qq fixed in 2.21.1
- Medium GHSA-72hv-8253-57qq fixed in 2.21.1
Medium 2 known vulnerabilities in openssl@1%3A3.5.1-7.el9_7 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of openssl is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs openssl 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-31790 fixed in no fix yet
- Medium CVE-2026-28390 fixed in no fix yet
Medium 2 known vulnerabilities in python-pip@21.3.1-1.el9 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of python-pip is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs python-pip 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-2023-45803 fixed in no fix yet
- Low CVE-2021-3572 fixed in no fix yet
Medium 2 known vulnerabilities in glib2@2.68.4-18.el9_7.1 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of glib2 is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs glib2 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-13601 fixed in no fix yet
- Low CVE-2025-7039 fixed in no fix yet
Medium 2 known vulnerabilities in openssl@1%3A3.5.1-7.el9_7 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of openssl is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs openssl 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-31790 fixed in no fix yet
- Medium CVE-2026-28390 fixed in no fix yet
Medium 2 known vulnerabilities in python-pip@21.3.1-1.el9 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of python-pip is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs python-pip 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-2023-45803 fixed in no fix yet
- Low CVE-2021-3572 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go@1.55.5 (grafana/grafana:11.6.0)
How to fix
No fixed version of aws-sdk-go is available yet. Check whether grafana/grafana:11.6.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
- Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go-v2@1.58.3#service/s3 (grafana/grafana:11.6.0)
How to fix
Update aws-sdk-go-v2 from 1.58.3#service/s3 to 1.97.3 or later in grafana/grafana:11.6.0. 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.97.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 GHSA-xmrv-pmrh-hhx2 fixed in 1.97.3
- Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.7.8
Medium 2 known vulnerabilities in zlib@1.3.1-r2 (grafana/grafana:11.6.0)
How to fix
Update zlib from 1.3.1-r2 to 1.3.2-r0 or later in grafana/grafana:11.6.0. 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.2-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
- Medium CVE-2026-22184 fixed in 1.3.2-r0
- Low CVE-2026-27171 fixed in 1.3.2-r0
Medium 2 known vulnerabilities in aws-sdk-go@1.55.5 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
No fixed version of aws-sdk-go is available yet. Check whether otel/opentelemetry-collector-contrib:0.114.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
- Low CVE-2020-8912 fixed in no fix yet
Medium 2 known vulnerabilities in aws-sdk-go@1.55.7 (prom/prometheus:v3.4.0)
How to fix
No fixed version of aws-sdk-go is available yet. Check whether prom/prometheus:v3.4.0 needs aws-sdk-go 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-2020-8911 fixed in no fix yet
- Low CVE-2020-8912 fixed in no fix yet
Medium 1 known vulnerability in busybox@1.37.0-r20 (alpine:3.22)
How to fix
No fixed version of busybox is available yet. Check whether alpine:3.22 needs busybox 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-60876 fixed in no fix yet
Medium 1 known vulnerability in curl@7.76.1-35.el9_7.3 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of curl is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs curl 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-9086 fixed in no fix yet
Medium 1 known vulnerability in libtasn1@4.16.0-9.el9 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of libtasn1 is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs libtasn1 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-13151 fixed in no fix yet
Medium 1 known vulnerability in log4j-1.2-api@2.25.3 (confluentinc/cp-kafka:8.2.0)
How to fix
Update log4j-1.2-api from 2.25.3 to 2.25.4 or later in confluentinc/cp-kafka:8.2.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.25.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-34479 fixed in 2.25.4
Medium 1 known vulnerability in systemd@252-55.el9_7.7 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of systemd is available yet. Check whether confluentinc/cp-kafka:8.2.0 needs systemd 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-29111 fixed in no fix yet
Medium 1 known vulnerability in util-linux@2.37.4-21.el9_7 (confluentinc/cp-kafka:8.2.0)
How to fix
No fixed version of util-linux is available yet. Check whether confluentinc/cp-kafka:8.2.0 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-2025-14104 fixed in no fix yet
Medium 1 known vulnerability in async-http-client@2.12.4 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update async-http-client from 2.12.4 to 3.0.9 or later in confluentinc/cp-schema-registry:8.2.0. 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.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-2026-40490 fixed in 3.0.9
Medium 1 known vulnerability in curl@7.76.1-35.el9_7.3 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of curl is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs curl 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-9086 fixed in no fix yet
Medium 1 known vulnerability in jackson-core@2.19.0 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update jackson-core from 2.19.0 to 2.21.1 or later in confluentinc/cp-schema-registry:8.2.0. 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.21.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 GHSA-72hv-8253-57qq fixed in 2.21.1
Medium 1 known vulnerability in libtasn1@4.16.0-9.el9 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of libtasn1 is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs libtasn1 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-13151 fixed in no fix yet
Medium 1 known vulnerability in log4j-1.2-api@2.25.3 (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update log4j-1.2-api from 2.25.3 to 2.25.4 or later in confluentinc/cp-schema-registry:8.2.0. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.25.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-34479 fixed in 2.25.4
Medium 1 known vulnerability in systemd@252-55.el9_7.7 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of systemd is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs systemd 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-29111 fixed in no fix yet
Medium 1 known vulnerability in util-linux@2.37.4-21.el9_7 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of util-linux is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 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-2025-14104 fixed in no fix yet
Medium 1 known vulnerability in vertx-core@4.5.24 (confluentinc/cp-schema-registry:8.2.0)
How to fix
No fixed version of vertx-core is available yet. Check whether confluentinc/cp-schema-registry:8.2.0 needs vertx-core 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-6860 fixed in no fix yet
Medium 1 known vulnerability in bleve@2.4.4-0.20250319135056-b82baf10b205#v2 (grafana/grafana:11.6.0)
How to fix
Update bleve from 2.4.4-0.20250319135056-b82baf10b205#v2 to 2.5.0 or later in grafana/grafana:11.6.0. 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.5.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-2022-31022 fixed in 2.5.0
Medium 1 known vulnerability in eventstream@1.6.3 (grafana/grafana:11.6.0)
How to fix
Update eventstream from 1.6.3 to 1.7.8 or later in grafana/grafana:11.6.0. 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.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
- Medium GHSA-xmrv-pmrh-hhx2 fixed in 1.7.8
Medium 1 known vulnerability in exporters@1.34.0#otlp/otlptrace/otlptracehttp (grafana/grafana:11.6.0)
How to fix
Update exporters from 1.34.0#otlp/otlptrace/otlptracehttp to 1.43.0 or later in grafana/grafana:11.6.0. 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.43.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-2026-39882 fixed in 1.43.0
Medium 1 known vulnerability in go-ntlmssp@0.0.0-20220621081337-cb9428e4ac1e (grafana/grafana:11.6.0)
How to fix
Update go-ntlmssp from 0.0.0-20220621081337-cb9428e4ac1e to 0.1.1 or later in grafana/grafana:11.6.0. 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.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-32952 fixed in 0.1.1
Medium 1 known vulnerability in loki@3.2.1#v3 (grafana/grafana:11.6.0)
How to fix
Update loki from 3.2.1#v3 to 3.6.4 or later in grafana/grafana:11.6.0. 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.6.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-21726 fixed in 3.6.4
Medium 1 known vulnerability in otlptracehttp@1.34.0 (grafana/grafana:11.6.0)
How to fix
Update otlptracehttp from 1.34.0 to 1.43.0 or later in grafana/grafana:11.6.0. 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.43.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-2026-39882 fixed in 1.43.0
and 10 more groups with 10 findings
Low 7
Low 2 known vulnerabilities in circl@1.3.7 (grafana/grafana:11.6.0)
How to fix
Update circl from 1.3.7 to 1.6.3 or later in grafana/grafana:11.6.0. 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.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
- Low CVE-2026-1229 fixed in 1.6.3
- Low CVE-2025-8556 fixed in 1.6.1
Low 1 known vulnerability in netty-handler-proxy@4.1.130.Final (confluentinc/cp-schema-registry:8.2.0)
How to fix
Update netty-handler-proxy from 4.1.130.Final to 4.1.133.Final or later in confluentinc/cp-schema-registry:8.2.0. 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.1.133.Final); 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-42578 fixed in 4.1.133.Final
Low 1 known vulnerability in go-redis@9.7.0#v9 (grafana/grafana:11.6.0)
How to fix
Update go-redis from 9.7.0#v9 to 9.7.3 or later in grafana/grafana:11.6.0. 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.7.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
- Low CVE-2025-29923 fixed in 9.7.3
Low 1 known vulnerability in edwards25519@1.1.0 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update edwards25519 from 1.1.0 to 1.1.1 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.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-2026-26958 fixed in 1.1.1
Low 1 known vulnerability in go-redis@9.7.0#v9 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update go-redis from 9.7.0#v9 to 9.7.3 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.7.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
- Low CVE-2025-29923 fixed in 9.7.3
Low 1 known vulnerability in gosnowflake@1.12.0 (otel/opentelemetry-collector-contrib:0.114.0)
How to fix
Update gosnowflake from 1.12.0 to 1.13.3 or later in otel/opentelemetry-collector-contrib:0.114.0. 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.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
- Low CVE-2025-46327 fixed in 1.13.3
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 11 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.