Vulnerability Reportotel/opentelemetry-collector:0.161.0

otel/opentelemetry-collector:0.161.0
digestsha256:b6d2b9a85b1029d05b5ad913150c1f014eed4ae99be81a1813ca5ade4a191913

Executive Summary

Last scanned:

Threat Score
25/100NEEDS ATTENTION
Reputation
RELIABLE

This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The most relevant finding is CVE-2026-78669, a denial-of-service issue in the HTTP/2 handling used by the collector's gRPC receiver; a malicious client could consume CPU and disrupt telemetry ingestion. There are 15 exposed findings and 4 post-exploit findings, but the maximum exposed severity is 6.38 and no exposed finding reaches 7.0, so the verdict remains NEEDS_ATTENTION. The image's popular community reputation and digest pinning are positive, but the gRPC receiver's HTTP/2 path remains the practical risk to remediate.

Vulnerabilities

Vulnerability Log

19 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-78669MEDIUM6.38
golang.org/x/net
v0.58.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: HIGH
CVE-2026-78669MEDIUM5.1
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97031MEDIUM5.1
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-97032MEDIUM5.02
golang.org/x/net
v0.58.0
fixed in 0.60.0
0.4%
Theoretical Threat
Directly ExposedContext importance: HIGH
CVE-2026-97032MEDIUM4.02
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78663LOW3.6
golang.org/x/net
v0.58.0
fixed in 0.60.0
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-78663LOW3.6
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-56857LOW2.8
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-78667LOW2.29
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-56866LOW1.99
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-94439LOW1.99
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-94448LOW1.87
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.2%
Theoretical Threat
Post-Exploit
GO-2026-5932NONE0
golang.org/x/crypto
v0.56.0
No fix yet
—
Not Applicable
CVE-2026-78659NONE0
golang.org/x/net
v0.58.0
fixed in 0.60.0
0.6%
Theoretical Threat
Not Applicable
CVE-2026-78660NONE0
golang.org/x/net
v0.58.0
fixed in 0.60.0
0.3%
Theoretical Threat
Not Applicable
CVE-2026-78659NONE0
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.6%
Theoretical Threat
Not Applicable
CVE-2026-78660NONE0
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.3%
Theoretical Threat
Not Applicable
CVE-2026-94440NONE0
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.4%
Theoretical Threat
Not Applicable
CVE-2026-97030NONE0
stdlib
v1.26.8
fixed in 1.26.9, 1.27.2
0.2%
Theoretical Threat
Not Applicable

Reachability analysis

Which CVEs are actually reachable — is the vulnerable code even linked and callable.

Locked

Runtime verification

Live-container probes: default user, writable paths, capabilities, exposed ports.

Locked

Supply chain analysis

Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.

Locked

Hardening recommendations

A step-by-step hardened build plan, with parity tests proving nothing breaks.

Locked

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