| CVE-2026-7210 |
|
High |
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 tri
more...
`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 this patch.
less...
|
3.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.14.5, 3.13.13, 3.14.4, 3.12.13
|
| CVE-2026-6019 |
BDSA-2026-8103 |
Medium |
Apr 22, 2026 |
http.cookies.Morsel.js_output() returns an inline snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sen
more...
http.cookies.Morsel.js_output() returns an inline snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value.
less...
|
3.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.14.5, 3.13.13, 3.14.4, 3.12.13
|
| CVE-2026-4519 |
|
Low |
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
behavio
more...
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().
less...
|
3.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.13.12
|
| CVE-2026-3644 |
|
High |
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 p
more...
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 output validation applied to BaseCookie.output().
less...
|
3.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.13.12
|
| CVE-2026-3087 |
|
High |
Apr 27, 2026 |
If `shutil.unpack_archive()` is given a ZIP archive with an absolute Windows path containing a drive (`C:\\...`) then the archive will be extracted out
more...
If `shutil.unpack_archive()` is given a ZIP archive with an absolute Windows path containing a drive (`C:\\...`) then the archive will be extracted outside the target directory which is different than other operating systems. Only Windows is affected by this vulnerability.
less...
|
3.11.17, 3.10.22, 3.12.15, 3.13.16, 3.11.16, 3.10.21, 3.12.14, 3.13.15, 3.13.14, 3.13.13
|
| 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.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.9.25
|
| CVE-2025-13462 |
|
Low |
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_L
more...
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 other implementations.
less...
|
3.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.13.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.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.9.25
|
| 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.11.17, 3.10.22, 3.12.15, 3.11.16, 3.10.21, 3.12.14, 3.12.13, 3.11.15, 3.10.20, 3.14.1
|
| BDSA-2026-6872 |
|
Medium |
Apr 13, 2026 |
CPython is vulnerable to data integrity issues due to improper handling of excess padding in the `base64.b64decode` function. A remote attacker could e
more...
CPython is vulnerable to data integrity issues due to improper handling of excess padding in the `base64.b64decode` function. A remote attacker could exploit the discrepancies in data processing in order to effect the output of the data decoding.
less...
|
|
