Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The findings are all denial-of-service flaws rated at most 6.0, and none are known to be actively exploited. Most depend on optional listeners such as HTTP/2 or TLS endpoints that Telegraf only exposes when they are configured, so in a default setup the practical risk is limited to slowed metric intake or a crash under heavy hostile traffic. Note that CVE-2026-78669 only applies if an HTTPS listener is enabled, and CVE-2026-33818 only matters when certificate or TLS-style data is exposed. Keeping those listeners disabled where they are not needed, and updating the Go and x/net packages in a future rebuild, will reduce exposure further.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78669 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33818 | MEDIUM6 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56853 | MEDIUM6 | stdlib v1.26.5 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.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78669 | MEDIUM6 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97031 | MEDIUM6 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78659 | MEDIUM6 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94440 | MEDIUM6 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM5.9 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88018 | MEDIUM5.88 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88044 | MEDIUM5.46 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-111943 | MEDIUM5.44 | stdlib v1.26.5 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78663 | MEDIUM5.3 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94439 | MEDIUM5.2 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-39821 | MEDIUM4.92 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56858 | MEDIUM4.86 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107386 | MEDIUM4.72 | github.com/rabbitmq/amqp091-go v1.13.0 fixed in 1.14.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97032 | MEDIUM4.72 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-88045 | MEDIUM4.5 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56851 | MEDIUM4.5 | golang.org/x/text v0.40.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84445 | MEDIUM4.5 | google.golang.org/grpc v1.84.0-dev.0.20260723093437-b6eac429d7b6 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-46600 | MEDIUM4.5 | stdlib v1.26.5 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM4.5 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM4.5 | stdlib v1.26.5 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78667 | MEDIUM4.5 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78660 | MEDIUM4.5 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88017 | MEDIUM4.38 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78663 | MEDIUM4.24 | golang.org/x/net v0.57.0 fixed in 0.60.0 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-56854 | MEDIUM4.08 | golang.org/x/crypto v0.54.0 fixed in 0.55.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88016 | LOW3.9 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86597 | LOW3.9 | github.com/snowflakedb/gosnowflake v1.19.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56866 | LOW3.9 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88014 | LOW3.78 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94448 | LOW3.66 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97030 | LOW3.66 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81870 | LOW3.3 | go.opentelemetry.io/otel/sdk v1.44.0 fixed in 1.45.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56857 | LOW3.3 | stdlib v1.26.5 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-88015 | LOW3.18 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88046 | LOW3.18 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88013 | LOW3.18 | github.com/rclone/rclone v1.75.0 fixed in 1.75.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56855 | LOW3.18 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78662 | LOW3.18 | golang.org/x/crypto v0.54.0 fixed in 0.56.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-114437 | LOW2.88 | github.com/go-chi/chi/v5 v5.3.1 fixed in 5.4.0 | 0.1% Theoretical Threat | Directly Exposed |
| GO-2026-5932 | LOW2.4 | golang.org/x/crypto v0.54.0 No fix yet | — | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.