| CVE-2026-43706 |
A double free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43707 |
A memory corruption issue was addressed with improved memory handling
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43727 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43731 |
A use-after-free issue was addressed with improved memory management
|
8.8
Élevée
|
29 juin 2026 |
| CVE-2026-43724 |
The issue was addressed with improved input sanitization
|
7.8
Élevée
|
29 juin 2026 |
| CVE-2026-43732 |
A path handling issue was addressed with improved validation
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43708 |
The issue was addressed with improved input validation
|
4.3
Moyenne
|
29 juin 2026 |
| CVE-2026-43712 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43745 |
An out-of-bounds write issue was addressed with improved input validation
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43704 |
A use-after-free issue was addressed with improved memory management
|
5.3
Moyenne
|
29 juin 2026 |
| CVE-2026-43705 |
A type confusion issue was addressed with improved checks
|
8.8
Élevée
|
29 juin 2026 |
| CVE-2026-43713 |
A permissions issue was addressed with additional restrictions
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43709 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43699 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43676 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43725 |
The issue was addressed with improved input validation
|
7.1
Élevée
|
29 juin 2026 |
| CVE-2026-43743 |
A race condition was addressed with improved state handling
|
4.7
Moyenne
|
29 juin 2026 |
| CVE-2026-43734 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43718 |
A stack overflow was addressed with improved input validation
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-28979 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43735 |
The issue was addressed with improved checks
|
8.1
Élevée
|
29 juin 2026 |
| CVE-2026-43703 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43715 |
A use-after-free issue was addressed with improved memory management
|
8.8
Élevée
|
29 juin 2026 |
| CVE-2026-43742 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-28995 |
A logic issue was addressed with improved restrictions
|
8.8
Élevée
|
11 mai 2026 |