Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main concern is CVE-2026-86145, a memory-corruption flaw in the pcre2 regex library that mongod uses by default to process client queries, so a crafted regex from a network client could possibly lead to code execution on the server. The image also contains 54 exposed-surface findings in total, and none are known to be actively exploited, but they still widen the attack surface and should be tracked. The 16 post-exploit-only findings are low severity and do not change this assessment. Because the container runs as root by default, updating the pcre2 package and running the container with least privilege would reduce the impact of any future exploit.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-86145 | MEDIUM6.9 | libpcre2-8-0 10.46-1build1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-88647 | MEDIUM5.52 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-103111 | MEDIUM5.52 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89161 | MEDIUM5.52 | libpcre2-8-0 10.46-1build1 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-41256 | MEDIUM5.5 | libjq1 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM5.5 | libjq1 1.8.1-4ubuntu2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM5.5 | libjq1 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM5.5 | libjq1 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.2 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-gconv-modules-extra 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.43-2ubuntu2.4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM4.72 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-59869 | MEDIUM4.5 | js-yaml 3.13.1 fixed in 3.15.0, 4.3.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84375 | MEDIUM4.5 | js-yaml 3.13.1 fixed in 4.3.2, 3.15.2 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-5p4m-2wfm-xmqj | MEDIUM4.5 | js-yaml 3.13.1 fixed in 4.3.1, 3.15.1 | — | Directly Exposed |
| CVE-2026-43895 | MEDIUM4.4 | libjq1 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-gconv-modules-extra 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.43-2ubuntu2.4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM4.14 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.14 | libpcre2-8-0 10.46-1build1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | libsasl2-2 2.1.28+dfsg1-9ubuntu3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | libsasl2-modules 2.1.28+dfsg1-9ubuntu3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.14 | libsasl2-modules-db 2.1.28+dfsg1-9ubuntu3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95209 | MEDIUM4 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95210 | MEDIUM4 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GO-2026-5932 | MEDIUM4 | golang.org/x/crypto v0.58.0 No fix yet | — | Directly Exposed |
| CVE-2026-35350 | LOW3.96 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | libpcre2-8-0 10.46-1build1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35360 | LOW3.78 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35364 | LOW3.78 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35374 | LOW3.78 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.26.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW3.54 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35363 | LOW3.36 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW3.3 | dash 0.5.12-12ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW3.3 | jq 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW3.3 | jq 1.8.1-4ubuntu2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW3.3 | jq 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW3.3 | jq 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35348 | LOW3.3 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35373 | LOW3.3 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-61801 | LOW3.3 | github.com/moby/sys/user v0.1.0 fixed in 0.4.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW3.3 | libpcre2-8-0 10.46-1build1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-40228 | LOW3.3 | libsystemd0 259.9-0ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 259.9-0ubuntu0.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.18 | libgnutls30t64 3.8.12-2ubuntu1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-35345 | LOW3.18 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | LOW3.18 | js-yaml 3.13.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53550 | LOW3.18 | js-yaml 3.13.1 fixed in 4.2.0, 3.15.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-35354 | LOW2.82 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35357 | LOW2.82 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35359 | LOW2.82 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43895 | LOW2.64 | jq 1.8.1-4ubuntu2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35370 | LOW2.64 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-4ubuntu0.4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-4ubuntu0.4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35351 | LOW2.52 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35341 | LOW2.48 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35352 | LOW2.48 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35368 | LOW2.48 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.4 | dash 0.5.12-12ubuntu3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39824 | LOW2.4 | golang.org/x/sys v0.1.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35344 | LOW1.98 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35367 | LOW1.98 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35371 | LOW1.98 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35377 | LOW1.98 | rust-coreutils 0.10.0-1ubuntu2~26.04.1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2ubuntu3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.24.6 fixed in 1.26.10, 1.27.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.6 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.2% 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.