Количество 82
Количество 82
SUSE-SU-2026:1937-1
Security update for python3
openSUSE-SU-2026:21459-1
Security update for python313, python3
SUSE-SU-2026:2387-1
Security update for python
SUSE-SU-2026:1818-1
Security update for python39
SUSE-SU-2026:2664-1
Security update for python, python-base, python-doc
RLSA-2026:19176
Important: python3.14 security update
RLSA-2026:19019
Important: python3.14 security update
ELSA-2026-19176
ELSA-2026-19176: python3.14 security update (IMPORTANT)
ELSA-2026-19019
ELSA-2026-19019: python3.14 security update (IMPORTANT)
SUSE-SU-2026:1715-1
Security update for python3
RLSA-2026:10950
Important: python3.12 security update
ELSA-2026-10950
ELSA-2026-10950: python3.12 security update (IMPORTANT)
RLSA-2026:19177
Important: python3.12 security update
RLSA-2026:19064
Important: python3.12 security update
ELSA-2026-19177
ELSA-2026-19177: python3.12 security update (IMPORTANT)
ELSA-2026-19064
ELSA-2026-19064: python3.12 security update (IMPORTANT)
CVE-2026-6100
Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
CVE-2026-6100
Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
CVE-2026-6100
Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
CVE-2026-6100
Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | SUSE-SU-2026:1937-1 Security update for python3 | 4 месяца назад | ||
| openSUSE-SU-2026:21459-1 Security update for python313, python3 | около 2 месяцев назад | ||
| SUSE-SU-2026:2387-1 Security update for python | 3 месяца назад | ||
| SUSE-SU-2026:1818-1 Security update for python39 | 4 месяца назад | ||
| SUSE-SU-2026:2664-1 Security update for python, python-base, python-doc | 3 месяца назад | ||
 | RLSA-2026:19176 Important: python3.14 security update | 4 месяца назад | ||
| RLSA-2026:19019 Important: python3.14 security update | 4 месяца назад | ||
| ELSA-2026-19176 ELSA-2026-19176: python3.14 security update (IMPORTANT) | 3 месяца назад | ||
| ELSA-2026-19019 ELSA-2026-19019: python3.14 security update (IMPORTANT) | 2 месяца назад | ||
| SUSE-SU-2026:1715-1 Security update for python3 | 4 месяца назад | ||
| RLSA-2026:10950 Important: python3.12 security update | 5 месяцев назад | ||
| ELSA-2026-10950 ELSA-2026-10950: python3.12 security update (IMPORTANT) | 5 месяцев назад | ||
| RLSA-2026:19177 Important: python3.12 security update | 4 месяца назад | ||
| RLSA-2026:19064 Important: python3.12 security update | 4 месяца назад | ||
| ELSA-2026-19177 ELSA-2026-19177: python3.12 security update (IMPORTANT) | 3 месяца назад | ||
| ELSA-2026-19064 ELSA-2026-19064: python3.12 security update (IMPORTANT) | 2 месяца назад | ||
 | CVE-2026-6100 Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable. | CVSS3: 8.1 | 1% Низкий | 5 месяцев назад |
 | CVE-2026-6100 Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable. | CVSS3: 8.1 | 1% Низкий | 5 месяцев назад |
 | CVE-2026-6100 Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable. | CVSS3: 8.1 | 1% Низкий | 5 месяцев назад |
 | CVE-2026-6100 Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure | CVSS3: 8.1 | 1% Низкий | 3 месяца назад |
Уязвимостей на страницу