When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() &
Source GCVE Database
Not known to be exploited · fixed in 0.41.1 : patch Apache Qpid Proton C soon.
Data as of 29 Oct 2026, 13:47 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 0.41.1
Exploitation 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Qpid Proton C | Affected
| Fixed in– |
AI-suggested
Users should upgrade to Apache Qpid Proton C version 0.41.1, which fixes this issue. As a workaround, setting the SSL_CERT_FILE environment variable to /dev/null can prevent the accumulation of trust anchors. No action is required for users of the Win32 SChannel TLS implementation, as it is not affected.
Description
A vulnerability in Apache Qpid Proton C's OpenSSL TLS implementation causes the APIs pn_ssl_domain_set_trusted_ca_db() and pn_tls_config_set_trusted_certs() to add to rather than replace the default system trust anchors. This behavior can lead to trusting unexpected peer certificates. The issue does not affect the Win32 SChannel TLS implementation. It affects versions through 0.40.0 and is fixed in version 0.41.1.