python3.13 - Debian Package Tracker

general

source: python3.13 (main)
version: 3.13.12-1
maintainer: Matthias Klose (DMD)
uploaders: Stefano Rivera [DMD]
arch: all any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

stable: 3.13.5-2+deb13u2
testing: 3.13.12-1
unstable: 3.13.12-1

versioned links

3.13.5-2+deb13u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.13.12-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

idle-python3.13
libpython3.13
libpython3.13-dbg
libpython3.13-dev
libpython3.13-minimal
libpython3.13-stdlib (2 bugs: 0, 2, 0, 0)
libpython3.13-testsuite
python3.13 (5 bugs: 0, 4, 1, 0)
python3.13-dbg (2 bugs: 0, 2, 0, 0)
python3.13-dev
python3.13-doc
python3.13-examples
python3.13-full
python3.13-gdbm (1 bugs: 0, 1, 0, 0)
python3.13-minimal (1 bugs: 0, 0, 1, 0)
python3.13-nopie
python3.13-tk
python3.13-venv

action needed

A new upstream version is available: 3.13.13 high

A new upstream version 3.13.13 is available, you should consider packaging it.

Created: 2026-04-09 Last update: 2026-06-06 08:03

8 security issues in trixie high

There are 8 open security issues in trixie.

2 important issues:

CVE-2026-3276: unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms.
CVE-2026-7774: tarfile.data_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() to write files outside the destination directory, subject to the permissions of the extracting process.

3 issues left for the package maintainer to handle:

CVE-2026-1502: (needs triaging) CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
CVE-2026-7210: (needs triaging) `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.
CVE-2026-8328: (needs triaging) 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.

You can find information about how to handle these issues in the security team's documentation.

3 ignored issues:

CVE-2025-12781: 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.
CVE-2025-15366: The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
CVE-2025-15367: The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

Created: 2025-05-16 Last update: 2026-06-05 07:00

17 security issues in sid high

There are 17 open security issues in sid.

17 important issues:

CVE-2026-1502: CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
CVE-2026-2297: The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
CVE-2026-3276: unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms.
CVE-2026-3446: When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data.
CVE-2026-3644: 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 output validation applied to BaseCookie.output().
CVE-2026-4224: 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-4519: 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-4786: 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.
CVE-2026-6019: 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.
CVE-2026-6100: 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()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
CVE-2026-7210: `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.
CVE-2026-7774: tarfile.data_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() to write files outside the destination directory, subject to the permissions of the extracting process.
CVE-2026-8328: 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.
CVE-2025-12781: 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.
CVE-2025-13462: 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 other implementations.
CVE-2025-15366: The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
CVE-2025-15367: The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

Created: 2026-01-21 Last update: 2026-06-05 07:00

17 security issues in forky high

There are 17 open security issues in forky.

17 important issues:

CVE-2026-1502: CR/LF bytes were not rejected by HTTP client proxy tunnel headers or host.
CVE-2026-2297: The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
CVE-2026-3276: unicodedata.normalize() can take excessive CPU time when processing specially crafted Unicode input containing long runs of combining characters with alternating Canonical Combining Class values. This affects all normalization forms.
CVE-2026-3446: When calling base64.b64decode() or related functions the decoding process would stop after encountering the first padded quad regardless of whether there was more information to be processed. This can lead to data being accepted which may be processed differently by other implementations. Use "validate=True" to enable stricter processing of base64 data.
CVE-2026-3644: 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 output validation applied to BaseCookie.output().
CVE-2026-4224: 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-4519: 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-4786: 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.
CVE-2026-6019: 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.
CVE-2026-6100: 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()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
CVE-2026-7210: `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.
CVE-2026-7774: tarfile.data_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() to write files outside the destination directory, subject to the permissions of the extracting process.
CVE-2026-8328: 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.
CVE-2025-12781: 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.
CVE-2025-13462: 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 other implementations.
CVE-2025-15366: The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
CVE-2025-15367: The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

Created: 2026-01-21 Last update: 2026-06-05 07:00

lintian reports 10 errors and 31 warnings high

Lintian reports 10 errors and 31 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-02-05 Last update: 2026-05-27 03:01

AppStream hints: 1 error and 1 warning for idle-python3.13 high

AppStream found metadata issues for packages:

idle-python3.13: 1 error and 1 warning

You should get rid of them to provide more metadata about this software.

Created: 2024-10-08 Last update: 2024-10-08 17:00

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2026-06-02 Last update: 2026-06-06 12:47

Depends on packages which need a new maintainer normal

The packages that python3.13 depends on which need a new maintainer are:

db5.3 (#1055356)
- Depends: libdb5.3t64 libdb5.3t64
systemtap (#1114760)
- Build-Depends: systemtap-sdt-dev
db-defaults (#1055344)
- Build-Depends: libdb-dev

Created: 2024-05-15 Last update: 2026-06-06 11:02

Multiarch hinter reports 2 issue(s) normal

There are issues with the multiarch metadata for this package.

python3.13-examples could be marked Multi-Arch: foreign
python3.13-gdbm could be marked Multi-Arch: same

Created: 2024-05-15 Last update: 2026-06-06 09:00

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2024-05-31 Last update: 2026-06-06 08:04

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 3.13.13-1, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 08369a8d3096fea5d037969dc76e6c1b541290dd
Author: Stefano Rivera <stefanor@debian.org>
Date:   Tue Jun 2 18:48:10 2026 -0400

    Refresh patches.

commit d31acffd1afe11738d081f80906c837e7c18b123
Author: Stefano Rivera <stefanor@debian.org>
Date:   Tue Jun 2 18:43:29 2026 -0400

    Python 3.13.13.

commit 3829f09ed25d832846a7013780b5816847be46ee
Author: Stefano Rivera <stefanor@debian.org>
Date:   Tue Jun 2 12:58:40 2026 -0400

    Tidy up python3.X-config manpage. Closes: #1101810.

commit 2110556b9afc3a30c1e7ca59dc118e110a71e94d
Author: Stefano Rivera <stefanor@debian.org>
Date:   Tue Jun 2 12:47:25 2026 -0400

    Drop mention of gdbinit from README.debug. Closes: #1109449.

commit 0aee1ba13f03baa3db7a1619d9e248e003d91201
Merge: b3ad752 0ae6384
Author: Stefano Rivera <stefanor@debian.org>
Date:   Mon May 11 13:01:48 2026 +0000

    Merge branch 'drop-libnsl-dev' into 'python3.13'
    
    Drop libnsl-dev build-dependency
    
    See merge request cpython-team/python3!38

commit 0ae63845cf39aa15e36ad5bbd46e49cb2d21978a
Author: Colin Watson <cjwatson@debian.org>
Date:   Tue Jun 17 18:55:07 2025 +0100

    Drop libnsl-dev build-dependency
    
    This was added in Python 3.12 to fix https://bugs.debian.org/1065128.
    However, it's superfluous in Python 3.13 since the nis module was
    dropped as one of the "dead batteries"
    (https://peps.python.org/pep-0594/#nis).

commit b3ad75229fff05df935377788036a62cdacc5c32
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Apr 7 05:37:05 2026 +0200

      * Explicitly build-depend on uuid-dev. LP: #2147343.

Created: 2026-04-07 Last update: 2026-06-03 02:32

9 open merge requests in Salsa normal

There are 9 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-08-19 Last update: 2026-05-11 14:00

debian/patches: 9 patches to forward upstream low

Among the 27 debian patches available in version 3.13.12-1 of the package, we noticed the following issues:

9 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2024-05-15 Last update: 2026-02-05 10:31

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-03-31 15:01

testing migrations

This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2026-05-08] Accepted python3.13 3.13.5-2+deb13u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2026-05-02] Accepted python3.13 3.13.5-2+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2026-02-11] python3.13 3.13.12-1 MIGRATED to testing (Debian testing watch)
[2026-02-04] Accepted python3.13 3.13.12-1 (source) into unstable (Stefano Rivera)
[2025-12-12] python3.13 3.13.11-1 MIGRATED to testing (Debian testing watch)
[2025-12-06] Accepted python3.13 3.13.11-1 (source) into unstable (Stefano Rivera)
[2025-10-22] python3.13 3.13.9-1 MIGRATED to testing (Debian testing watch)
[2025-10-16] Accepted python3.13 3.13.9-1 (source) into unstable (Stefano Rivera)
[2025-10-15] python3.13 3.13.8-1 MIGRATED to testing (Debian testing watch)
[2025-10-09] Accepted python3.13 3.13.8-1 (source) into unstable (Matthias Klose)
[2025-08-28] python3.13 3.13.7-1 MIGRATED to testing (Debian testing watch)
[2025-08-21] Accepted python3.13 3.13.7-1 (source) into unstable (Stefano Rivera)
[2025-08-18] python3.13 3.13.6-1 MIGRATED to testing (Debian testing watch)
[2025-08-10] Accepted python3.13 3.13.6-1 (source) into unstable (Stefano Rivera)
[2025-07-11] python3.13 3.13.5-2 MIGRATED to testing (Debian testing watch)
[2025-06-26] Accepted python3.13 3.13.5-2 (source) into unstable (Stefano Rivera)
[2025-06-12] Accepted python3.13 3.13.5-1 (source) into unstable (Stefano Rivera)
[2025-06-03] Accepted python3.13 3.13.4-1 (source) into unstable (Matthias Klose)
[2025-05-21] Accepted python3.13 3.13.3-4 (source) into unstable (Matthias Klose)
[2025-05-20] Accepted python3.13 3.13.3-3 (source) into unstable (Matthias Klose)
[2025-04-22] python3.13 3.13.3-2 MIGRATED to testing (Debian testing watch)
[2025-04-11] Accepted python3.13 3.13.3-2 (source) into unstable (Stefano Rivera)
[2025-04-09] Accepted python3.13 3.13.3-1 (source) into unstable (Stefano Rivera)
[2025-04-04] python3.13 3.13.2-3 MIGRATED to testing (Debian testing watch)
[2025-03-29] Accepted python3.13 3.13.2-3 (source) into unstable (Matthias Klose)
[2025-03-19] python3.13 3.13.2-2 MIGRATED to testing (Debian testing watch)
[2025-03-13] Accepted python3.13 3.13.2-2 (source) into unstable (Matthias Klose)
[2025-02-11] python3.13 3.13.2-1 MIGRATED to testing (Debian testing watch)
[2025-02-05] Accepted python3.13 3.13.2-1 (source) into unstable (Stefano Rivera)
[2025-01-14] python3.13 3.13.1-3 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 14
RC: 0
I&N: 12
M&W: 2
F&P: 0
patch: 1

links

lintian (10, 31)
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
screenshots
debian patches
debci