python3.14 - Debian Package Tracker

general

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

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

[pool directory]

testing: 3.14.6-1
unstable: 3.14.7-1
exp: 3.14.7-2

versioned links

3.14.6-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.14.7-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.14.7-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

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

action needed

7 security issues in sid high

There are 7 open security issues in sid.

7 important 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.
CVE-2026-15310: When decompressing crafted zip files using the bzip/LZMA/Zstandard compressions, Python could use an attacker-controlled size to pre-allocate memory, possibly resulting in memory exhaustion.
CVE-2026-15806: The HTTPPasswordMgr class in the urllib.request module, along with its subclasses HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account when matching stored credentials against a requested URL. Credentials added for an https:// URL were also used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials in cleartext. Credentials added for http:// URLs could likewise be sent over https://. Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme are only used for requests with the same scheme. Credentials registered with a bare authority (such as example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing code, including proxy authentication. Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http:// requests to hosts for which credentials are registered, for example by not following redirects to http:// URLs.
CVE-2026-17084: The "stringprep" module didn't process characters from RFC 3454 tables B.2 or B.3 correctly: the latest Unicode codepoint attributes were used instead of the specified Unicode 3.2.0. This behavior would cause mismatches when processing domain names using IDNA 2003 (the "idna" codec) and the in_table_b2() function of the "stringprep" module. This only affects domain names containing characters that were not previously registered or had their Unicode attributes such as case-folding behavior updated since Unicode 3.2.0.
CVE-2026-19672: 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, .. components are collapsed before the path reaches the filesystem, so the directories outside the destination are never created.

Created: 2026-01-21 Last update: 2026-09-01 22:00

14 security issues in forky high

There are 14 open security issues in forky.

14 important issues:

CVE-2026-0864: When using the "configparser" module to write configuration files containing multi-line text values with carriage return characters (\r) the resulting file could be injected with unexpected keys and values if the attacker controls the written value.
CVE-2026-4360: In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract() function.
CVE-2026-6879: `Element.findall()` and fully-consumed `Element.iterfind()` exhibit `O(n^2)` time complexity when using XPath index predicates (e.g. `[1]`, `[last()]`, `[last()-N]`) on XML documents with many same-tag siblings. `Element.find()` is only affected when the first match is near the end of the sibling list, such as with `[last()]` or `[last()-N]`; `.//item[1]` short-circuits after the first match.
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.
CVE-2026-11940: tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself. The extraction fallback validated the symlink at it's archived location but recreated it at the hardlink's shallower path, letting a relative target the filter judged contained escape the destination directory. This allowed a malicious tar archive to create a symlink pointing outside the destination, enabling out-of-destination file reads or writes. This was an incomplete fix of CVE-2025-4330.
CVE-2026-11972: When using the "tarfile" module with a file opened in "streaming mode" (mode="r|") the tarfile module did not properly handle EOF, making archive parsing take exponentially longer.
CVE-2026-15308: The incremental HTML parser (html.parser.HTMLParser) allows for CPU denial-of-service through repeated unterminated markup declarations when processing uncontrolled data.
CVE-2026-15310: When decompressing crafted zip files using the bzip/LZMA/Zstandard compressions, Python could use an attacker-controlled size to pre-allocate memory, possibly resulting in memory exhaustion.
CVE-2026-15806: The HTTPPasswordMgr class in the urllib.request module, along with its subclasses HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account when matching stored credentials against a requested URL. Credentials added for an https:// URL were also used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials in cleartext. Credentials added for http:// URLs could likewise be sent over https://. Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme are only used for requests with the same scheme. Credentials registered with a bare authority (such as example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing code, including proxy authentication. Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http:// requests to hosts for which credentials are registered, for example by not following redirects to http:// URLs.
CVE-2026-17084: The "stringprep" module didn't process characters from RFC 3454 tables B.2 or B.3 correctly: the latest Unicode codepoint attributes were used instead of the specified Unicode 3.2.0. This behavior would cause mismatches when processing domain names using IDNA 2003 (the "idna" codec) and the in_table_b2() function of the "stringprep" module. This only affects domain names containing characters that were not previously registered or had their Unicode attributes such as case-folding behavior updated since Unicode 3.2.0.
CVE-2026-18503: Attacker-controlled CSV samples can trigger super-linear regular-expression work during dialect sniffing and consume significant CPU when applications pass unbounded input to csv.Sniffer.sniff().
CVE-2026-19672: 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, .. components are collapsed before the path reaches the filesystem, so the directories outside the destination are never created.

Created: 2026-01-21 Last update: 2026-09-01 22:00

lintian reports 15 errors and 39 warnings high

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

Created: 2026-08-11 Last update: 2026-08-12 20:30

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

AppStream found metadata issues for packages:

idle-python3.14: 1 error and 1 warning

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

Created: 2025-09-19 Last update: 2025-09-19 09:30

Depends on packages which need a new maintainer normal

The packages that python3.14 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: 2025-09-19 Last update: 2026-09-02 15:30

3 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit b4113a10abd564ed52868e075f84f7679aceadd1
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Sep 1 11:48:55 2026 +0200

    prepare for upload

commit 45a89aebf9794475ec6a55cdb37839bd9852f28d
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Sep 1 10:48:14 2026 +0200

      * Apply the OpenSSL 4.0 patches from the 3.15 branch. Closes: #1137595.

commit 4f35f62b36f54c929c8221c239211597cd45a71f
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Sep 1 10:40:02 2026 +0200

      * Update to the 3.14 branch 2026-09-01.

https://salsa.debian.org/api/v4/projects/cpython-team%2Fpython3 API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.

Created: 2026-09-01 Last update: 2026-09-02 15:03

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2026-08-16 Last update: 2026-09-02 15:02

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: 2025-09-25 Last update: 2026-09-02 14:01

Multiarch hinter reports 2 issue(s) normal

There are issues with the multiarch metadata for this package.

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

Created: 2025-09-19 Last update: 2026-09-02 10:20

debian/patches: 13 patches to forward upstream low

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

13 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: 2025-09-19 Last update: 2026-08-11 18:31

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.
excuses:
- Migration status for python3.14 (3.14.6-1 to 3.14.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Updating python3.14 would introduce bugs in testing: #1146095
- ∙ ∙ Autopkgtest for calibre/9.13.0+ds+~0.10.6-1: i386: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for esys-particle: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for libreoffice/4:26.8.0.3-2: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for macaulay2/1.26.06+ds-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openbabel/3.1.1+dfsg-14: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for opm-common/2025.10+ds-4: arm64: Pass ♻ (reference ♻), riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for plfit/0.9.6+ds-2: arm64: Pass ♻, i386: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python3.14/3.14.7-1: amd64: Pass, arm64: Pass, armhf: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for pytorch/2.12.1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for ros-ros-comm/1.17.4+ds-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.14.html
- ∙ ∙ Not reproduced on amd64 (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
- ∙ ∙ Not reproduced on arm64 (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
- ∙ ∙ Not reproduced on armhf (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
- ∙ ∙ Reproducibility regression on i386: libpython3.14-minimal
- ∙ ∙ Reproducibility issues ignored for src:python3.14 as requested by ginggs
- ∙ ∙ 22 days old (needed 5 days)
- Not considered

news

[rss feed]

[2026-09-01] Accepted python3.14 3.14.7-2 (source) into experimental (Matthias Klose)
[2026-08-11] Accepted python3.14 3.14.7-1 (source) into unstable (Matthias Klose)
[2026-06-16] python3.14 3.14.6-1 MIGRATED to testing (Debian testing watch)
[2026-06-11] Accepted python3.14 3.14.6-1 (source) into unstable (Stefano Rivera)
[2026-05-24] python3.14 3.14.5-1 MIGRATED to testing (Debian testing watch)
[2026-05-11] Accepted python3.14 3.14.5-1 (source) into unstable (Stefano Rivera)
[2026-05-06] Accepted python3.14 3.14.5~rc1-1 (source) into unstable (Matthias Klose)
[2026-05-05] python3.14 3.14.4-2 MIGRATED to testing (Debian testing watch)
[2026-04-22] Accepted python3.14 3.14.4-2 (source) into unstable (Matthias Klose)
[2026-04-08] Accepted python3.14 3.14.4-1 (source) into unstable (Matthias Klose)
[2026-03-28] Accepted python3.14 3.14.3-5 (source) into unstable (Matthias Klose)
[2026-03-27] Accepted python3.14 3.14.3-4 (source) into unstable (Matthias Klose)
[2026-03-26] python3.14 3.14.3-3 MIGRATED to testing (Debian testing watch)
[2026-03-21] Accepted python3.14 3.14.3-3 (source) into unstable (Matthias Klose)
[2026-03-17] python3.14 3.14.3-2 MIGRATED to testing (Debian testing watch)
[2026-03-11] Accepted python3.14 3.14.3-2 (source) into unstable (Matthias Klose)
[2026-02-11] python3.14 3.14.3-1 MIGRATED to testing (Debian testing watch)
[2026-02-04] Accepted python3.14 3.14.3-1 (source) into unstable (Stefano Rivera)
[2025-12-12] python3.14 3.14.2-1 MIGRATED to testing (Debian testing watch)
[2025-12-06] Accepted python3.14 3.14.2-1 (source) into unstable (Stefano Rivera)
[2025-12-06] python3.14 3.14.0-5 MIGRATED to testing (Debian testing watch)
[2025-12-01] Accepted python3.14 3.14.0-5 (source) into unstable (Matthias Klose)
[2025-10-28] python3.14 3.14.0-4 MIGRATED to testing (Debian testing watch)
[2025-10-21] Accepted python3.14 3.14.0-4 (source) into unstable (Stefano Rivera)
[2025-10-20] Accepted python3.14 3.14.0-3 (source) into unstable (Stefano Rivera)
[2025-10-15] python3.14 3.14.0-2 MIGRATED to testing (Debian testing watch)
[2025-10-09] Accepted python3.14 3.14.0-2 (source) into unstable (Matthias Klose)
[2025-10-07] Accepted python3.14 3.14.0-1 (source) into unstable (Stefano Rivera)
[2025-09-25] python3.14 3.14.0~rc3-1 MIGRATED to testing (Debian testing watch)
[2025-09-18] Accepted python3.14 3.14.0~rc3-1 (source) into unstable (Stefano Rivera)

bugs [bug history graph]

all: 7
RC: 0
I&N: 6
M&W: 1
F&P: 0
patch: 0

links

lintian (15, 39)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.14.6-1