Follow security updates for vulnerabilities detected and patched in Minimus images.
CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-55831 | neo4j-4.4 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59901 | neo4j-4.4 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59921 | neo4j-4.4 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55833 | neo4j-4.4 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-6790 | neo4j-4.4 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59898 | neo4j-4.4 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-10050 | neo4j-4.4 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56746 | neo4j-4.4 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56745 | neo4j-4.4 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59899 | neo4j-4.4 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-6790 | neo4j-2026.04 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56745 | neo4j-2026.04 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55831 | neo4j-2026.04 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55851 | neo4j-2026.04 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59899 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59898 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-8384 | neo4j-2026.04 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59921 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-10051 | neo4j-2026.04 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59901 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59919 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56746 | neo4j-2026.04 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-10050 | neo4j-2026.04 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55833 | neo4j-2026.04 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56745 | neo4j-2026.03 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-6790 | neo4j-2026.03 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-10051 | neo4j-2026.03 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59921 | neo4j-2026.03 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59899 | neo4j-2026.03 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55831 | neo4j-2026.03 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-8384 | neo4j-2026.03 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59901 | neo4j-2026.03 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-10050 | neo4j-2026.03 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-55833 | neo4j-2026.03 | - | high | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-56746 | neo4j-2026.03 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59898 | neo4j-2026.03 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59901 | neo4j-2026.02 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59899 | neo4j-2026.02 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-8384 | neo4j-2026.02 | - | medium | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |
| CVE-2026-59921 | neo4j-2026.02 | - | unknown | - | Fix not planned | Jul 23, 2026 | Jul 23, 2026 |