rpm package
opensuse/python313&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/python313&distro=openSUSE%20Tumbleweed
Vulnerabilities (75)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-15308 | Hig | 7.5 | < 3.13.14-2.1 | 3.13.14-2.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-4360 | Med | 5.3 | < 3.13.14-2.1 | 3.13.14-2.1 | Jun 30, 2026 | In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract( | |
| CVE-2026-11972 | Hig | — | < 3.13.14-2.1 | 3.13.14-2.1 | Jun 23, 2026 | When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly handle EOF, making archive parsing take exponentially longer. | |
| CVE-2026-0864 | Med | 5.5 | < 3.13.14-2.1 | 3.13.14-2.1 | Jun 23, 2026 | When using the "configparser" module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value. | |
| CVE-2026-11940 | Hig | — | < 3.13.14-1.1 | 3.13.14-1.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-7774 | Med | — | < 3.13.14-2.1 | 3.13.14-2.1 | Jun 4, 2026 | tarfile.data_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() to write files | |
| CVE-2026-3276 | Med | — | < 3.13.14-2.1 | 3.13.14-2.1 | Jun 3, 2026 | unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms. | |
| CVE-2026-8328 | Med | — | < 3.13.14-1.1 | 3.13.14-1.1 | May 13, 2026 | The ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV host addresses with the actual peer address (getpeername()[0]), ftpcp() still calls parse227() directly and passes the raw attacker | |
| CVE-2026-7210 | Hig | 7.5 | < 3.13.14-1.1 | 3.13.14-1.1 | May 11, 2026 | `xml.parsers.expat` and `xml.etree.ElementTree` use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying thi | |
| CVE-2026-6019 | Med | 6.1 | < 3.13.13-2.1 | 3.13.13-2.1 | Apr 22, 2026 | http.cookies.Morsel.js_output() returns an inline inside the generated script element. Mitigation base64-encodes the cookie value to disallow esc | |
| CVE-2026-4786 | Hig | 7.1 | < 3.13.13-2.1 | 3.13.13-2.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.13.13-2.1 | 3.13.13-2.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-3446 | Med | — | < 3.13.13-2.1 | 3.13.13-2.1 | Apr 10, 2026 | When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other impleme | |
| CVE-2026-1502 | Med | — | < 3.13.13-2.1 | 3.13.13-2.1 | Apr 10, 2026 | CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host. | |
| CVE-2026-4519 | Low | 3.3 | < 3.13.12-3.1 | 3.13.12-3.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-3479 | Non | — | < 3.13.13-1.1 | 3.13.13-1.1 | Mar 18, 2026 | DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security mode | |
| CVE-2026-4224 | Hig | 7.5 | < 3.13.12-3.1 | 3.13.12-3.1 | Mar 16, 2026 | When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs. | |
| CVE-2026-3644 | Hig | 7.5 | < 3.13.12-3.1 | 3.13.12-3.1 | Mar 16, 2026 | The fix for CVE-2026-0672, which rejected control characters in http.cookies.Morsel, was incomplete. The Morsel.update(), |= operator, and unpickling paths were not patched, allowing control characters to bypass input validation. Additionally, BaseCookie.js_output() lacked the ou | |
| CVE-2025-13462 | Low | 3.3 | < 3.13.12-3.1 | 3.13.12-3.1 | Mar 12, 2026 | The "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to ot | |
| CVE-2026-2297 | Med | — | < 3.13.12-2.1 | 3.13.12-2.1 | Mar 4, 2026 | The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire. |
- affected < 3.13.14-2.1fixed 3.13.14-2.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.13.14-2.1fixed 3.13.14-2.1
In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract(
- affected < 3.13.14-2.1fixed 3.13.14-2.1
When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly handle EOF, making archive parsing take exponentially longer.
- affected < 3.13.14-2.1fixed 3.13.14-2.1
When using the "configparser" module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.
- affected < 3.13.14-1.1fixed 3.13.14-1.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.13.14-2.1fixed 3.13.14-2.1
tarfile.data_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() to write files
- affected < 3.13.14-2.1fixed 3.13.14-2.1
unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms.
- affected < 3.13.14-1.1fixed 3.13.14-1.1
The ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV host addresses with the actual peer address (getpeername()[0]), ftpcp() still calls parse227() directly and passes the raw attacker
- affected < 3.13.14-1.1fixed 3.13.14-1.1
`xml.parsers.expat` and `xml.etree.ElementTree` use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or later and applying thi
- affected < 3.13.13-2.1fixed 3.13.13-2.1
http.cookies.Morsel.js_output() returns an inline inside the generated script element. Mitigation base64-encodes the cookie value to disallow esc
- affected < 3.13.13-2.1fixed 3.13.13-2.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.13.13-2.1fixed 3.13.13-2.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.13.13-2.1fixed 3.13.13-2.1
When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other impleme
- affected < 3.13.13-2.1fixed 3.13.13-2.1
CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
- affected < 3.13.12-3.1fixed 3.13.12-3.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.13.13-1.1fixed 3.13.13-1.1
DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security mode
- affected < 3.13.12-3.1fixed 3.13.12-3.1
When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs.
- affected < 3.13.12-3.1fixed 3.13.12-3.1
The fix for CVE-2026-0672, which rejected control characters in http.cookies.Morsel, was incomplete. The Morsel.update(), |= operator, and unpickling paths were not patched, allowing control characters to bypass input validation. Additionally, BaseCookie.js_output() lacked the ou
- affected < 3.13.12-3.1fixed 3.13.12-3.1
The "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to ot
- affected < 3.13.12-2.1fixed 3.13.12-2.1
The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
Page 1 of 4