rpm package
almalinux/platform-python
pkg:rpm/almalinux/platform-python
Vulnerabilities (44)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-116566 | Med | — | < 3.6.8-80.el8_10.alma.1 | 3.6.8-80.el8_10.alma.1 | Oct 29, 2026 | socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated. | |
| CVE-2026-103995 | Low | — | < 3.6.8-80.el8_10.alma.1 | 3.6.8-80.el8_10.alma.1 | Oct 27, 2026 | Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents. | |
| CVE-2026-114583 | Med | — | < 3.6.8-80.el8_10.alma.1 | 3.6.8-80.el8_10.alma.1 | Oct 22, 2026 | tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar | |
| CVE-2026-19553 | Hig | — | < 3.6.8-79.el8_10.alma.1 | 3.6.8-79.el8_10.alma.1 | Sep 30, 2026 | ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set. Due to a missing parameter check in SSLObject, if the server_hostname argument isn't supplied then hostname verification would be silently skipped. Thi | |
| CVE-2026-19445 | Cri | — | < 3.6.8-79.el8_10.alma.1 | 3.6.8-79.el8_10.alma.1 | Sep 30, 2026 | A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. | |
| CVE-2026-12345 | Med | — | < 3.6.8-79.el8_10.alma.1 | 3.6.8-79.el8_10.alma.1 | Sep 29, 2026 | The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags r | |
| CVE-2026-15308 | Hig | 7.5 | < 3.6.8-77.el8_10.alma.1 | 3.6.8-77.el8_10.alma.1 | Jul 9, 2026 | The incremental HTML parser (html.parser.HTMLParser) allows for CPU denial-of-service through repeated unterminated markup declarations when processing uncontrolled data. | |
| CVE-2026-11940 | Hig | — | < 3.6.8-78.el8_10.alma.1 | 3.6.8-78.el8_10.alma.1 | Jun 23, 2026 | tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself. The extraction fallback validated the symlink at it's archived location but recreated it at the | |
| CVE-2026-4786 | Hig | 7.1 | < 3.6.8-76.el8_10.alma.1 | 3.6.8-76.el8_10.alma.1 | Apr 13, 2026 | Mitgation of CVE-2026-4519 was incomplete. If the URL contained "%action" the mitigation could be bypassed for certain browser types the "webbrowser.open()" API could have commands injected into the underlying shell. See CVE-2026-4519 for details. | |
| CVE-2026-6100 | Hig | 8.1 | < 3.6.8-76.el8_10.alma.1 | 3.6.8-76.el8_10.alma.1 | Apr 13, 2026 | 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 | |
| CVE-2026-4519 | Low | 3.3 | < 3.6.8-75.el8_10.alma.1 | 3.6.8-75.el8_10.alma.1 | Mar 20, 2026 | The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open(). | |
| CVE-2026-1299 | Med | — | < 3.6.8-73.el8_10.alma.1 | 3.6.8-73.el8_10.alma.1 | Jan 23, 2026 | The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't | |
| CVE-2026-0865 | Med | — | < 3.6.8-73.el8_10.alma.1 | 3.6.8-73.el8_10.alma.1 | Jan 20, 2026 | User-controlled header names and values containing newlines can allow injecting HTTP headers. | |
| CVE-2025-15367 | Med | — | < 3.6.8-73.el8_10.alma.1 | 3.6.8-73.el8_10.alma.1 | Jan 20, 2026 | The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. | |
| CVE-2025-15366 | Med | — | < 3.6.8-73.el8_10.alma.1 | 3.6.8-73.el8_10.alma.1 | Jan 20, 2026 | The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters. | |
| CVE-2025-12084 | Med | 5.3 | < 3.6.8-72.el8_10.alma.1 | 3.6.8-72.el8_10.alma.1 | Dec 3, 2025 | When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadratic. Availability can be impacted when building excessively nested documents. | |
| CVE-2025-8194 | Hig | 7.5 | < 3.6.8-71.el8_10.alma.1 | 3.6.8-71.el8_10.alma.1 | Jul 28, 2025 | There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously cra | |
| CVE-2025-4517 | Cri | 9.4 | < 3.6.8-70.el8_10.alma.1 | 3.6.8-70.el8_10.alma.1 | Jun 3, 2025 | Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= param | |
| CVE-2025-4435 | Hig | 7.5 | < 3.6.8-70.el8_10.alma.1 | 3.6.8-70.el8_10.alma.1 | Jun 3, 2025 | When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not | |
| CVE-2025-4330 | Hig | 7.5 | < 3.6.8-70.el8_10.alma.1 | 3.6.8-70.el8_10.alma.1 | Jun 3, 2025 | Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac |
- affected < 3.6.8-80.el8_10.alma.1fixed 3.6.8-80.el8_10.alma.1
socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated.
- affected < 3.6.8-80.el8_10.alma.1fixed 3.6.8-80.el8_10.alma.1
Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents.
- affected < 3.6.8-80.el8_10.alma.1fixed 3.6.8-80.el8_10.alma.1
tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar
- affected < 3.6.8-79.el8_10.alma.1fixed 3.6.8-79.el8_10.alma.1
ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set. Due to a missing parameter check in SSLObject, if the server_hostname argument isn't supplied then hostname verification would be silently skipped. Thi
- affected < 3.6.8-79.el8_10.alma.1fixed 3.6.8-79.el8_10.alma.1
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive.
- affected < 3.6.8-79.el8_10.alma.1fixed 3.6.8-79.el8_10.alma.1
The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags r
- affected < 3.6.8-77.el8_10.alma.1fixed 3.6.8-77.el8_10.alma.1
The incremental HTML parser (html.parser.HTMLParser) allows for CPU denial-of-service through repeated unterminated markup declarations when processing uncontrolled data.
- affected < 3.6.8-78.el8_10.alma.1fixed 3.6.8-78.el8_10.alma.1
tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself. The extraction fallback validated the symlink at it's archived location but recreated it at the
- affected < 3.6.8-76.el8_10.alma.1fixed 3.6.8-76.el8_10.alma.1
Mitgation of CVE-2026-4519 was incomplete. If the URL contained "%action" the mitigation could be bypassed for certain browser types the "webbrowser.open()" API could have commands injected into the underlying shell. See CVE-2026-4519 for details.
- affected < 3.6.8-76.el8_10.alma.1fixed 3.6.8-76.el8_10.alma.1
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
- affected < 3.6.8-75.el8_10.alma.1fixed 3.6.8-75.el8_10.alma.1
The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().
- affected < 3.6.8-73.el8_10.alma.1fixed 3.6.8-73.el8_10.alma.1
The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't
- affected < 3.6.8-73.el8_10.alma.1fixed 3.6.8-73.el8_10.alma.1
User-controlled header names and values containing newlines can allow injecting HTTP headers.
- affected < 3.6.8-73.el8_10.alma.1fixed 3.6.8-73.el8_10.alma.1
The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
- affected < 3.6.8-73.el8_10.alma.1fixed 3.6.8-73.el8_10.alma.1
The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
- affected < 3.6.8-72.el8_10.alma.1fixed 3.6.8-72.el8_10.alma.1
When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadratic. Availability can be impacted when building excessively nested documents.
- affected < 3.6.8-71.el8_10.alma.1fixed 3.6.8-71.el8_10.alma.1
There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously cra
- affected < 3.6.8-70.el8_10.alma.1fixed 3.6.8-70.el8_10.alma.1
Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= param
- affected < 3.6.8-70.el8_10.alma.1fixed 3.6.8-70.el8_10.alma.1
When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not
- affected < 3.6.8-70.el8_10.alma.1fixed 3.6.8-70.el8_10.alma.1
Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac
Page 1 of 3