Vulnerability Reportflink:2.2.1

flink:2.2.1-scala_2.12-java17flink:2.2.1-scala_2.12flink:2.2.1-java17flink:2.2.1flink:2.2-scala_2.12-java17flink:2.2-scala_2.12flink:2.2-java17flink:2.2
digestsha256:c95f48391db3e191345549b4d06406c08616fe8f99ee57fa4f4c44268c912a46

Executive Summary

Last scanned:

Threat Score
3/100SAFE
Reputation
TRUSTED

This image is safe for production use. The scan did find vulnerabilities, including 17 that can be reached from the network in normal operation and 19 that only matter after the container is already compromised, but none are severe enough to change the verdict, with the highest reachable severity at 5.5 and the highest post-compromise severity at 3.3. The image is published by Docker Official and is pinned by digest, which supports confidence in its origin. Routine patching and monitoring as part of normal operations are still advisable.

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

38 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2025-66382MEDIUM5.5
libexpat1
2.6.1-2ubuntu0.6
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-18374MEDIUM4.9
libc-bin
2.39-0ubuntu8.9
No fix yet
0.1%
Theoretical Threat
Directly Exposed
CVE-2026-18374MEDIUM4.9
libc6
2.39-0ubuntu8.9
No fix yet
0.1%
Theoretical Threat
Directly Exposed
CVE-2026-34478MEDIUM4.5
org.apache.logging.log4j:log4j-core
2.24.3
fixed in 2.25.4
1.0%
Theoretical Threat
Directly Exposed
CVE-2026-34479MEDIUM4.5
org.apache.logging.log4j:log4j-core
2.24.3
fixed in 2.25.4
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-34480MEDIUM4.5
org.apache.logging.log4j:log4j-core
2.24.3
fixed in 2.25.4
1.0%
Low-Moderate Risk
Directly Exposed
CVE-2026-34481MEDIUM4.5
org.apache.logging.log4j:log4j-layout-template-json
2.24.3
fixed in 2.25.4
0.7%
Theoretical Threat
Directly Exposed
CVE-2026-89092MEDIUM4.2
libc-bin
2.39-0ubuntu8.9
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-89092MEDIUM4.2
libc6
2.39-0ubuntu8.9
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-89157MEDIUM4.14
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-89158LOW3.9
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-89160LOW3.9
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-49844LOW3.54
org.apache.logging.log4j:log4j-api
2.24.3
fixed in 2.25.5, 2.26.1
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-34477LOW3.54
org.apache.logging.log4j:log4j-core
2.24.3
fixed in 2.25.4
0.6%
Theoretical Threat
Directly Exposed
CVE-2026-102473LOW3.3
dash
0.5.12-6ubuntu5
No fix yet
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-40228LOW3.3
libsystemd0
255.4-1ubuntu8.18
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-40228LOW3.3
libudev1
255.4-1ubuntu8.18
No fix yet
0.2%
Theoretical Threat
Directly Exposed
CVE-2025-68161LOW2.88
org.apache.logging.log4j:log4j-core
2.24.3
fixed in 2.25.3
0.8%
Theoretical Threat
Directly Exposed
CVE-2026-18477LOW2.64
tar
1.35+dfsg-3ubuntu0.4
No fix yet
<0.1%
Theoretical Threat
Post-Exploit
CVE-2026-18508LOW2.64
tar
1.35+dfsg-3ubuntu0.4
No fix yet
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-88647LOW2.48
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-88648LOW2.48
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-103111LOW2.48
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-86145LOW2.48
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-89161LOW2.48
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-107161LOW2.48
libsasl2-2
2.1.28+dfsg1-5ubuntu3.1
No fix yet
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-107161LOW2.48
libsasl2-modules-db
2.1.28+dfsg1-5ubuntu3.1
No fix yet
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-102474LOW2.4
dash
0.5.12-6ubuntu5
No fix yet
0.1%
Theoretical Threat
Post-Exploit
CVE-2021-31879LOW2.2
wget
1.21.4-1ubuntu4.5
No fix yet
1.1%
Low-Moderate Risk
Post-Exploit
CVE-2026-67693LOW2.12
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-89156LOW2.12
libpcre2-8-0
10.42-4ubuntu2.1
No fix yet
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-95184LOW1.91
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2024-56433LOW1.84
login
1:4.13+dfsg1-4ubuntu3.2
No fix yet
0.4%
Theoretical Threat
Post-Exploit
CVE-2024-56433LOW1.84
passwd
1:4.13+dfsg1-4ubuntu3.2
No fix yet
0.4%
Theoretical Threat
Post-Exploit
CVE-2026-95209LOW1.8
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-95210LOW1.8
libgnutls30t64
3.8.3-1.1ubuntu3.6
No fix yet
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-18374NONE0
locales
2.39-0ubuntu8.9
No fix yet
0.1%
Theoretical Threat
Not Applicable
CVE-2026-89092NONE0
locales
2.39-0ubuntu8.9
No fix yet
0.2%
Theoretical Threat
Not Applicable

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