| CVE-2026-112637 |
A use-after-free issue was addressed with improved memory management
|
8.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112565 |
An integer overflow was addressed with improved input validation
|
7.5
Élevée
|
26 oct. 2026 |
| CVE-2026-86969 |
An out-of-bounds write was addressed with improved input validation
|
7.5
Élevée
|
26 oct. 2026 |
| CVE-2026-112477 |
A race condition was addressed with improved locking
|
7.0
Élevée
|
26 oct. 2026 |
| CVE-2026-86986 |
A use-after-free issue was addressed with improved memory management
|
7.5
Élevée
|
26 oct. 2026 |
| CVE-2026-113909 |
A memory corruption issue was addressed with improved input validation
|
8.0
Élevée
|
26 oct. 2026 |
| CVE-2026-86990 |
An access issue was addressed with improved access restrictions
|
5.1
Moyenne
|
26 oct. 2026 |
| CVE-2026-112461 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112695 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
26 oct. 2026 |
| CVE-2026-112416 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112683 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112705 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-113952 |
A logic issue was addressed with improved checks
|
5.4
Moyenne
|
26 oct. 2026 |
| CVE-2026-112640 |
A use-after-free issue was addressed with improved memory management
|
7.6
Élevée
|
26 oct. 2026 |
| CVE-2026-113913 |
An input validation issue was addressed with improved input validation
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-86973 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112656 |
An out-of-bounds read was addressed with improved bounds checking
|
3.3
Faible
|
26 oct. 2026 |
| CVE-2026-64750 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-86978 |
This issue was addressed with improved checks
|
3.3
Faible
|
26 oct. 2026 |
| CVE-2026-112466 |
An out-of-bounds read was addressed with improved input validation
|
7.1
Élevée
|
26 oct. 2026 |
| CVE-2026-112470 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
Élevée
|
26 oct. 2026 |
| CVE-2026-112630 |
An uninitialized memory issue was addressed with improved memory handling
|
3.3
Faible
|
26 oct. 2026 |
| CVE-2026-86942 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Moyenne
|
26 oct. 2026 |
| CVE-2026-112688 |
A memory corruption issue was addressed with improved memory handling
|
8.8
Élevée
|
26 oct. 2026 |
| CVE-2026-84494 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.1
Élevée
|
26 oct. 2026 |