Approved changes feed: RSS · Atom

cpe:2.3:a:python:python:3.15.0:alpha1:*:*:*:*:*:*

part: a version: 3.15.0 update: alpha1

VendorPython (b57ad93a-6195-5192-9423-6cfad6044a8b)
ProductPython (fc328eef-0a85-5ddb-b629-b8866ec518c8)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/python purl2cpe 2026-06-01 10:16:29.357718
pkg:github/python/cpython purl2cpe 2026-06-01 10:16:29.357719
pkg:python/python purl2cpe 2026-06-01 10:16:29.357721
pkg:rpm/opensuse/python purl2cpe 2026-06-01 10:16:29.357722

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-4519 vulnerable 2026-06-03 15:26:25.612687 webbrowser.open() allows leading dashes in URLs
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().
Published: 2026-03-20T15:08:32.576Z
Updated: 2026-04-13T21:47:40.137Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-6075 vulnerable 2026-06-03 15:12:26.625033 Quadratic complexity in os.path.expandvars() with user-controlled template
If the value passed to os.path.expandvars() is user-controlled a performance degradation is possible when expanding environment variables.
Published: 2025-10-31T16:41:34.983Z
Updated: 2026-03-03T14:43:01.737Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-13837 vulnerable 2026-06-03 14:58:53.763096 Out-of-memory when loading Plist
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
Published: 2025-12-01T18:13:32.739Z
Updated: 2026-03-03T14:41:54.597Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-13836 vulnerable 2026-06-03 14:58:53.761829 Excessive read buffering DoS in http.client
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.
Published: 2025-12-01T18:02:38.483Z
Updated: 2026-03-03T14:41:48.702Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-12781 vulnerable 2026-06-03 14:58:44.851485 base64.b64decode() always accepts "+/" characters, despite setting altchars
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.
Published: 2026-01-21T19:34:47.979Z
Updated: 2026-01-22T20:12:56.421Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-12084 vulnerable 2026-06-03 14:58:43.770013 Quadratic complexity in node ID cache clearing
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.
Published: 2025-12-03T18:55:32.222Z
Updated: 2026-03-03T14:41:38.821Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.