Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The most practical risk comes from CVE-2026-78667: because Grafana terminates HTTP and serves resources, a remote unauthenticated attacker could send crafted Range headers that drive up CPU usage and degrade or deny service availability. The remaining exposed findings are capped at a severity of 6.38, and the post-exploit-only surface is minimal with a maximum of 2.29, so nothing here points to code execution, credential theft, or data exposure. Pinning by digest and the verified Grafana publisher reduce supply-chain exposure. Placing Grafana behind a reverse proxy or WAF that rejects excessive or overly fragmented Range headers removes this denial-of-service vector entirely.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78667 | MEDIUM6.38 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | MEDIUM6.38 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78667 | MEDIUM6.38 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-78669 | MEDIUM5.1 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM5.1 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM5.1 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM5.1 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM5.1 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM5.1 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM5.1 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM5.1 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.02 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | LOW3.6 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56857 | LOW2.8 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW2.8 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW2.8 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84304 | LOW2.29 | google.golang.org/grpc v1.83.0 fixed in 1.83.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84445 | LOW2.29 | google.golang.org/grpc v1.83.0 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 | Post-Exploit |
| CVE-2026-21728 | LOW2.29 | github.com/grafana/tempo v1.5.1-0.20260910130453-bcfe9f230c1d fixed in 2.8.4, 2.9.2, 2.10.2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56866 | LOW1.99 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94439 | LOW1.99 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56866 | LOW1.99 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94439 | LOW1.99 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56866 | LOW1.99 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94439 | LOW1.99 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28377 | LOW1.99 | github.com/grafana/tempo v1.5.1-0.20260910130453-bcfe9f230c1d fixed in 2.10.3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94448 | LOW1.87 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94448 | LOW1.87 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94448 | LOW1.87 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56855 | LOW1.62 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-78662 | LOW1.62 | golang.org/x/crypto v0.55.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.4% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.57.0 No fix yet | — | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.56.0 No fix yet | — | Not Applicable |
| CVE-2026-78659 | NONE0 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.58.0 fixed in 0.60.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.7 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | golang.org/x/net v0.59.0 fixed in 0.60.0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.6 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.27.1 fixed in 1.26.9, 1.27.2 | 0.2% Theoretical Threat | Not Applicable |
| GO-2026-5932 | NONE0 | golang.org/x/crypto v0.55.0 No fix yet | — | Not Applicable |
| CVE-2026-84303 | NONE0 | google.golang.org/grpc v1.83.0 fixed in 1.83.1 | 0.3% 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.