VYPR

rpm package

suse/python3&distro=SUSE Linux Enterprise Server 12 SP5-LTSS

pkg:rpm/suse/python3&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP5-LTSS

Vulnerabilities (18)

  • CVE-2026-4519LowMar 20, 2026
    affected < 3.4.10-25.180.1fixed 3.4.10-25.180.1

    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().

  • CVE-2026-3479NonMar 18, 2026
    affected < 3.4.10-25.180.1fixed 3.4.10-25.180.1

    DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security mode

  • CVE-2026-4224HigMar 16, 2026
    affected < 3.4.10-25.180.1fixed 3.4.10-25.180.1

    When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs.

  • CVE-2026-3644HigMar 16, 2026
    affected < 3.4.10-25.180.1fixed 3.4.10-25.180.1

    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 ou

  • CVE-2025-13462LowMar 12, 2026
    affected < 3.4.10-25.180.1fixed 3.4.10-25.180.1

    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 ot

  • CVE-2026-1299MedJan 23, 2026
    affected < 3.4.10-25.175.1fixed 3.4.10-25.175.1

    The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't

  • CVE-2026-0865MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    User-controlled header names and values containing newlines can allow injecting HTTP headers.

  • CVE-2026-0672MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.

  • CVE-2025-15367MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

  • CVE-2025-15366MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

  • CVE-2025-15282MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    User-controlled data URLs parsed by urllib.request.DataHandler allow injecting headers through newlines in the data URL mediatype.

  • CVE-2025-11468MedJan 20, 2026
    affected < 3.4.10-25.172.1fixed 3.4.10-25.172.1

    When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.

  • CVE-2025-4517CriJun 3, 2025
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= param

  • CVE-2025-4435HigJun 3, 2025
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not

  • CVE-2025-4330HigJun 3, 2025
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac

  • CVE-2025-4138HigJun 3, 2025
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac

  • CVE-2024-12718MedJun 3, 2025
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    Allows modifying some file metadata (e.g. last modified) with filter="data" or file permissions (chmod) with filter="tar" of files outside the extraction directory. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.

  • CVE-2007-4559CriAug 28, 2007
    affected < 3.4.10-25.169.1fixed 3.4.10-25.169.1

    Directory traversal vulnerability in the (1) extract and (2) extractall functions in the tarfile module in Python allows user-assisted remote attackers to overwrite arbitrary files via a .. (dot dot) sequence in filenames in a TAR archive, a related issue to CVE-2001-1267.