CVE-2026-105031: vulnerability in Apache Qpid Proton C
Apache Qpid Proton C: The OpenSSL TLS implementation adds a locally trusted certificate authority to the existing trusted system trust anchors.
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.1%
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.
Affected products
Apache Software Foundation · Apache Qpid Proton CRelated CVEs — Apache Qpid Proton C
In the same product, most dangerous first.
CVE-2026-114230—Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL framesEPSS 0.3%CVE-2026-105042—Apache Qpid Proton C: Unbounded recursion in parsing AMQP message bodies can lead to crashEPSS 0.2%CVE-2026-115942—Apache Qpid Proton C: Verifying non compliant TLS wildcard cert can cause stack buffer overflow readEPSS 0.1%