Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who reaches the gRPC ingestion ports could exhaust CPU or memory through HTTP/2 floods and fragmented frames, as with GHSA-hrxh-6v49-42gf and CVE-2026-84304, crashing the trace collector and interrupting trace ingestion. These ports accept unauthenticated streams in the default configuration, so anyone who can reach them can exploit this, and enabling authentication on those receivers closes that anonymous path. The authorization bypass in CVE-2026-33186 is only relevant if gRPC authorization rules are actually configured. Review the exposed ports and apply the upstream library updates before relying on this image in production.
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.1 fixed in 1.82.1 | — | Directly ExposedContext importance: HIGH |
| CVE-2026-84304 | HIGH7.5 | google.golang.org/grpc v1.79.1 fixed in 1.83.1 | 0.6% 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-33186 | HIGH7.28 | google.golang.org/grpc v1.79.1 fixed in 1.79.3 | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111943 | MEDIUM6.8 | stdlib v1.26.1 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-q382-vc8q-7jhj | MEDIUM6.56 | github.com/modelcontextprotocol/go-sdk v1.3.1 fixed in 1.4.1 | — | Directly ExposedContext importance: MEDIUM |
| 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-34742 | MEDIUM6.48 | github.com/modelcontextprotocol/go-sdk v1.3.1 fixed in 1.4.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| 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.1 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-27145 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | 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-33814 | MEDIUM6 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | 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-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-78667 | MEDIUM6 | stdlib v1.26.1 fixed in 1.26.9, 1.27.2 | 0.5% 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-31789 | MEDIUM5.88 | libcrypto3 3.5.5-r0 fixed in 3.5.6-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3 3.5.5-r0 fixed in 3.5.6-r0 | 0.2% 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-45445 | MEDIUM5.46 | libcrypto3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | libssl3 3.5.5-r0 fixed in 3.5.7-r0 | 0.7% 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.16.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.40.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.41.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-39828 | MEDIUM5.28 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39832 | MEDIUM5.22 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33252 | MEDIUM5.2 | github.com/modelcontextprotocol/go-sdk v1.3.1 fixed in 1.4.1 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| 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-39821 | MEDIUM4.92 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33810 | MEDIUM4.92 | stdlib v1.26.1 fixed in 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | MEDIUM4.92 | stdlib v1.26.1 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% 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-39831 | MEDIUM4.86 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25681 | MEDIUM4.86 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27136 | MEDIUM4.86 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | MEDIUM4.68 | musl 1.2.5-r21 fixed in 1.2.5-r23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | MEDIUM4.68 | musl-utils 1.2.5-r21 fixed in 1.2.5-r23 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22184 | MEDIUM4.68 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.4% Theoretical Threat | 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-42151 | MEDIUM4.5 | github.com/prometheus/prometheus v0.309.2-0.20260113170727-c7bc56cf6c8f fixed in 0.311.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42154 | MEDIUM4.5 | github.com/prometheus/prometheus v0.309.2-0.20260113170727-c7bc56cf6c8f fixed in 0.311.3, 0.305.2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM4.5 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM4.5 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM4.5 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM4.5 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM4.5 | golang.org/x/net v0.51.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM4.5 | golang.org/x/net v0.51.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM4.5 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78659 | MEDIUM4.5 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.4% 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.1 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-33811 | MEDIUM4.5 | stdlib v1.26.1 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM4.44 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 6.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46595 | MEDIUM4.26 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39883 | MEDIUM4.2 | go.opentelemetry.io/otel/sdk v1.41.0 fixed in 1.43.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56854 | MEDIUM4.08 | golang.org/x/crypto v0.48.0 fixed in 0.55.0 | 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.41.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.16.0 fixed in 0.21.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | LOW3.9 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | LOW3.9 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | LOW3.9 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.3% 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-40179 | LOW3.66 | github.com/prometheus/prometheus v0.309.2-0.20260113170727-c7bc56cf6c8f fixed in 3.5.2, 3.11.2, 0.311.2-0.20260410083055-07c6232d159b | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44903 | LOW3.66 | github.com/prometheus/prometheus v0.309.2-0.20260113170727-c7bc56cf6c8f fixed in 0.311.3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | LOW3.66 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | LOW3.54 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.3 | zlib 1.3.1-r2 fixed in 1.3.2-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | LOW3.3 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.41.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.41.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.41.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-42506 | LOW3.24 | golang.org/x/net v0.51.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81872 | LOW3.18 | go.opentelemetry.io/otel/sdk/log v0.16.0 fixed in 0.21.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | LOW3.18 | golang.org/x/crypto v0.48.0 fixed in 0.52.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.48.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.48.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | LOW3.18 | golang.org/x/net v0.51.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib 1.3.1-r2 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| 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 |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.48.0 No fix yet | — | Directly Exposed |
| CVE-2026-81870 | LOW1.98 | go.opentelemetry.io/otel/sdk v1.41.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.