Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit CVE-2026-33186 to bypass gRPC authorization and perform unauthorized actions, and CVE-2026-41889 could enable SQL injection against the Harbor database under non-default query conditions. The exposed surface is significant: 103 exposed vulnerabilities, including 37 at severity 6 or higher and 1 at severity 7 or higher. Note that CVE-2026-33186 only applies if Harbor's gRPC server uses path-based authorization with specific deny rules and a fallback allow rule; CVE-2026-41889 requires the non-default simple protocol and a specific dollar-quoted query pattern. Remediation of the affected packages must be completed before any production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33186 | HIGH7.28 | google.golang.org/grpc v1.72.1 fixed in 1.79.3 | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41889 | MEDIUM6.66 | github.com/jackc/pgx/v4 v4.18.3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40355 | MEDIUM6.38 | krb5 1.20.2-14.ph5 fixed in 1.20.2-15.ph5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | krb5 1.20.2-14.ph5 fixed in 1.20.2-15.ph5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48863 | MEDIUM6.38 | libsolv 0.7.35-1.ph5 fixed in 0.7.39-1.ph5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-35172 | MEDIUM6.38 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34986 | MEDIUM6.38 | github.com/go-jose/go-jose/v4 v4.0.5 fixed in 4.1.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-32286 | MEDIUM6.38 | github.com/jackc/pgproto3/v2 v2.3.3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63209 | MEDIUM6.38 | github.com/klauspost/compress v1.18.0 fixed in 1.18.7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39882 | MEDIUM6.38 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.34.0 fixed in 1.43.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39829 | MEDIUM6.38 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39830 | MEDIUM6.38 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39835 | MEDIUM6.38 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46597 | MEDIUM6.38 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | golang.org/x/net v0.42.0 fixed in 0.53.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46600 | MEDIUM6.38 | golang.org/x/net v0.42.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM6.38 | golang.org/x/net v0.42.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM6.38 | golang.org/x/text v0.28.0 fixed in 0.41.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56852 | MEDIUM6.38 | golang.org/x/text v0.28.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84304 | MEDIUM6.38 | google.golang.org/grpc v1.72.1 fixed in 1.83.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84445 | MEDIUM6.38 | google.golang.org/grpc v1.72.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-33811 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33818 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56853 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78669 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97031 | MEDIUM6.38 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42508 | MEDIUM6.29 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-46595 | MEDIUM6.03 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44604 | MEDIUM5.95 | rpm-libs 6.0.1-4.ph5 fixed in 6.0.1-5.ph5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-39883 | MEDIUM5.95 | go.opentelemetry.io/otel/sdk v1.40.0 fixed in 1.43.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56854 | MEDIUM5.78 | golang.org/x/crypto v0.41.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9149 | MEDIUM5.52 | libsolv 0.7.35-1.ph5 fixed in 0.7.39-1.ph5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9150 | MEDIUM5.52 | libsolv 0.7.35-1.ph5 fixed in 0.7.39-1.ph5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41888 | MEDIUM5.52 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39827 | MEDIUM5.52 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39834 | MEDIUM5.52 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25680 | MEDIUM5.52 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | MEDIUM5.52 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM5.52 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16389 | MEDIUM5.18 | nss-libs 3.78-12.ph5 fixed in 3.78-13.ph5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42502 | MEDIUM5.18 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | MEDIUM5.18 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29181 | MEDIUM5.1 | go.opentelemetry.io/otel v1.40.0 fixed in 1.41.0 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-25679 | MEDIUM5.1 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27145 | MEDIUM5.1 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32280 | MEDIUM5.1 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-32283 | MEDIUM5.1 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-72897 | MEDIUM5.02 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.02 | golang.org/x/net v0.42.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97032 | MEDIUM5.02 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39833 | MEDIUM4.67 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32288 | MEDIUM4.67 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42506 | MEDIUM4.59 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.24.13 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47914 | MEDIUM4.5 | golang.org/x/crypto v0.41.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-58181 | MEDIUM4.5 | golang.org/x/crypto v0.41.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46598 | MEDIUM4.5 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | MEDIUM4.5 | golang.org/x/crypto v0.41.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | MEDIUM4.5 | golang.org/x/crypto v0.41.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-47911 | MEDIUM4.5 | golang.org/x/net v0.42.0 fixed in 0.45.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58190 | MEDIUM4.5 | golang.org/x/net v0.42.0 fixed in 0.45.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.5 | golang.org/x/net v0.42.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.24.13 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.24.13 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.5 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | LOW3.83 | stdlib v1.24.13 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35206 | LOW3.74 | helm.sh/helm/v3 v3.19.0 fixed in 3.20.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW2.8 | go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 fixed in 1.45.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW2.8 | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.34.0 fixed in 1.45.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW2.8 | go.opentelemetry.io/otel/sdk v1.40.0 fixed in 1.45.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW2.8 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32952 | LOW2.7 | github.com/Azure/go-ntlmssp v0.0.0-20221128193559-754e69321358 fixed in 0.1.1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2 1.11.1-5.ph5 fixed in 1.11.1-6.ph5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39828 | LOW2.69 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-39832 | LOW2.66 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-33540 | LOW2.63 | github.com/distribution/distribution v2.8.2+incompatible No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | LOW2.51 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39821 | LOW2.51 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-39831 | LOW2.48 | golang.org/x/crypto v0.41.0 fixed in 0.52.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25681 | LOW2.48 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27136 | LOW2.48 | golang.org/x/net v0.42.0 fixed in 0.55.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56858 | LOW2.48 | stdlib v1.24.13 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48864 | LOW2.39 | libsolv 0.7.35-1.ph5 fixed in 0.7.39-1.ph5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-39822 | LOW2.39 | stdlib v1.24.13 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW2.29 | libssh2 1.11.1-5.ph5 fixed in 1.11.1-6.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-47913 | LOW2.29 | golang.org/x/crypto v0.41.0 fixed in 0.43.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-27139 | LOW2.12 | stdlib v1.24.13 fixed in 1.25.8, 1.26.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW1.99 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW1.99 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW1.99 | libssh2 1.11.1-5.ph5 fixed in 1.11.1-6.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW1.99 | libssh2 1.11.1-5.ph5 fixed in 1.11.1-6.ph5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80231 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW1.81 | libssh2 1.11.1-5.ph5 fixed in 1.11.1-6.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW1.81 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl-libs 8.21.0-2.ph5 fixed in 8.22.0-1.ph5 | 0.4% Theoretical Threat | Post-Exploit |
| BDSA-2026-35496 | NONE0 | openssl 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | — | Not Applicable |
| BDSA-2026-35496 | NONE0 | openssl-libs 3.5.8-1.1.ph5 fixed in 3.5.9-0.1.ph5 | — | Not Applicable |
| BDSA-2026-22478 | NONE0 | rpm-libs 6.0.1-4.ph5 fixed in 6.0.1-5.ph5 | — | Not Applicable |
| CVE-2025-24358 | NONE0 | github.com/gorilla/csrf v1.7.2 fixed in 1.7.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47909 | NONE0 | github.com/gorilla/csrf v1.7.2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2303 | NONE0 | go.mongodb.org/mongo-driver v1.14.0 fixed in 1.17.7 | 0.3% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.41.0 No fix yet | — | Not Applicable |
| CVE-2026-78659 | NONE0 | golang.org/x/net v0.42.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.42.0 fixed in 0.60.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.40.0 fixed in 0.44.0 | 0.2% Theoretical Threat | Not Applicable |
| GHSA-hrxh-6v49-42gf | NONE0 | google.golang.org/grpc v1.72.1 fixed in 1.82.1 | — | Not Applicable |
| CVE-2026-84303 | NONE0 | google.golang.org/grpc v1.72.1 fixed in 1.83.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.13 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
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.