| CVE-2025-1218 | |
| CVE-2026-6103 | |
| CVE-2026-91769 | |
| CVE-2026-91765 | |
| CVE-2026-91767 | |
| CVE-2026-92842 | |
| CVE-2026-91766 | |
| CVE-2026-93682 | |
| CVE-2026-91768 | |
| CVE-2025-14181 | |
| CVE-2026-14355 | |
| CVE-2026-9672 | |
| CVE-2026-7260 | |
| CVE-2026-17543 | |
| CVE-2026-12184 | |
| CVE-2026-6735 | |
| CVE-2026-6722 | |
| CVE-2024-2757 | |
| CVE-2025-1736 | |
| CVE-2024-8932 | |
| Arbitrary Code Injection | |
| CVE-2024-1874 | |
| CVE-2026-7262 | |
| CVE-2026-7261 | |
| Out-of-bounds Write | |
| CVE-2026-7568 | |
| Integer Overflow or Wraparound | |
| CVE-2024-8929 | |
| CVE-2024-2756 | |
| CVE-2024-3096 | |
| Integer Overflow or Wraparound | |
| CVE-2025-6491 | |
| CVE-2025-1219 | |
| CVE-2025-14180 | |
| CVE-2025-1734 | |
| CVE-2025-14177 | |
| CVE-2025-1861 | |
| CVE-2026-7259 | |
| Use After Free | |
| CVE-2025-1220 | |
| CVE-2025-1735 | |
| CVE-2026-7258 | |
| Interpretation Conflict | |