Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The official, digest-pinned image is in the NEEDS_ATTENTION band, and the only exposed finding at severity 6.0 is CVE-2019-20838, which only applies if PCRE JIT is enabled, UTF is disabled, and a route regex uses \X or \R with a fixed quantifier greater than 1. In that specific configuration, a crafted request could crash a Kong worker and cause denial of service. Avoiding such regex patterns or ensuring those conditions are not met fully eliminates the CVE-2019-20838 exposure. The remaining exposed and post-exploit-only findings are below severity 6.0 and do not change the production-use verdict.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-20838 | MEDIUM6 | libpcre3 2:8.39-15build1 No fix yet | 2.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.6.1-2ubuntu0.6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.39-0ubuntu8.9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.39-0ubuntu8.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.31 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.01 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-6ubuntu5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW2.8 | libsystemd0 255.4-1ubuntu8.17 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 255.4-1ubuntu8.17 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | LOW2.69 | git 1:2.43.0-1ubuntu7.3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.51 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.39 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-103111 | LOW2.33 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.26 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3ubuntu0.4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-87863 | LOW2.22 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-87863 | LOW2.22 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-6ubuntu5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW1.99 | libpcre2-8-0 10.42-4ubuntu2.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl3t64-gnutls 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl4t64 8.5.0-2ubuntu10.15 No fix yet | — | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.43.0-1ubuntu7.3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-4ubuntu3.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30t64 3.8.3-1.1ubuntu3.6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-2 2.1.28+dfsg1-5ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-modules-db 2.1.28+dfsg1-5ubuntu3.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg-3.1ubuntu2.2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.