Skip to main content
CVE-2026-105031VulnerabilityPublished Updated

Qpid proton: When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() &

Affects qpid-protonSource GCVE Database

0
Compare
Authoritative record:CVE-2026-105031· Critical 9.1

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

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.19.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Ubuntu 26.10qpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=stonkingOther threatsAffected
  • 0.37.0-7build1 – 0.37.0-9build1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=resoluteOther threatsAffected
  • 0.37.0-6 – 0.37.0-7build1
4 affected builds
Fixed in–
Ubuntu 24.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=nobleOther threatsAffected
  • 0.37.0-2build1 – 0.37.0-2build5
4 affected builds
Fixed in–
Ubuntu 22.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=jammyOther threatsAffected
  • 0.22.0-5.1 – 0.22.0-5.1ubuntu2
4 affected builds
Fixed in–
Ubuntu 20.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=focalOther threatsAffected
  • 0.22.0-3.2 – 0.22.0-3.3build1
4 affected builds
Fixed in–
Ubuntu 18.04 LTSqpid-protonpkg:deb/ubuntu/qpid-proton?arch=source&distro=bionicOther threatsAffected
  • =0.14.0-5.1
  • =0.14.0-5.1ubuntu1
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

Community reviews

Loading reviews…