| CVE-2025-46313 |
A logging issue was addressed with improved data redaction
|
5.5
Moyenne
|
11 juin 2026 |
| CVE-2025-43278 |
This issue was addressed with improved handling of symlinks
|
5.5
Moyenne
|
11 juin 2026 |
| CVE-2025-46308 |
An authorization issue was addressed with improved state management
|
5.3
Moyenne
|
11 juin 2026 |
| CVE-2025-43451 |
A permissions issue was addressed by removing the vulnerable code
|
5.5
Moyenne
|
26 mai 2026 |
| CVE-2025-46307 |
A logic issue was addressed with improved restrictions
|
5.5
Moyenne
|
26 mai 2026 |
| CVE-2025-46280 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Moyenne
|
26 mai 2026 |
| CVE-2025-43289 |
A logic issue was addressed with improved validation
|
5.5
Moyenne
|
26 mai 2026 |
| CVE-2025-43290 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
26 mai 2026 |
| CVE-2025-43306 |
A logic issue was addressed with improved checks
|
7.8
Élevée
|
26 mai 2026 |
| CVE-2025-46284 |
A race condition was addressed with additional validation
|
7.0
Élevée
|
26 mai 2026 |
| CVE-2026-28976 |
An information leakage was addressed with additional validation
|
7.5
Élevée
|
11 mai 2026 |
| CVE-2026-43653 |
The issue was addressed with improved memory handling
|
6.2
Moyenne
|
11 mai 2026 |
| CVE-2026-28848 |
A buffer overflow was addressed with improved bounds checking
|
7.5
Élevée
|
11 mai 2026 |
| CVE-2026-28995 |
A logic issue was addressed with improved restrictions
|
8.8
Élevée
|
11 mai 2026 |
| CVE-2026-28983 |
A type confusion issue was addressed with improved checks
|
7.5
Élevée
|
11 mai 2026 |
| CVE-2026-28940 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
11 mai 2026 |
| CVE-2026-28917 |
The issue was addressed with improved input validation
|
4.3
Moyenne
|
11 mai 2026 |
| CVE-2026-39869 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
11 mai 2026 |
| CVE-2026-28901 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
11 mai 2026 |
| CVE-2026-28956 |
A memory corruption issue was addressed with improved input validation
|
6.5
Moyenne
|
11 mai 2026 |
| CVE-2026-28941 |
The issue was addressed with improved checks
|
7.1
Élevée
|
11 mai 2026 |
| CVE-2026-28994 |
A use after free issue was addressed with improved memory management
|
5.3
Moyenne
|
11 mai 2026 |
| CVE-2026-43652 |
A permissions issue was addressed with additional restrictions
|
7.5
Élevée
|
11 mai 2026 |
| CVE-2026-43668 |
A use after free issue was addressed with improved memory management
|
7.5
Élevée
|
11 mai 2026 |
| CVE-2026-28936 |
The issue was addressed with improved checks
|
7.5
Élevée
|
11 mai 2026 |