| CVE-2025-13837 |
|
Medium |
Dec 01, 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
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
less...
|
3.12.13, 3.11.15, 3.10.20, 3.9.25, 3.13.9, 3.11.14, 3.10.19, 3.9.24, 3.12.12, 3.13.8
|
| CVE-2025-13836 |
|
High |
Dec 01, 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 maliciou
more...
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.
less...
|
3.12.13, 3.11.15, 3.10.20, 3.13.10, 3.9.25, 3.13.9, 3.11.14, 3.10.19, 3.9.24, 3.12.12
|
| CVE-2025-12781 |
|
Medium |
Jan 21, 2026 |
When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be
more...
When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues.
This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet.
The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64
alphabet they are expecting or verify that their application would not be
affected if the b64decode() functions accepted "+" or "/" outside of altchars.
less...
|
3.12.13, 3.11.15, 3.10.20, 3.9.25, 3.13.9, 3.11.14, 3.10.19, 3.9.24, 3.12.12, 3.13.8
|
| CVE-2025-12084 |
|
Medium |
Dec 03, 2025 |
When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadrati
more...
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.
less...
|
3.12.13, 3.11.15, 3.10.20, 3.14.1, 3.13.10, 3.9.25, 3.13.9, 3.11.14, 3.10.19, 3.9.24
|
| BDSA-2025-13429 |
|
Low |
Oct 08, 2025 |
CPython does not check the validity of ZIP64 End of Central Directory (EOCD) Locator record offset values. Instead of using these values to locate the
more...
CPython does not check the validity of ZIP64 End of Central Directory (EOCD) Locator record offset values. Instead of using these values to locate the ZIP64 EOCD record, it is assumed that it is the previous record in the ZIP archive. This could allow an attacker to craft a ZIP archive which is processed differently to other ZIP implementations, which may result in unexpected behavior.
less...
|
|
| BDSA-2025-1227 |
|
Medium |
Feb 17, 2025 |
The Python (C implementation) `mimetypes` module on Windows uses the same default known file locations as on Linux and macOS platforms. This causes the
more...
The Python (C implementation) `mimetypes` module on Windows uses the same default known file locations as on Linux and macOS platforms. This causes the file to be user-writable, meaning other users can create invalid files to cause a `MemoryError` to be raised on Python runtime startup or have file extensions be interpreted as the incorrect file type.
less...
|
|
| BDSA-2023-1596 |
|
Medium |
Jun 26, 2023 |
Python is vulnerable to denial-of-service (DoS) via an undocumented recursion limit exception when parsing crafted email addresses with the function `p
more...
Python is vulnerable to denial-of-service (DoS) via an undocumented recursion limit exception when parsing crafted email addresses with the function `parseaddr`. A remote attacker could send a crafted email address to a network facing application that uses `parseaddr`. In the worst case, this could crash the application if the exception was not handled gracefully.
**Note:** `email.utils.parseaddr` is categorized as a legacy API in the documentation for the Python email package.
**Note:** The vendor's perspective is that this is neither a vulnerability nor a bug. The email package is intended to have size limits and to throw an exception when limits are exceeded; they were exceeded by the example demonstration code.
less...
|
|
