rpm package
suse/python313-core&distro=SUSE Linux Enterprise Server for SAP applications 16.0
pkg:rpm/suse/python313-core&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20applications%2016.0
Vulnerabilities (18)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-4519 | Low | 3.3 | < 3.13.13-160000.1.1 | 3.13.13-160000.1.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-160000.1.1 | 3.13.13-160000.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.13-160000.1.1 | 3.13.13-160000.1.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.13-160000.1.1 | 3.13.13-160000.1.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.13-160000.1.1 | 3.13.13-160000.1.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.13-160000.1.1 | 3.13.13-160000.1.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. | |
| CVE-2026-1299 | Med | — | < 3.13.12-160000.1.1 | 3.13.12-160000.1.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.13.12-160000.1.1 | 3.13.12-160000.1.1 | Jan 20, 2026 | User-controlled header names and values containing newlines can allow injecting HTTP headers. | |
| CVE-2026-0672 | Med | — | < 3.13.12-160000.1.1 | 3.13.12-160000.1.1 | Jan 20, 2026 | When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters. | |
| CVE-2025-15282 | Med | — | < 3.13.12-160000.1.1 | 3.13.12-160000.1.1 | Jan 20, 2026 | User-controlled data URLs parsed by urllib.request.DataHandler allow injecting headers through newlines in the data URL mediatype. | |
| CVE-2025-11468 | Med | — | < 3.13.12-160000.1.1 | 3.13.12-160000.1.1 | Jan 20, 2026 | When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized. | |
| CVE-2025-12084 | — | < 3.13.11-160000.1.1 | 3.13.11-160000.1.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-13836 | Hig | 7.5 | < 3.13.11-160000.1.1 | 3.13.11-160000.1.1 | Dec 1, 2025 | When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS. | |
| CVE-2025-13837 | — | < 3.13.11-160000.1.1 | 3.13.11-160000.1.1 | Dec 1, 2025 | When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues | ||
| CVE-2025-6075 | — | < 3.13.11-160000.1.1 | 3.13.11-160000.1.1 | Oct 31, 2025 | If the value passed to os.path.expandvars() is user-controlled a performance degradation is possible when expanding environment variables. | ||
| CVE-2025-8291 | Med | 4.3 | < 3.13.11-160000.1.1 | 3.13.11-160000.1.1 | Oct 7, 2025 | The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be | |
| CVE-2025-8194 | Hig | 7.5 | < 3.13.11-160000.1.1 | 3.13.11-160000.1.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-6069 | Med | 4.3 | < 3.13.11-160000.1.1 | 3.13.11-160000.1.1 | Jun 17, 2025 | The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service. |
- affected < 3.13.13-160000.1.1fixed 3.13.13-160000.1.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-160000.1.1fixed 3.13.13-160000.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.13-160000.1.1fixed 3.13.13-160000.1.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.13-160000.1.1fixed 3.13.13-160000.1.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.13-160000.1.1fixed 3.13.13-160000.1.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.13-160000.1.1fixed 3.13.13-160000.1.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.
- affected < 3.13.12-160000.1.1fixed 3.13.12-160000.1.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.13.12-160000.1.1fixed 3.13.12-160000.1.1
User-controlled header names and values containing newlines can allow injecting HTTP headers.
- affected < 3.13.12-160000.1.1fixed 3.13.12-160000.1.1
When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.
- affected < 3.13.12-160000.1.1fixed 3.13.12-160000.1.1
User-controlled data URLs parsed by urllib.request.DataHandler allow injecting headers through newlines in the data URL mediatype.
- affected < 3.13.12-160000.1.1fixed 3.13.12-160000.1.1
When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.
- CVE-2025-12084Dec 3, 2025affected < 3.13.11-160000.1.1fixed 3.13.11-160000.1.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.13.11-160000.1.1fixed 3.13.11-160000.1.1
When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.
- CVE-2025-13837Dec 1, 2025affected < 3.13.11-160000.1.1fixed 3.13.11-160000.1.1
When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues
- CVE-2025-6075Oct 31, 2025affected < 3.13.11-160000.1.1fixed 3.13.11-160000.1.1
If the value passed to os.path.expandvars() is user-controlled a performance degradation is possible when expanding environment variables.
- affected < 3.13.11-160000.1.1fixed 3.13.11-160000.1.1
The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be
- affected < 3.13.11-160000.1.1fixed 3.13.11-160000.1.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.13.11-160000.1.1fixed 3.13.11-160000.1.1
The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.