Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could stall trace ingestion, exhaust memory and crash the collector through CVE-2026-84304, or drive up CPU on the UI port, disrupting observability for the services that depend on it. The gRPC ports accept unauthenticated traffic in the default configuration, so anyone who can reach them can trigger these flaws, and enabling authentication closes that anonymous path. Most of the 111 exposed findings are denial-of-service issues with no known active exploitation, so the verdict rests on availability risk rather than data theft or code execution.
Hardening plan for this image · 5 steps. The first cuts risk from 66 to 0.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| GHSA-hrxh-6v49-42gf | HIGH8.8 | google.golang.org/grpc v1.79.3 fixed in 1.82.1 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-84304 | HIGH7.5 | google.golang.org/grpc v1.79.3 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-56853 | HIGH7.5 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94440 | HIGH7.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | HIGH7.4 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34182 | HIGH7.4 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.26.1 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM6.5 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM6.5 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM6.48 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32282 | MEDIUM6.4 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM6.3 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM6.3 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-84303 | MEDIUM6.3 | google.golang.org/grpc v1.79.3 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-32289 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | MEDIUM6.1 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41602 | MEDIUM6 | github.com/apache/thrift v0.22.0 fixed in 0.23.0 | 1.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-43871 | MEDIUM6 | github.com/apache/thrift v0.22.0 fixed in 0.24.0 | 1.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32283 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56862 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-31790 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6042 | MEDIUM5.5 | musl 1.2.5-r21 fixed in 1.2.5-r22 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6042 | MEDIUM5.5 | musl-utils 1.2.5-r21 fixed in 1.2.5-r22 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM5.5 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM5.4 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM5.4 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39882 | MEDIUM5.3 | go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp v0.18.0 fixed in 0.19.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39882 | MEDIUM5.3 | go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.42.0 fixed in 1.43.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39882 | MEDIUM5.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.42.0 fixed in 1.43.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39822 | MEDIUM4.68 | stdlib v1.26.1 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM4.5 | github.com/klauspost/compress v1.18.4 fixed in 1.18.7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.34.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM4.5 | golang.org/x/text v0.34.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84445 | MEDIUM4.5 | google.golang.org/grpc v1.79.3 fixed in 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.5-r21 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.5-r21 fixed in 1.2.5-r24 | — | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.42.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-81871 | LOW3.9 | go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.18.0 fixed in 0.21.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.5-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.5-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | LOW3.53 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3.53 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.42.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.42.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.42.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW3.28 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW3.28 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-81872 | LOW3.18 | go.opentelemetry.io/otel/sdk/log v0.18.0 fixed in 0.21.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39828 | LOW3.17 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39832 | LOW3.13 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.95 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33810 | LOW2.95 | stdlib v1.26.1 fixed in 1.26.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.95 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39831 | LOW2.92 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.92 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.92 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40200 | LOW2.81 | musl 1.2.5-r21 fixed in 1.2.5-r23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40200 | LOW2.81 | musl-utils 1.2.5-r21 fixed in 1.2.5-r23 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22184 | LOW2.81 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42151 | LOW2.7 | github.com/prometheus/prometheus v0.310.0 fixed in 0.311.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42154 | LOW2.7 | github.com/prometheus/prometheus v0.310.0 fixed in 0.311.3, 0.305.2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39829 | LOW2.7 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-39830 | LOW2.7 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39835 | LOW2.7 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46597 | LOW2.7 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33814 | LOW2.7 | golang.org/x/net v0.51.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | LOW2.7 | golang.org/x/net v0.51.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78669 | LOW2.7 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78659 | LOW2.7 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78660 | LOW2.7 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27145 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33811 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-33814 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-33818 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39820 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-39836 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42499 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42504 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46600 | LOW2.7 | stdlib v1.26.1 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56859 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56860 | LOW2.7 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42508 | LOW2.66 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 6.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46595 | LOW2.56 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39883 | LOW2.52 | go.opentelemetry.io/otel/sdk v1.42.0 fixed in 1.43.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56854 | LOW2.45 | golang.org/x/crypto v0.48.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39827 | LOW2.34 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39834 | LOW2.34 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25680 | LOW2.34 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40179 | LOW2.2 | github.com/prometheus/prometheus v0.310.0 fixed in 3.5.2, 3.11.2, 0.311.2-0.20260410083055-07c6232d159b | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44903 | LOW2.2 | github.com/prometheus/prometheus v0.310.0 fixed in 0.311.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42502 | LOW2.2 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-97032 | LOW2.12 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW1.98 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39833 | LOW1.98 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42506 | LOW1.94 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46598 | LOW1.91 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56855 | LOW1.91 | golang.org/x/crypto v0.48.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78662 | LOW1.91 | golang.org/x/crypto v0.48.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-78663 | LOW1.91 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW1.8 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Post-Exploit |
| GO-2026-5932 | LOW1.44 | golang.org/x/crypto v0.48.0 No fix yet | — | Post-Exploit |
| CVE-2026-81870 | LOW1.19 | go.opentelemetry.io/otel/sdk v1.42.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.