Vulnerability Reporttimberio/vector:nightly-2026-06-17-distroless-libc

timberio/vector:nightly-2026-06-17-distroless-libc
digestsha256:b9dc5f8593a894b8a1d9b178a76ae00e50b9a0766707d5ff79e26897d7402372

Executive Summary

Last scanned:

Threat Score
0/100SAFE
Reputation
TRUSTED

This image is safe for production use. Although 9 exposed and 17 post-exploit vulnerabilities were detected, all are low severity (max CVSS 4.67) and none are exposed in a way that would allow remote exploitation. The image is trusted, verified, and pinned by digest, reducing supply chain risks.

Already in good shape · 2 hardening steps left

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

26 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2022-27943MEDIUM4.67
gcc-12-base
12.2.0-14+deb12u1
No fix yet
0.9%
Theoretical Threat
Directly Exposed
CVE-2022-27943MEDIUM4.67
libgcc-s1
12.2.0-14+deb12u1
No fix yet
0.9%
Theoretical Threat
Directly Exposed
CVE-2022-27943MEDIUM4.67
libgomp1
12.2.0-14+deb12u1
No fix yet
0.9%
Theoretical Threat
Directly Exposed
CVE-2026-7383MEDIUM4.67
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.4%
Theoretical Threat
Directly Exposed
CVE-2022-27943MEDIUM4.67
libstdc++6
12.2.0-14+deb12u1
No fix yet
0.9%
Theoretical Threat
Directly Exposed
CVE-2026-5450MEDIUM4.25
libc6
2.36-9+deb12u14
No fix yet
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-5928MEDIUM4.25
libc6
2.36-9+deb12u14
No fix yet
0.3%
Theoretical Threat
Directly Exposed
CVE-2019-1010022LOW3.53
libc6
2.36-9+deb12u14
No fix yet
3.2%
Low-Moderate Risk
Post-Exploit
CVE-2019-1010023LOW3.17
libc6
2.36-9+deb12u14
No fix yet
3.1%
Low-Moderate Risk
Post-Exploit
CVE-2026-45446LOW3.15
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-45447LOW2.92
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
2.3%
Low-Moderate Risk
Post-Exploit
CVE-2026-45445LOW2.78
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.3%
Theoretical Threat
Post-Exploit
CVE-2018-20796LOW2.7
libc6
2.36-9+deb12u14
No fix yet
5.8%
Low-Moderate Risk
Post-Exploit
CVE-2019-9192LOW2.7
libc6
2.36-9+deb12u14
No fix yet
2.4%
Low-Moderate Risk
Post-Exploit
CVE-2026-34182LOW2.26
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-6238LOW1.99
libc6
2.36-9+deb12u14
No fix yet
0.3%
Theoretical Threat
Post-Exploit
CVE-2019-1010024LOW1.91
libc6
2.36-9+deb12u14
No fix yet
3.2%
Low-Moderate Risk
Post-Exploit
CVE-2019-1010025LOW1.91
libc6
2.36-9+deb12u14
No fix yet
2.3%
Low-Moderate Risk
Post-Exploit
CVE-2026-5435LOW1.81
libc6
2.36-9+deb12u14
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-42770LOW1.81
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-9076LOW1.81
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-42766LOW1.62
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.6%
Theoretical Threat
Post-Exploit
CVE-2026-42767LOW1.62
libssl3
3.0.20-1~deb12u1
No fix yet
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-34180LOW1.53
libssl3
3.0.20-1~deb12u1
fixed in 3.0.20-1~deb12u2
0.5%
Theoretical Threat
Post-Exploit
CVE-2010-4756LOW1.44
libc6
2.36-9+deb12u14
No fix yet
2.6%
Low-Moderate Risk
Post-Exploit
CVE-2025-27587NONE0
libssl3
3.0.20-1~deb12u1
No fix yet
0.4%
Theoretical Threat
Not Applicable

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