p PatchFirst

PatchFirst · Latest vulnerabilities

python3.13 vulnerabilities · Page 2

Vulnerabilities published for python3.13 in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 34

  1. CVE-2025-12781

    Medium · CVSS 6.3EPSS 0.56%No fix published

    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 (w

    Published Updated
  2. CVE-2025-11468

    Medium · CVSS 5.7EPSS 0.62%Fix available

    Folding email comments of unfoldable characters doesn't preserve parenthesis

    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.

    • Update to 3.13.7-1ubuntu0.3
    Published Updated
  3. CVE-2025-13836

    Medium · CVSS 6.3EPSS 1.63%Fix available

    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.

    • Update to 3.13.7-1ubuntu0.2
    Published Updated
  4. CVE-2025-8291

    Medium · CVSS 4.3EPSS 0.47%Fix available

    ZIP64 End of Central Directory (EOCD) Locator record offset not checked

    The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be abused to create ZIP archives that are handled differently by the 'zipfile' module compared to other ZIP implementations. Remediation maintains this behavior, but checks that the offset specified in the ZIP64 EOCD Locator record matches the expected value.

    • Update to 3.13.7-1ubuntu0.1
    Published Updated
  5. CVE-2025-8194

    High · CVSS 7.5EPSS 0.71%Fix available

    Tarfile infinite loop during parsing with negative member offset

    There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives. This vulnerability can be mitigated by including the following patch after importing the “tarfile” module:  https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1

    • Update to 3.13.6-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →