| CVE-2026-112685 |
An authorization issue was addressed with improved state management
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112514 |
A use-after-free issue was addressed with improved memory management
|
9.1
Critique
|
26 oct. 2026 |
| CVE-2026-113915 |
A race condition was addressed with additional validation
|
4.7
Moyenne
|
26 oct. 2026 |
| CVE-2026-112596 |
An integer overflow was addressed with improved bounds checking
|
Non notée
|
26 oct. 2026 |
| CVE-2026-84495 |
A use-after-free issue was addressed with improved memory management
|
7.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112666 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
26 oct. 2026 |
| CVE-2026-112689 |
An out-of-bounds write issue was addressed with improved input validation
|
8.4
Élevée
|
26 oct. 2026 |
| CVE-2026-112518 |
An issue with signature validation was addressed with improved checks
|
6.3
Moyenne
|
26 oct. 2026 |
| CVE-2026-112563 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112665 |
An information disclosure issue was addressed with improved state management
|
3.3
Faible
|
26 oct. 2026 |
| CVE-2026-112425 |
An out-of-bounds read was addressed with improved bounds checking
|
3.3
Faible
|
26 oct. 2026 |
| CVE-2026-112560 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112464 |
An out-of-bounds write issue was addressed with improved input validation
|
7.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112608 |
An out-of-bounds read was addressed with improved bounds checking
|
4.3
Moyenne
|
26 oct. 2026 |
| CVE-2026-112599 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112576 |
A memory integrity issue was addressed with improved handling of copy-on-write pages
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112501 |
A race condition was addressed with improved state handling
|
6.2
Moyenne
|
26 oct. 2026 |
| CVE-2026-112686 |
A race condition was addressed with improved locking
|
3.1
Faible
|
26 oct. 2026 |
| CVE-2026-112669 |
A race condition was addressed with improved state handling
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112517 |
A use after free issue was addressed with improved memory management
|
7.7
Élevée
|
26 oct. 2026 |
| CVE-2026-112491 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112468 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112595 |
This issue was addressed with improved authentication
|
7.5
Élevée
|
26 oct. 2026 |
| CVE-2026-112469 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.5
Élevée
|
26 oct. 2026 |
| CVE-2026-112516 |
A use-after-free issue was addressed with improved memory management
|
6.2
Moyenne
|
26 oct. 2026 |