Qpid proton: When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() &
Affects qpid-protonSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical · fixed in 0.41.1 : patch qpid-proton as a priority.
Data as of 18 Nov 2026, 15:20 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 9.1 |
|---|
- Patch
- Available – fixed in 0.41.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10qpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-105031 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-105031 (opens in a new tab)
- openwall.com/lists/oss-security/2026/10/28/22 (opens in a new tab)
- issues.apache.org/jira/browse/PROTON-2976 (opens in a new tab)
- github.com/apache/qpid-proton/commit/d793f97e4a2d0f960eda32724a2e867236468337 (opens in a new tab)