Vulnerability Reportprom/node-exporter:v1.12.1

prom/node-exporter:latestprom/node-exporter:v1prom/node-exporter:v1-busyboxprom/node-exporter:latest-busyboxprom/node-exporter:v1.12.1prom/node-exporter:v1.12.1-busybox
digestsha256:1b4e4438faca4dd7e001dd445d161a4a2091b0fededa84093b3a8dfeae1f1be0

Executive Summary

Last scanned:

Threat Score
32/100NEEDS ATTENTION
Reputation
RELIABLE

This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The findings are denial-of-service issues, meaning the worst outcome is slowed or stalled metric scrapes and exporter memory or CPU exhaustion, not data theft or code execution. Note: CVE-2026-78669 and CVE-2026-56862 only apply when TLS or HTTP/2 is enabled in the exporter's web config, which is not the default, so keeping the default plain-HTTP setup avoids those paths. Upgrading the Go standard library and golang.org/x/net packages to fixed versions is the practical way to clear these seven medium-severity 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

32 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-78669MEDIUM6
golang.org/x/net
v0.57.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78659MEDIUM6
golang.org/x/net
v0.57.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-56853MEDIUM6
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-56862MEDIUM6
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-78669MEDIUM6
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97031MEDIUM6
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78659MEDIUM6
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97032MEDIUM5.9
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78663MEDIUM5.3
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-94439MEDIUM5.2
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-39821MEDIUM4.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-56858MEDIUM4.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-97032MEDIUM4.72
golang.org/x/net
v0.57.0
fixed in 0.60.0
0.5%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78660MEDIUM4.5
golang.org/x/net
v0.57.0
fixed in 0.60.0
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-56851MEDIUM4.5
golang.org/x/text
v0.40.0
fixed in 0.41.0
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-33818MEDIUM4.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-46600MEDIUM4.5
stdlib
v1.26.5
fixed in 1.26.6, 1.27.0-rc.3
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-56859MEDIUM4.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-56860MEDIUM4.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-78667MEDIUM4.5
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78660MEDIUM4.5
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-94440MEDIUM4.5
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78663MEDIUM4.24
golang.org/x/net
v0.57.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-56854MEDIUM4.08
golang.org/x/crypto
v0.54.0
fixed in 0.55.0
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-111943MEDIUM4.08
stdlib
v1.26.5
fixed in 1.26.10, 1.27.3
0.4%
Theoretical Threat
Directly Exposed
CVE-2026-94448LOW3.66
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-97030LOW3.66
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-56857LOW3.3
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-56855LOW3.18
golang.org/x/crypto
v0.54.0
fixed in 0.56.0
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78662LOW3.18
golang.org/x/crypto
v0.54.0
fixed in 0.56.0
0.4%
Theoretical Threat
Directly Exposed
GO-2026-5932LOW2.4
golang.org/x/crypto
v0.54.0
No fix yet
—
Directly Exposed
CVE-2026-56866LOW2.34
stdlib
v1.26.5
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Post-Exploit

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