python3.14 - Debian Package Tracker

general

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

versioned links

3.14.3-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.14.3-3: [.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
python3.14-nopie
python3.14-tk
python3.14-venv

action needed

lintian reports 13 errors and 32 warnings high

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

Created: 2026-03-21 Last update: 2026-03-22 03:31

9 security issues in sid high

There are 9 open security issues in sid.

9 important issues:

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-3479: pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.
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-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-03-21 17:30

9 security issues in forky high

There are 9 open security issues in forky.

9 important issues:

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-3479: pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.
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-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-03-21 17: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-03-25 07: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.3-4, 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 0d826099359ee2290749a8dd744e71a0e86c52ea
Author: Matthias Klose <[email protected]>
Date:   Wed Mar 25 06:33:50 2026 +0100

      * Update autopkg test dependencies for 3.14.

Created: 2026-03-25 Last update: 2026-03-25 06:16

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-03-25 04:31

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

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

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

Created: 2025-09-19 Last update: 2026-03-25 05:32

debian/patches: 13 patches to forward upstream low

Among the 35 debian patches available in version 3.14.3-3 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-03-21 18:00

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-03-21 17: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.
excuses:
- Migration status for python3.14 (3.14.3-2 to 3.14.3-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for boost1.88/1.88.0-1.4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for gyoto/2.0.2-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for python3.14/3.14.3-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for ros-geometry2/0.7.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
- ∙ ∙ Autopkgtest for ros-ros-comm/1.17.4+ds-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for ros-vision-opencv/1.16.2+ds-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Lintian check waiting for test results on riscv64 - info
- ∙ ∙ Too young, only 4 of 5 days old
- 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
- ∙ ∙ Not reproduced on i386 (not a regression): libpython3.14-dev, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
- ∙ ∙ Reproducibility check waiting for results on ppc64el
- Not considered

news

[rss feed]

[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)
[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: 3
RC: 0
I&N: 2
M&W: 1
F&P: 0
patch: 0

links

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

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.14.3-2