p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

python 3.14.4: bekannte Sicherheitslücken · Seite 2

Bekannte Sicherheitslücken für python 3.14.4: 32. Vergleichen Sie die unten genannten Korrekturen mit Ihrer installierten Version.

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 32

  1. CVE-2026-8328

    Mittel · CVSS 5.9EPSS 0,46%Korrektur verfügbar

    FTP PASV SSRF, ftpcp() does not use actual peer address, trusts server-supplied PASV host address

    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-controllable IP address and port to target.sendport(). This patch is related to CVE-2021-4189.

    • Auf 3.14.6 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-7210

    Mittel · CVSS 6.3EPSS 0,67%Korrektur verfügbar

    The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection

    `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.

    • Auf 3.14.6 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-3087

    Mittel · CVSS 6.0EPSS 0,73%Korrektur verfügbar

    shutil.unpack_archive() doesn't check for Windows absolute paths in ZIPs

    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.

    • Auf 3.14.5rc1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-6019

    Niedrig · CVSS 2.1EPSS 0,21%Korrektur verfügbar

    BaseCookie.js_output() does not neutralize embedded characters

    http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value.

    • Auf 3.14.5rc1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-3298

    Hoch · CVSS 8.8EPSS 0,6%Korrektur verfügbar

    Out-of-bounds write in Windows asyncio.ProacterEventLoop.sock_recvfrom_into() when using nbytes

    The method "sock_recvfrom_into()" of "asyncio.ProacterEventLoop" (Windows only) was missing a boundary check for the data buffer when using nbytes parameter. This allowed for an out-of-bounds buffer write if data was larger than the buffer size. Non-Windows platforms are not affected.

    • Auf 3.14.5rc1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-5713

    Mittel · CVSS 5.3EPSS 0,15%Korrektur verfügbar

    Out-of-bounds read/write during remote profiling and asyncio process introspection when connecting to malicious target

    The "profiling.sampling" module (Python 3.15+) and "asyncio introspection capabilities" (3.14+, "python -m asyncio ps" and "python -m asyncio pstree") features could be used to read and write addresses in a privileged process if that process connected to a malicious or "infected" Python process via the remote debugging feature. This vulnerability requires persistently and repeatedly connecting to the process to be exploited, even after the connecting process crashes with high likelihood due to ASLR.

    • Auf 3.14.5 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-4786

    Hoch · CVSS 7.0EPSS 0,29%Korrektur verfügbar

    Incomplete mitigation of CVE-2026-4519, %action expansion for command injection to webbrowser.open()

    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.

    • Auf 3.14.5rc1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-6100

    Kritisch · CVSS 9.1EPSS 0,76%Korrektur verfügbar

    Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure

    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 fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`,

    • Auf 3.14.5rc1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2024-3220

    Niedrig · CVSS 2.3EPSS 0,6%Korrektur verfügbar

    Default mimetype known files writeable on Windows

    There is a defect in the CPython standard library module “mimetypes” where on Windows the default list of known file locations are writable meaning other users can create invalid files to cause MemoryError to be raised on Python runtime startup or have file extensions be interpreted as the incorrect file type. This defect is caused by the default locations of Linux and macOS platforms (such as “/etc/mime.types”) also being used on Windows, where they are user-writable locations (“C:\etc\mime.types”). To work-around this issue a user can call mimetypes.init() with an empty list (“[]”) on Windows platforms to avoid using the default list of k

    • Auf 3.14.9 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →