Last scanned:
··This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The scan found 8 exposed findings, 2 of them rated 6.0 or higher, and none known to be actively exploited. The most notable is CVE-2026-106118 in the ImageSharp library, which could allow heap corruption and possibly code execution, but it only applies if Radarr decodes fax-compressed tiled TIFF images, which is not a normal workflow. CVE-2026-84008 in the cryptography library could cause temporary unavailability through crafted input, though its exposure in Radarr is uncertain. Updating these packages in a future image build is the practical way to reduce the attack surface.
Hardening plan for this image · 3 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-106118 | MEDIUM6 | SixLabors.ImageSharp 3.1.12 fixed in 3.2.0, 4.1.1 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-84008 | MEDIUM6 | System.Security.Cryptography.Pkcs 8.0.1 fixed in 10.0.13, 11.0.0-rc.2, 8.0.2, 9.0.21 | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-70162 | MEDIUM5.9 | System.Security.Cryptography.Pkcs 8.0.1 fixed in 10.0.13, 11.0.0-rc.2, 8.0.2, 9.0.21 | 0.9% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-106110 | MEDIUM4.5 | SixLabors.ImageSharp 3.1.12 fixed in 3.2.0, 4.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106113 | MEDIUM4.5 | SixLabors.ImageSharp 3.1.12 fixed in 3.2.0, 4.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106115 | MEDIUM4.5 | SixLabors.ImageSharp 3.1.12 fixed in 3.2.0, 4.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106114 | LOW3.18 | SixLabors.ImageSharp 3.1.12 fixed in 4.1.2, 3.2.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-106116 | LOW3.18 | SixLabors.ImageSharp 3.1.12 fixed in 3.2.0, 4.1.2 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.