Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker sending crafted web requests could execute code on the Adminer server and gain access to database credentials that Adminer stores or uses. Both top flaws, CVE-2026-109618 and CVE-2026-109619, are in the PHP runtime and are reachable in the default configuration by anyone who can reach port 8080, since no authentication stands between the network and the request handler. Upgrading PHP to a fixed release is the only complete remediation identified here; no compensating control in the data fully removes these flaws.
Hardening plan for this image · 5 steps. The first closes 2 actively exploited CVEs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-109618 | CRITICAL10 | php 8.4.24 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-109619 | CRITICAL10 | php 8.4.24 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-111497 | MEDIUM6 | brotli-libs 1.2.0-r1 fixed in 1.2.1-r0 | 55.5% Actively Exploited | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-91766 | MEDIUM5.9 | php 8.4.24 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92842 | MEDIUM5.9 | php 8.4.24 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93682 | MEDIUM5.8 | php 8.4.24 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14662 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14664 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14669 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-14670 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14671 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14676 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14677 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14680 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16238 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16239 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19385 | MEDIUM5.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-91767 | MEDIUM5.2 | php 8.4.24 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18408 | MEDIUM5.04 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14668 | MEDIUM4.86 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6464 | MEDIUM4.86 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15741 | MEDIUM4.8 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15742 | MEDIUM4.5 | libpq 18.4-r0 fixed in 18.5-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91765 | MEDIUM4.5 | php 8.4.24 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6471 | MEDIUM4.32 | libpq 18.4-r0 fixed in 18.5-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91769 | MEDIUM4.3 | php 8.4.24 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14679 | MEDIUM4.26 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14663 | LOW3.9 | libpq 18.4-r0 fixed in 18.5-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14181 | LOW3.9 | php 8.4.24 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91768 | LOW3.9 | php 8.4.24 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6103 | LOW3.3 | php 8.4.24 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | LOW3.24 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14672 | LOW3.18 | libpq 18.4-r0 fixed in 18.5-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | LOW2.92 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-82208 | LOW2.88 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.88 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW2.58 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14678 | LOW2.58 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18024 | LOW2.58 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6470 | LOW2.58 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14666 | LOW2.52 | libpq 18.4-r0 fixed in 18.5-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | LOW2.45 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-80256 | LOW2.4 | curl 8.21.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-80256 | LOW2.4 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-14673 | LOW2.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16241 | LOW2.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6469 | LOW2.28 | libpq 18.4-r0 fixed in 18.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW2.22 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.