python3.14 - Debian Package Tracker

general

source: python3.14 (main)
version: 3.14.7-4
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.7-4
unstable: 3.14.7-4

versioned links

3.14.7-4: [.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 (1 bugs: 0, 1, 0, 0)
python3.14-examples
python3.14-full
python3.14-gdbm
python3.14-minimal
python3.14-nopie
python3.14-tk
python3.14-venv

action needed

4 security issues in sid high

There are 4 open security issues in sid.

4 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-87910: 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.

Created: 2026-01-21 Last update: 2026-09-18 17:00

4 security issues in forky high

There are 4 open security issues in forky.

4 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-87910: 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.

Created: 2026-01-21 Last update: 2026-09-18 17:00

lintian reports 13 errors and 31 warnings high

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

Created: 2026-09-14 Last update: 2026-09-14 10:01

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: 2026-09-06 Last update: 2026-09-06 05: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: 2025-09-25 Last update: 2026-09-23 06:00

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-23 05:31

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-23 05:02

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.14.7-5, 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 98ca7240da66b45e135d9b30dd89488cf677689d
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Sep 15 14:37:47 2026 +0200

      * Update devhelp documentation for devhelp format v2 (Simon McVittie).

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-15 Last update: 2026-09-21 08:35

debian/patches: 20 patches to forward upstream low

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

20 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-09-13 19:30

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-09-19] python3.14 3.14.7-4 MIGRATED to testing (Debian testing watch)
[2026-09-13] Accepted python3.14 3.14.7-4 (source) into unstable (Matthias Klose)
[2026-09-12] python3.14 3.14.7-3 MIGRATED to testing (Debian testing watch)
[2026-09-05] Accepted python3.14 3.14.7-3 (source) into unstable (Matthias Klose)
[2026-09-03] python3.14 3.14.7-1 MIGRATED to testing (Debian testing watch)
[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)

bugs [bug history graph]

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

links

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

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.14.7-4ubuntu2
2 bugs
patches for 3.14.7-4ubuntu2