Vulnerability Reporttelegraf:1.40.2-alpine

telegraf:alpinetelegraf:1.40.2-alpinetelegraf:1.40-alpine
digestsha256:4a62bd294bf2f4c1e3781194fe7b625b7e527244eeb31afd5758227914a16229

Executive Summary

Last scanned:

Threat Score
30/100NEEDS ATTENTION
Reputation
TRUSTED

This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main findings are denial-of-service flaws, such as CVE-2026-78669 in golang.org/x/net, that could slow or crash telegraf by exhausting CPU or memory. Each of these needs a non-default HTTP/2 or TLS listener to be turned on, so they do not apply to the default setup. Keeping those listeners disabled removes the path for CVE-2026-78669 entirely. Updating the Go and golang.org/x/net dependencies in a future image build is the practical way to close the remaining findings.

Hardening plan for this image · 3 steps

Included in Pro

Scanning procedure

  1. Vulnerability scan
    Full CVE sweep across OS packages and app dependencies
  2. Exploitability check
    CVEs ranked by exploit probability (EPSS) and matched against CISA KEV
  3. Reachability analysis
    Symbol-level proof: is the vulnerable code even linked and callable in your binaries?
  4. Runtime verification
    Live-container probes: exposed endpoints, feature flags, real defaults
  5. Supply chain analysis
    Base-image lineage, package provenance and signatures — nothing slipped in unnoticed
  6. Hardening recommendations
    A hardened build plan — patch, remove unused packages, lock down the runtime — with parity tests proving nothing broke

Vulnerabilities

Vulnerability Log

21 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-78669MEDIUM6
golang.org/x/net
v0.59.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78659MEDIUM6
golang.org/x/net
v0.59.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78669MEDIUM6
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97031MEDIUM6
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78659MEDIUM6
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-94440MEDIUM6
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-111943MEDIUM5.44
stdlib
v1.27.1
fixed in 1.26.10, 1.27.3
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-94439MEDIUM5.2
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97032MEDIUM4.72
golang.org/x/net
v0.59.0
fixed in 0.60.0
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97032MEDIUM4.72
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78660MEDIUM4.5
golang.org/x/net
v0.59.0
fixed in 0.60.0
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-78667MEDIUM4.5
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78660MEDIUM4.5
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly Exposed
GO-2026-5932MEDIUM4
golang.org/x/crypto
v0.57.0
No fix yet
—
Directly Exposed
CVE-2026-56866LOW3.9
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-94448LOW3.66
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-97030LOW3.66
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-56857LOW3.3
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-78663LOW3.18
golang.org/x/net
v0.59.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-78663LOW3.18
stdlib
v1.27.1
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-114437LOW2.88
github.com/go-chi/chi/v5
v5.3.2
fixed in 5.4.0
0.1%
Theoretical Threat
Directly Exposed

Want to check another image? Run a full scan with the Docker Security Scanner.