python3.14 - Debian Package Tracker

general

source: python3.14 (main)
version: 3.14.3-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]

testing: 3.14.3-1
unstable: 3.14.3-1

versioned links

3.14.3-1: [.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
libpython3.14-testsuite
python3.14 (1 bugs: 0, 0, 1, 0)
python3.14-dbg
python3.14-dev
python3.14-doc
python3.14-examples
python3.14-full
python3.14-gdbm
python3.14-minimal (1 bugs: 0, 0, 1, 0)
python3.14-nopie
python3.14-tk
python3.14-venv

action needed

3 security issues in sid high

There are 3 open security issues in sid.

3 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.

Created: 2026-01-21 Last update: 2026-02-10 12:30

3 security issues in forky high

There are 3 open security issues in forky.

3 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.

Created: 2026-01-21 Last update: 2026-02-10 12:30

lintian reports 14 errors and 31 warnings high

Lintian reports 14 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-02-06 08:31

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-02-12 20:00

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-02-12 17:32

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-02-12 16:01

2 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 d57b4881ea030da54e5990cbb79d8788d8071b94
Author: Stefano Rivera <stefanor@debian.org>
Date:   Thu Feb 12 08:25:55 2026 -0400

    More version handling for verify-signature

commit 73281db1262a2c7ad436d002c773146209ca418a
Author: Stefano Rivera <stefanor@debian.org>
Date:   Thu Feb 5 18:49:20 2026 -0400

    exec in pdbX.Y

Created: 2026-02-05 Last update: 2026-02-12 14:00

10 open merge requests in Salsa normal

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

Created: 2025-09-18 Last update: 2025-11-22 13:32

debian/patches: 11 patches to forward upstream low

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

11 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-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.3 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-02-05 05:49

news

[rss feed]

[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)
[2025-08-21] Accepted python3.14 3.14.0~rc2-1 (source) into experimental (Stefano Rivera)
[2025-07-24] Accepted python3.14 3.14.0~rc1-1 (source) into experimental (Stefano Rivera)
[2025-07-09] Accepted python3.14 3.14.0~b4-1 (source) into experimental (Stefano Rivera)
[2025-06-18] Accepted python3.14 3.14.0~b3-1 (source) into experimental (Stefano Rivera)
[2025-05-28] Accepted python3.14 3.14.0~b2-1 (source) into experimental (Stefano Rivera)
[2025-05-09] Accepted python3.14 3.14.0~b1-1 (source) into experimental (Stefano Rivera)
[2025-05-03] Accepted python3.14 3.14.0~a7-1 (source all amd64) into experimental (Debian FTP Masters) (signed by: Matthias Klose)

bugs [bug history graph]

all: 4
RC: 0
I&N: 2
M&W: 2
F&P: 0
patch: 0

links

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

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.14.2-1