Skip to content
Fencer Intel
critical 9.1

CVE-2026-105031 json

Apache Qpid Proton C: The OpenSSL TLS implementation adds a locally trusted certificate authority to the existing trusted system trust anchors.

published 11d ago modified 4d ago also EUVD-2026-112725

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

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.

Is CVE-2026-105031 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-105031 updated cvss 7.4

qpid-proton: qpid-proton: improper certificate validation via retention of default system trust anchors

  • Red Hat AMQ Clients qpid-proton 0.40.0-2.el8 Red Hat OpenStack Platform 13 (Queens) qpid-proton-c, qpid-proton-cpp, qpid-proton-tests, python-qpid-proton, qpid-proton 0.40.0-2.el8 Red Hat OpenStack Platform 16.2 qpid-proton-c, python3-qpid-proton Red Hat OpenStack Platform 17.1 qpid-proton-c, python3-qpid-proton Red Hat Service Interconnect 2 qpid-proton 0.40.0-2.el8
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
4d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Apache Software Foundation Apache Qpid Proton C

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.