p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

python 3.14.8: bekannte Sicherheitslücken

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

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6

  1. CVE-2026-114583

    Mittel · CVSS 6.9EPSS 0,21%Korrektur verfügbar

    tar filter allows writing outside destination via empty-named symlink

    tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar" to write files outside the destination directory, subject to the permissions of the extracting process. This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.

    • Auf 3.16.0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-12345

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

    Race condition in tempfile.TemporaryDirectory cleanup allows deleting files outside the temporary directory

    The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags reset, with the privileges of the process performing the cleanup. Note that platforms where shutil.rmtree.avoids_symlink_attacks is false, remain affected, and file flags may still be reset outside of the tree on all platforms.

    • Auf 3.14.9 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-87910

    Mittel · CVSS 5.7EPSS 0,5%Korrektur verfügbar

    tarfile hardlink fallback ignores custom extraction filter rejection via None

    When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

    • Auf 3.14.9 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-19672

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

    tarfile extraction filter bypass allows creation of directories outside the destination

    The tarfile module's tar and data extraction filters created directories outside the destination for members whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The containment check used the resolved path, but intermediate directories were created from the name as given. Only empty directories are created outside the destination. Member contents are still extracted inside it. To return to the destination the member's name must contain the destination directory's own final component, so extraction into a secure randomised directory is not affected. This affects POSIX platforms only. On Windows, .. co

    • Auf 3.16.0 aktualisieren
    Veröffentlicht Aktualisiert
  5. 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 →