Last scanned:
This image is safe for production use. It is a verified Sonatype image pinned by digest, and the provided threat scoring places it in the SAFE band. Although the stats show 14 exposed-surface findings and 2 post-exploit-only findings, their maximum severities are 5.1 and 2.12, with 0 findings at or above severity 6.0 in either group. No top exposed-surface or post-exploit findings are listed in the provided inputs, so there are no CVE-specific issues to call out here. Maintain digest pinning and normal image update hygiene as operational best practice.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-89425 | MEDIUM5.1 | com.fasterxml.jackson.core:jackson-core 2.22.2 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91776 | MEDIUM5.1 | com.fasterxml.jackson.core:jackson-databind 2.22.2 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84939 | MEDIUM5.1 | org.freemarker:freemarker 2.3.32 fixed in 2.3.35 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-75140 | MEDIUM5.1 | org.jsoup:jsoup 1.23.1 fixed in 1.23.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89425 | MEDIUM5.1 | tools.jackson.core:jackson-core 3.2.1 fixed in 3.1.7, 3.2.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-68497 | MEDIUM5.1 | tools.jackson.core:jackson-databind 3.2.1 fixed in 3.2.2, 3.1.6 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91776 | MEDIUM5.1 | tools.jackson.core:jackson-databind 3.2.1 fixed in 3.1.7, 3.2.3 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89407 | MEDIUM4.02 | com.fasterxml.jackson.core:jackson-core 2.22.2 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89407 | MEDIUM4.02 | tools.jackson.core:jackson-core 3.2.1 fixed in 3.1.7, 3.2.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91777 | LOW3.83 | com.fasterxml.jackson.core:jackson-databind 2.22.2 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | LOW3.83 | tools.jackson.core:jackson-databind 3.2.1 fixed in 3.1.7, 3.2.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | LOW2.86 | tools.jackson.core:jackson-databind 3.2.1 fixed in 3.1.6, 3.2.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | LOW2.7 | tools.jackson.core:jackson-databind 3.2.1 fixed in 3.1.6, 3.2.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46675 | LOW2.12 | libpng 1.6.58-r1 fixed in 1.6.59-r0 | — | Post-Exploit |
| CVE-2026-58055 | LOW1.65 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-88807 | NONE0 | libxrender 0.9.12-r0 fixed in 0.9.13-r0 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-88806 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94286 | NONE0 | libxtst 1.2.5-r0 fixed in 1.2.6-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93541 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93542 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93543 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93544 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93545 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94281 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94282 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11 1.8.13-r0 fixed in 1.8.14-r0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109089 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | — | Not Applicable |
| CVE-2026-109090 | NONE0 | libxi 1.8.3-r0 fixed in 1.8.4-r0 | — | Not Applicable |
| CVE-2026-109088 | NONE0 | libxtst 1.2.5-r0 fixed in 1.2.6-r0 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 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.