Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could flood the HTTP/2 and web interface with crafted requests, exhausting CPU and memory and making Portainer slow or unavailable to administrators, as shown by CVE-2026-78669 and CVE-2026-78659. Note: CVE-2026-17106 only applies if an archive upload or import feature is enabled. The 49 exposed findings are acknowledged, but they are mostly denial-of-service issues and none are known to be actively exploited, which keeps the risk in the caution band rather than the critical band. Upgrading the affected Go runtime and golang.org/x/net packages to patched releases is the practical path to reducing this exposure.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | HIGH7.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | HIGH7.5 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | HIGH7.5 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78659 | HIGH7.5 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-94440 | HIGH7.5 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-17106 | MEDIUM6.24 | github.com/moby/go-archive v0.1.0 fixed in 0.3.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84304 | MEDIUM6 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84445 | MEDIUM6 | google.golang.org/grpc v1.82.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 ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78660 | MEDIUM6 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.9 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33747 | MEDIUM5.88 | github.com/moby/buildkit v0.25.1 fixed in 0.28.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-61801 | MEDIUM5.5 | github.com/moby/sys/user v0.4.0 fixed in 0.4.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85747 | MEDIUM5.44 | github.com/docker/distribution v2.8.3+incompatible No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111943 | MEDIUM5.44 | stdlib v1.25.14 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM5.3 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM5.2 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94439 | MEDIUM5.2 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84303 | MEDIUM5.04 | google.golang.org/grpc v1.82.1 fixed in 1.83.1 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94448 | MEDIUM4.88 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33997 | MEDIUM4.86 | github.com/docker/docker v28.5.1+incompatible fixed in 29.3.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15558 | MEDIUM4.8 | github.com/docker/cli v28.5.1+incompatible fixed in 29.2.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-95837 | MEDIUM4.68 | github.com/containerd/containerd/v2 v2.2.5 fixed in 2.2.7, 2.3.4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33748 | MEDIUM4.5 | github.com/moby/buildkit v0.25.1 fixed in 0.28.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41567 | MEDIUM4.32 | github.com/docker/docker v28.5.1+incompatible No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42306 | MEDIUM4.32 | github.com/docker/docker v28.5.1+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-47909 | LOW3.91 | github.com/gorilla/csrf v1.7.3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-61711 | LOW3.78 | github.com/moby/buildkit v0.25.1 fixed in 0.31.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | LOW3.66 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41568 | LOW3.6 | github.com/docker/docker v28.5.1+incompatible No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53495 | LOW3.3 | github.com/containerd/containerd v1.7.33 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53495 | LOW3.3 | github.com/containerd/containerd/v2 v2.2.5 fixed in 2.0.12, 2.2.8, 2.3.5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-61712 | LOW3.3 | github.com/moby/buildkit v0.25.1 fixed in 0.31.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.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.35.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.43.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/sdk v1.43.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.25.14 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53493 | LOW3.18 | github.com/containerd/containerd v1.7.33 fixed in 1.7.36 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53493 | LOW3.18 | github.com/containerd/containerd/v2 v2.2.5 fixed in 2.0.13, 2.2.9, 2.3.6, 2.4.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.55.0 No fix yet | — | Directly Exposed |
| CVE-2026-95838 | LOW1.98 | github.com/containerd/containerd v1.7.33 fixed in 1.7.35 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95838 | LOW1.98 | github.com/containerd/containerd/v2 v2.2.5 fixed in 2.0.12, 2.2.8, 2.3.5 | 0.2% Theoretical Threat | Directly Exposed |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.