Follow security updates for vulnerabilities detected and patched in Minimus images.
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-55798 | litellm-1.82 | medium | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54060 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59198 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59875 | litellm-1.82 | medium | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59873 | litellm-1.82 | critical | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59205 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59203 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54059 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59204 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59871 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59200 | litellm-1.82 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54060 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59200 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59873 | litellm-1.81 | critical | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59199 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-55379 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-13149 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-55798 | litellm-1.81 | medium | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59874 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59205 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59871 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59198 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54059 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54058 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59875 | litellm-1.81 | medium | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59203 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59197 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-55380 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59204 | litellm-1.81 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59200 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-55798 | litellm-1.80 | medium | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-13149 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59204 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-55379 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59197 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59873 | litellm-1.80 | critical | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54060 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59874 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-54058 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 | |
| CVE-2026-59199 | litellm-1.80 | high | - | Fix not planned | Jul 21, 2026 | Jul 21, 2026 |