Debian Package Tracker
Register | Log in
Subscribe

qpid-proton

Choose email to subscribe with

general
  • source: qpid-proton (main)
  • version: 0.41.1-1
  • maintainer: Debian OpenStack (DMD)
  • uploaders: Thomas Goirand (DMD)
  • arch: all any
  • std-ver: 3.9.8
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 0.22.0-5.1
  • oldstable: 0.37.0-2
  • stable: 0.37.0-6
  • stable-p-u: 0.37.0-6+deb13u1
  • testing: 0.37.0-10
  • unstable: 0.41.1-1
versioned links
  • 0.22.0-5.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.37.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.37.0-6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.37.0-6+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.37.0-10: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.41.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libqpid-proton-cpp12
  • libqpid-proton-cpp12-dev
  • libqpid-proton-cpp12-dev-doc
  • libqpid-proton11
  • libqpid-proton11-dev
  • libqpid-proton11-dev-doc
  • libqpid-proton11-dev-examples
  • python-qpid-proton-doc
  • python3-qpid-proton
action needed
4 security issues in forky high

There are 4 open security issues in forky.

4 important issues:
  • CVE-2026-105031: When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() & pn_tls_config_set_trusted_certs() APIs added to rather than replaced the default system trust anchors. Leading to potentially trusting unexpected peer certificates. This can be worked around by setting the SSL_CERT_FILE environment variable for the application to /dev/null. This issue does not affect the Win32 SChannel TLS implementation. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-105042: A message body that is deeply nested and decoded by pn_message_body() could overflow the stack and cause a crash. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-114230: When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-115942: A misconfigured wildcard TLS certificate causes a stack read overflow. This issue does not affect any wildcard certificate issued to the RFC9525 standard - the fix only accepts certificates that comply to this standard. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
Created: 2026-10-29 Last update: 2026-11-12 09:00
4 security issues in bookworm high

There are 4 open security issues in bookworm.

4 important issues:
  • CVE-2026-105031: When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() & pn_tls_config_set_trusted_certs() APIs added to rather than replaced the default system trust anchors. Leading to potentially trusting unexpected peer certificates. This can be worked around by setting the SSL_CERT_FILE environment variable for the application to /dev/null. This issue does not affect the Win32 SChannel TLS implementation. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-105042: A message body that is deeply nested and decoded by pn_message_body() could overflow the stack and cause a crash. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-114230: When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
  • CVE-2026-115942: A misconfigured wildcard TLS certificate causes a stack read overflow. This issue does not affect any wildcard certificate issued to the RFC9525 standard - the fix only accepts certificates that comply to this standard. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.
Created: 2026-10-29 Last update: 2026-11-12 09:00
lintian reports 1 error and 5 warnings high
Lintian reports 1 error and 5 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-09-03 Last update: 2026-11-11 05:30
Standards version of the package is outdated. high
The package is severely out of date with respect to the Debian Policy. The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 3.9.8).
Created: 2017-07-11 Last update: 2026-11-10 23:01
Multiarch hinter reports 4 issue(s) normal
There are issues with the multiarch metadata for this package.
  • libqpid-proton-cpp12-dev-doc could be marked Multi-Arch: foreign
  • libqpid-proton11-dev-doc could be marked Multi-Arch: foreign
  • python-qpid-proton-doc could be marked Multi-Arch: foreign
  • libqpid-proton11 could be marked Multi-Arch: same
Created: 2016-09-14 Last update: 2026-11-16 02:31
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: 2020-01-05 Last update: 2026-11-15 23: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 qpid-proton (0.37.0-10 to 0.41.1-1): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for gnocchi/4.7.0-8: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for python-pyngus/2.3.0-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for qpid-proton/0.41.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton.html
    • ∙ ∙ Not reproduced on amd64 (not a regression): libqpid-proton11
    • ∙ ∙ Not reproduced on arm64 (not a regression): libqpid-proton11
    • ∙ ∙ Not reproduced on armhf (not a regression): libqpid-proton11
    • ∙ ∙ Not reproduced on i386 (not a regression): libqpid-proton11
    • ∙ ∙ 5 days old (needed 5 days)
    • Not considered
news
[rss feed]
  • [2026-11-13] Accepted qpid-proton 0.37.0-6+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
  • [2026-11-10] Accepted qpid-proton 0.41.1-1 (source) into unstable (Thomas Goirand)
  • [2026-09-12] qpid-proton 0.37.0-10 MIGRATED to testing (Debian testing watch)
  • [2026-09-02] Accepted qpid-proton 0.37.0-10 (source) into unstable (Thomas Goirand)
  • [2026-06-22] qpid-proton 0.37.0-9 MIGRATED to testing (Debian testing watch)
  • [2026-06-17] Accepted qpid-proton 0.37.0-9 (source) into unstable (Thomas Goirand)
  • [2026-04-20] qpid-proton 0.37.0-8 MIGRATED to testing (Debian testing watch)
  • [2026-04-14] Accepted qpid-proton 0.37.0-8 (source) into unstable (Thomas Goirand)
  • [2025-11-01] qpid-proton 0.37.0-7 MIGRATED to testing (Debian testing watch)
  • [2025-10-27] Accepted qpid-proton 0.37.0-7 (source) into unstable (Thomas Goirand)
  • [2025-03-03] qpid-proton 0.37.0-6 MIGRATED to testing (Debian testing watch)
  • [2025-02-26] Accepted qpid-proton 0.37.0-6 (source) into unstable (Thomas Goirand)
  • [2025-01-12] qpid-proton 0.37.0-5 MIGRATED to testing (Debian testing watch)
  • [2025-01-07] Accepted qpid-proton 0.37.0-5 (source) into unstable (Thomas Goirand)
  • [2024-12-25] qpid-proton 0.37.0-4 MIGRATED to testing (Debian testing watch)
  • [2024-12-20] Accepted qpid-proton 0.37.0-4 (source) into unstable (Thomas Goirand)
  • [2024-11-09] qpid-proton 0.37.0-3 MIGRATED to testing (Debian testing watch)
  • [2024-11-04] Accepted qpid-proton 0.37.0-3 (source) into unstable (Thomas Goirand)
  • [2022-12-11] qpid-proton 0.37.0-2 MIGRATED to testing (Debian testing watch)
  • [2022-12-05] Accepted qpid-proton 0.37.0-2 (source) into unstable (Thomas Goirand)
  • [2022-06-11] qpid-proton 0.37.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-05-11] Accepted qpid-proton 0.37.0-1 (source) into unstable (Thomas Goirand)
  • [2020-12-29] qpid-proton 0.22.0-5.1 MIGRATED to testing (Debian testing watch)
  • [2020-12-26] Accepted qpid-proton 0.22.0-5.1 (source) into unstable (Bernd Zeimetz)
  • [2020-10-16] Accepted qpid-proton 0.22.0-5 (source) into unstable (Thomas Goirand)
  • [2020-10-15] Accepted qpid-proton 0.22.0-4 (source amd64 all) into unstable, unstable (Debian FTP Masters) (signed by: Thomas Goirand)
  • [2020-01-05] qpid-proton 0.22.0-3.3 MIGRATED to testing (Debian testing watch)
  • [2020-01-03] Accepted qpid-proton 0.22.0-3.3 (source) into unstable (Sandro Tosi)
  • [2019-08-10] qpid-proton 0.22.0-3.2 MIGRATED to testing (Debian testing watch)
  • [2019-08-08] Accepted qpid-proton 0.22.0-3.2 (source) into unstable (Kenneth J. Pronovici)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (1, 5)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 0.37.0-10
  • 1 bug (1 patch)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing